Accessibility statement
What we have built in, what we know is imperfect, and how to tell us when we get it wrong.
Template note. This statement describes the template as shipped.
Once you add your own content, re-test and update it — an accessibility statement
that no longer matches the site is worse than not having one.
Last updated 1 January 2026
The standard we target
This site aims to meet WCAG 2.1 Level AA. That is the level most public bodies and large organisations are held to, and the one referenced by the European Accessibility Act.
What is built in
- Every text colour meets the AA contrast ratio against the background it sits on, including on tinted and dark sections
- A skip link to the main content on every page
- Visible focus outlines on everything reachable by keyboard
- Every form control has a label, including where the design shows none
- State is announced, not only shown —
aria-expanded,aria-pressed,aria-selectedandaria-current - Animation and page transitions respect
prefers-reduced-motion - Headings run in order, with one
h1per page - Nothing depends on colour alone to be understood
Known limitations
- The checkout is a demonstration and does not process payments
- Some decorative imagery is set as a CSS background and so is not announced — this is deliberate, as it carries no information
- Third-party content you embed later, such as a map, is outside our control and may not meet the same standard
Telling us about a problem
If something here is not usable for you, tell us through our contact page and say which page and what happened. We will reply within five working days.
How this was assessed
By a mix of automated contrast and structure checking and manual keyboard testing. Automated tools catch a minority of accessibility problems, so this statement claims what was tested rather than perfection.