Accessibility statement

What the build gives you

• A skip link to content on every page, and focus moved to each page’s heading on navigation
• Keyboard operation throughout, including the menu panel (Popover API) with Escape and focus return
• Light and dark themes that follow your choice and the system setting, with matching colour-scheme
• Motion, cursor, and progress controls that respect prefers-reduced-motion and paused-motion settings
• Text spacing that reflows at 320 pixels wide with no sideways scrolling
• Touch targets at least 24 pixels, and forced-colors modes kept distinct

On the focus pattern: after the skip link, a fresh page lands focus on its main heading, so keyboard and screen-reader users start where the content starts; Tab then walks the page in reading order.

How it is checked

Automated axe checks (WCAG 2.0/2.1/2.2 A and AA rules) run against the public pages at phone and desktop sizes in both themes, as part of the build’s test gate — the run’s evidence records them green. Keyboard journeys are tested for the menu, the finder, the enquiry forms, and the desk.

What is not yet checked

Real-device phone checks: not run. The owner chose emulation (Playwright device profiles and Lighthouse mobile) for this build, so every claim above is emulation-grade, and real-device behaviour — voice control, platform zoom, switch access — stays unverified until those checks run. When they do, this section is replaced by their results.

Reporting a barrier

The demonstration has no live inbox (see the contact page — that is the honest position). At go-live a monitored route opens and this section names it, with a commitment to respond.