Legal
Accessibility statement
What we target, how we check it, and what to do if something here does not work for you.
Conformance target
This site aims to meet the Web Content Accessibility Guidelines version 2.2 at level AA. That is a target we test against rather than a certification, and this statement describes where we actually stand.
What we do
Pages are built as static HTML, so all content is present without JavaScript. The site ships no client-side framework, and the only script on the page is a few lines that fill in hidden form fields. Turning JavaScript off changes nothing you can see and does not stop the enquiry form working.
Every page has one H1 and a heading structure that follows the content order. A skip link is the first focusable element. The navigation menu on small screens uses a native details element rather than a scripted dropdown, so it works with the keyboard by default.
Form fields have real labels rather than placeholder text standing in for them. Focus outlines are visible and deliberately high contrast. Colour is not the only means of conveying information. Motion respects the reduced motion preference, and transitions are effectively disabled when that is set.
How this is checked
Every pull request runs an automated axe accessibility scan across a sample of page types, and the build fails on any violation. A Lighthouse accessibility score below 98 also fails the build.
Automated testing catches a minority of accessibility problems. It does not judge whether alt text is meaningful, whether a reading order makes sense, or whether a form is understandable, so automated passes are a floor rather than evidence of conformance.
Known limitations
Data tables on service area pages carry captions and header cells, but a wide table on a narrow screen still requires horizontal scrolling.
Some long-form pages are dense. We are working on making the summaries at the top of each page carry more of the meaning, so the detail below is optional rather than required reading.
This site has not yet been audited by a third party, and it has not been formally tested with every combination of screen reader and browser.
Telling us about a barrier
If something here does not work for you, we want to know, and you should not have to explain the technical reason. Describe what you were trying to do and what happened. Contact details are on our contact page.
We will acknowledge a report within five working days. If a fix will take longer than that, we will tell you what the alternative route is in the meantime, including arranging the same thing by phone.
Last updated 15 September 2026.