Overview
Accessibility statement
The site aims to meet WCAG 2.2 Level AA and to work with keyboard navigation, screen readers, zoom and common assistive technologies. Accessibility is treated as an ongoing publishing requirement.
Design and code commitments
Pages use semantic headings, visible keyboard focus, sufficient contrast, descriptive link text and responsive layouts. Images receive meaningful alternative text when they convey information and empty alternatives when decorative.
Motion and interactive controls should respect user preferences.
Content commitments
Guides use plain language, short paragraphs and descriptive headings without removing necessary legal precision. Tables and calculators need labels, instructions and errors that do not rely on colour alone.
PDF-only information should be avoided where an HTML alternative is possible.
Known limitations
Third-party government pages, maps and embedded services may not meet the same standard. New tools and translated editions require separate keyboard and screen-reader testing before release.
Any known material limitation should be listed and prioritized for repair.
Report a barrier
A user can report the page, device, browser, assistive technology and task that failed. Personal disability information is not required beyond what helps reproduce the barrier.
We aim to acknowledge reports and provide an accessible alternative while a fix is developed.
Frequently asked questions
Questions about accessibility statement
Which standard does the site target?
WCAG 2.2 Level AA.
What should a barrier report include?
The page, attempted task and relevant device or assistive technology, without unnecessary personal information.
Related guides
