Accessibility statement
Many of the people who use this website are older, use a phone with a small screen, or are reading in a second language. We want it to work well for all of them.
The standard we work to
We aim for the website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We test with automated tools, with a keyboard only, with the text zoomed to 200% and 400%, and on small phone screens, and we fix problems as we find them. Automated tools can't find every problem, so we also check pages by hand.
What we've done
- Text is set at a comfortable size, in a typeface designed for readers with low vision, and you can zoom without losing content.
- Colours meet contrast requirements. We never rely on colour alone to show meaning, such as an error.
- Every page works with a keyboard, with a visible focus outline and a "skip to main content" link.
- Forms have clear labels and hints, explain errors in words next to each question, and list all problems at the top so you can go straight to each one.
- Pages work without JavaScript; menus and forms fall back to simple links and standard form submission.
- Animation is kept to a minimum and is switched off if your device asks for reduced motion.
- Images that carry meaning have text alternatives; decorative images are hidden from screen readers.
- Pages are structured with headings, lists and landmarks so screen-reader users can move around quickly.
Known limitations
This website is new. A full accessibility review, including testing with screen-reader users, is planned before launch, and this section will list anything we find that we haven't yet fixed. If you find a problem now, please tell us.
Tell us about a problem
If something on this website is hard to use, or you need information in a different format, please use the contact page and tell us the page and what happened. We'll do our best to help and to fix the problem.
Statement prepared: 1 October 2026.