Accessibility statement

Plain-English summary: this site targets WCAG 2.2 AA across every page. We test with axe-core + Lighthouse on every commit and run a manual VoiceOver pass before each major release. If you encounter an accessibility barrier email [email protected].

Our commitment

We aim to meet WCAG 2.2 Level AA across the entire website. We treat accessibility as a baseline requirement, not a nice-to-have.

Conformance status

This site has been self-assessed against WCAG 2.2 AA. We last ran automated accessibility tests on 2026-04-20 (axe-core + Lighthouse, in CI). The last manual screen-reader pass (VoiceOver on macOS) was performed on 2026-04-20.

Testing approach

• axe-core runs on every CI pipeline (PR and main). Zero serious or critical issues required to merge.
• Lighthouse Accessibility audit runs on every CI pipeline. Score ≥95 required.
• Manual screen-reader pass before each major release (currently: macOS VoiceOver; NVDA + JAWS spot-check pre-launch).
• Keyboard-only navigation verified manually before each release.

Known issues

None at the time of v1.0 publication.

Compatibility

• Recent Chrome, Safari, Firefox, Edge
• macOS VoiceOver, NVDA, JAWS
• Reasonable mobile / touch performance on iOS Safari and Android Chrome

Technical specifications

• Semantic HTML5
• ARIA only where native semantics fall short
• No JavaScript required for core content reading
• Single-language (en-GB) site for v1.0

Feedback

If you encounter any accessibility barrier, please email [email protected]. We aim to respond within 5 working days and remediate as quickly as practicable.

Enforcement

If you remain unsatisfied with our response after 30 days, you may escalate via the UK Equality Act 2010 framework or to the Information Commissioner’s Office (https://ico.org.uk) for discrimination matters.

Effective date

Effective: 2026-06-11 · Last reviewed: 2026-06-11 · Version: 1.0.1