Accessibility

The commitment

This site is built to be usable by everyone, and the architecture helps: almost every page is static HTML with no JavaScript required, one small interactive tool aside. If scripts fail to load, the content is still there.

The target is WCAG 2.2 Level AA.

What is done

• Semantic HTML with a single, correct heading order per page.
• A skip link to the main content, and visible keyboard focus throughout.
• Every interactive control reachable and operable by keyboard.
• Text alternatives for meaningful images; decorative images marked as decorative.
• Data tables with proper header cells and scope.
• Colour never used as the only way to convey status — evidence and page states carry text labels as well.
• Layout in relative units, so browser zoom and larger text sizes work.

Known gaps

Stated plainly rather than claimed away:

• No independent audit has been carried out. This statement reflects the standards the site is built to, not a verified conformance assessment.
• No assistive-technology testing has been done yet with screen readers or voice control.
• The route finder has not been separately audited. It is the one interactive component on the site, and it is the most likely place for a barrier.
• Long comparison tables may be awkward on small screens even though they scroll.

These will be worked through, and this page will record what changes.

Reporting a barrier

If something here is unusable for you, report it — including which page, what you were trying to do, and the browser or assistive technology you were using. Accessibility problems are treated as site errors under the same correction policy as factual errors, and are logged in updates when fixed.