Accessibility Statement

1. Our Commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible to people with disabilities — including auditory, cognitive, neurological, physical, speech, and visual disabilities — and more user-friendly for everyone.

Accessibility is not a one-time project but an ongoing commitment. It is integrated into our design system, component library, and development workflow.

2. Conformance Level

3. Measures We've Taken

• Semantic HTML: Proper heading hierarchy (h1 → h2 → h3), landmark regions (<header>, <main>, <nav>, <footer>), and descriptive <title> elements on every page
• ARIA labels: aria-label, aria-describedby, and aria-live regions used where semantic HTML alone is insufficient
• Keyboard navigation: All interactive elements reachable via Tab; custom keyboard shortcuts documented and non-destructive
• Focus management: Focus is never lost during modal open/close, page navigation, or dynamic content updates; focus moves to new content appropriately
• Colour contrast ratios: All normal text meets 4.5:1; large text and UI components meet 3:1 — verified with both automated tooling (axe-core) and manual inspection
• Form fields: Every input has an associated <label> or aria-label; error messages are programmatically associated with their field
• Images: All <img> elements carry descriptive alt text; decorative images use alt=""
• Touch targets: All interactive elements are at least 44 × 44 CSS pixels, meeting WCAG 2.1 Success Criterion 2.5.5
• Reduced motion: All animations respect prefers-reduced-motion — essential content is always visible without animation
• Skip link: A "Skip to main content" link is the first focusable element on every page

4. Known Limitations

While we strive for full accessibility, some areas may not yet be fully optimised:

• PDF documents: Some published PDF resources (e.g., whitepapers, compliance attestations) may not be fully tagged for accessibility. We are actively remediating these; contact us for an accessible alternative.
• Third-party embedded content: Embedded demo videos from YouTube/Vimeo may not have full keyboard control. We are migrating to accessible video players.
• Live chat widget: The live chat widget on the marketing site may not yet fully announce its status changes to screen readers — we are working with the vendor on an update.
• Legacy browser combinations: Some older browser/AT combinations may not render all accessibility features correctly. We test against the two most recent versions of Chrome, Firefox, Safari, and Edge.

5. Feedback & Contact

We welcome your feedback on the accessibility of PostMTA's website. If you encounter any barriers or have suggestions for improvement, please contact us:

We aim to respond to accessibility-related feedback within 5 business days and to remediate confirmed barriers within a commercially reasonable timeframe.

6. Technical Specifications