Accessibility

The service path should work without a mouse or a map.

This site is built around semantic HTML, visible focus states, keyboard-accessible navigation, readable contrast, reduced-motion support, and ordinary directory links.

What the site supports

• A skip link to main content
• Keyboard navigation for menus, links, finder controls, and FAQ disclosures
• A complete text directory beneath the geographic map
• Alternative text and intrinsic dimensions for meaningful images
• Responsive layouts designed to avoid horizontal overflow
• Reduced motion when the browser preference is enabled

Known limits

The service-request form is long by design, because triage questions come before contact details. Every step has visible labels, inline error messages, and a live region that announces progress, but a four-step flow is still more work with a screen reader than a single page would be. If any step is hard to complete, tell us and we will fix it.

Feedback

No accessibility contact address has been verified for publication. This statement must be updated when the public contact path is configured.