Accessibility

A clear path should work for more people.

The public website is designed to support keyboard navigation, readable content, labeled forms, responsive layouts, and reduced motion. WCAG AA is the design target; this statement is not an independent certification.

View contact options

Design and interaction approach

Core content uses semantic headings and landmarks. Controls have visible labels and focus states. Information is available as text rather than depending only on a chart, color, hover, or animation. Navigation and forms should remain usable at narrow widths and with a keyboard.

Verification and limitations

Automated checks can identify some issues, but they do not replace keyboard, screen-reader, zoom, and real-user testing. Browser, assistive technology, and content changes can reveal additional barriers. External provider sites have their own accessibility characteristics.

Reporting a barrier

The contact page shows whether a support route is available. When reporting, include the page, task, problem, browser, and assistive technology if you are comfortable sharing them. Avoid sending personal or sensitive information that is not needed to describe the issue.