Accessibility — Public Services Guide

Last updated: 2026-04-14

Our commitment

Public Services Guide targets WCAG 2.1 AA conformance. This was set as the baseline in the project's foundation epic and every component and page added since has been built against it.

Current state

The site is built with semantic HTML, keyboard-first interaction, visible focus indicators, and a high-contrast colour system. Every page runs through automated accessibility checks (axe-core via Lighthouse) before release, and every component was designed to be operable without a mouse.

That said, "tested" and "flawless" are not the same thing. If you find something that does not work for you, please tell us.

Known non-conformance items

None at the date above. If automated or user-reported audits surface items in the future, they will be listed here honestly — we do not hide gaps.

Tested browser and assistive-technology combinations

Chrome + keyboard-only navigation (primary test path)
Safari + VoiceOver (macOS) for screen-reader spot checks
Firefox + keyboard-only for focus-management verification
Mobile Safari + iOS VoiceOver for touch + screen-reader flows

We do not claim exhaustive testing against every assistive tech. If you use NVDA, JAWS, TalkBack, Dragon, ZoomText, or a configuration not listed and hit a barrier, please report it — your report becomes part of the next release's regression test.

How to report an accessibility issue

Email [email protected] with "Accessibility issue" in the subject line.

Please include: what you were trying to do, what went wrong, the page URL, your browser and assistive tech (if any), and — if comfortable — a screenshot or recording. We aim to acknowledge reports within 7 days.

Response commitment

Serious and critical issues (blocks someone from completing a task) are prioritised above other work. Moderate and minor issues are batched and fixed in the next polish cycle. Every report is acknowledged, even if the fix takes time.