Our commitment
We consider accessibility when building the site and editing its content. We aim to remove barriers that prevent people from finding and using directory information.
Our current approach
- Use semantic landmarks and a consistent heading structure.
- Support keyboard navigation and visible focus indicators.
- Respect system color and reduced-motion preferences.
- Maintain readable contrast and layouts that reflow on zoom.
- Provide text alternatives for meaningful images.
- Keep essential directory content available without JavaScript.
- Use clear labels and instructions for forms and controls.
Known limitations
Automated checks cover representative public routes and selected interactions. They cannot test every way people use assistive technology. We still need to test full tasks using only a keyboard and check key tasks with screen readers before launch.
We plan to test NVDA with Firefox and Narrator with Edge on Windows, VoiceOver with Safari on macOS and iOS, and TalkBack with Chrome on Android. Listing media requires ongoing editorial review, and third-party destinations may present barriers outside our direct control.
We will document confirmed limitations that cannot be fixed immediately and provide an alternative way to obtain the affected information when practical.
Request help or report a barrier
Email [email protected] with the subject Accessibility. Include the page URL and what you were trying to do. If you are comfortable sharing them, include your browser, device, and assistive technology.
You can also review all contact topics on the Contact page.
Assessment status
On July 22, 2026, automated browser checks reported no axe-detected WCAG 2.0 or 2.1 Level A or AA violations on the representative public routes in the test build. The same suite verified that the first keyboard focus reaches the skip link, pages contain no positive tab order, and representative layouts do not overflow at 320, 768, or 1440 CSS pixels.
Those results apply only to the tested build, routes, rules, and fixtures. They are not a claim of formal conformance or third-party certification. We will update this statement as manual testing, remediation, and the public directory progress.