Accessibility statement
This site is built to meet WCAG 2.2 level AA. That is the standard we hold ourselves to and the standard we build client sites to. This page sets out what that means in practice, what we know is imperfect, and how to tell us if something does not work for you.
Accessibility statement
What we have done
Semantic HTML throughout, with one main heading per page, headings in order with no skipped levels, and landmark regions that assistive technology can navigate by.
A skip link to the main content as the first focusable element on every page.
Visible focus indicators on every interactive element, and full keyboard operability with no keyboard traps.
Text contrast meeting at least 4.5:1 against its background, and 3:1 for large text and interface components.
Descriptive alternative text on images that carry meaning, and empty alt attributes on images that are purely decorative.
Text that reflows without horizontal scrolling down to 320 pixels wide, and remains usable when zoomed to 200 per cent.
Motion reduced automatically for anyone whose system requests it.
Form fields with real labels, errors described in text rather than by colour alone, and no time limits.
Known limitations
Some older PDF documents linked from the site may not be fully tagged for screen readers. If you need any document in an accessible format, ask and we will provide one.
Embedded third-party maps are not fully accessible. Wherever a map appears, the same information is given in text, and the address and directions are available without using the map.
Tell us if something does not work
If any part of this site is difficult or impossible for you to use, please tell us. Email or phone us using the details in the footer and describe what you were trying to do. We will respond within five working days and fix what we can.
We would genuinely rather hear about it than not. A site that fails somebody silently is a site we do not know is broken.
How we test
Automated testing with axe as part of the build, keyboard-only navigation on every template, and manual checks with a screen reader on the main page types. Automated tools catch roughly a third of real issues, so the manual pass is the one that matters.