Accessibility

Accessibility Statement

Last updated: August 22, 2026

How we work on accessibility

Accessibility is part of design, development, testing, and remediation. We use semantic HTML, keyboard-operable controls, visible focus treatment, text alternatives, responsive layouts, and sufficient color contrast. We do not use an accessibility overlay as a substitute for fixing the website itself.

Testing program

We maintain automated and manual checks for the public website. Automated tests use axe-core rules mapped to WCAG Level A and AA and run across every public route. Manual reviews cover:

• Keyboard-only navigation, focus order, focus visibility, and bypass links
• VoiceOver with Safari and NVDA with Chrome or Firefox
• Text zoom, browser zoom, and reflow at narrow viewport widths
• Labels, instructions, errors, and status messages in forms
• Focus management, names, descriptions, and dismissal behavior in dialogs
• Text alternatives, data tables, labels, and non-color cues for charts

Forms, dialogs, and charts are not currently present on the public site. They remain in the required test matrix so those checks are completed before any such component is released.

Evaluation and remediation

We preserve dated audit records and a remediation log. Issues are assigned a severity, owner, target date, and retest result. Automated tools are useful for prevention, but they cannot establish conformance on their own, so human testing remains required.

Known limitations

App store badges and destination pages are provided by Apple, Google, and Amazon. Their accessibility is controlled by those services. We continue to test the links and provide descriptive accessible names on this website.