Skip to content

Accessibility statement

Accessibility statement

We want this site to work for everyone, on any device and with any assistive technology. This statement says where we are, what we are doing about it, and how to tell us when something fails.

Last updated: TODO: set the real date once published

The standard we aim at

WCAG 2.2 level AA. We treat it as a floor rather than a target: meeting it is a matter of care, not of a certificate.

TODO: complete a formal audit against WCAG 2.2 AA with the results recorded here, and a date on it, before publishing this page.

What we do as we build

Semantic structure, one heading per page, and a logical heading order so screen reader navigation matches the visual one.

Full keyboard operation with a visible focus indicator, and a link to skip the navigation on every page.

Colour pairs checked for contrast at AA, and never colour alone to carry meaning.

Respect for prefers-reduced-motion: animations, transitions and smooth scrolling are all turned off when your system asks for that.

Real text wherever possible, so it scales and translates. Nothing essential is locked inside an image.

Known limitations

TODO: list any genuine known issues with a planned fix date. An empty list here will not be true, and an empty list is worse than an honest one.

Third-party content

Embedded maps, videos and chat widgets are outside our control and often fall short of AA. Where we add one we choose the most accessible option available and give you a text alternative.

Tell us when something fails

Email [email protected] with the page and what happened. We will fix accessibility defects ahead of almost anything else in the queue, and reply with a date rather than a apology.

If you consider our approach inadequate you can also contact the Equality and Human Rights Commission, or the Web Accessibility Service.