About · Evidence record
Accessibility testing and limitations
This record distinguishes development checks from completed manual evaluation. A successful automated test or merged fix does not prove an accessible experience for everyone.
Evidence currently available
- Automated checks: the repository includes Playwright and axe tests for selected routes and interaction behaviours. These tests can identify some technical failures but do not establish WCAG conformance for the whole site.
- Development corrections: documented fixes include the keyboard Lab's pointer-only example, contact-form conditional fields and keyboard dismissal, and Investigation output safety and evidence provenance. See the merged pull requests for implementation history.
- Limited manual observations: selected mobile screenshots and scenarios have been reviewed during development. These are not a completed device or assistive-technology test cycle.
Not yet verified
- End-to-end VoiceOver, TalkBack and switch-access journeys on physical devices.
- Representative keyboard-only journeys and focus order across the whole website.
- Systematic text resizing, reflow, zoom, text spacing and contrast evaluation.
- Usability with independent participants unfamiliar with the project.
- Comprehensive scenario coverage of every Investigation decision rule and every Lab demonstration.
How results will be recorded
For each completed test, record the page or journey, date, browser and device, assistive technology and version if used, steps, expected and observed results, outcome, limitations, and linked issue or correction. Do not convert a planned test into a claimed pass.
Current status
No full accessibility conformance claim has been made. The public issue register and independent user-testing results remain incomplete. Please report a barrier if you encounter one.