Accessibility
Built to be usable by everyone.
We target WCAG 2.2 AA across the platform, while continuing to test and improve the experience.
Implementation statement — not an independent accessibility audit. Updated 12 October 2026.
What we build for
We aim to support keyboard navigation, visible focus states, a skip-to-content link, readable colour contrast, semantic headings and landmarks, descriptive labels, responsive layouts, reduced motion preferences and accessible empty, error and loading states.
Current scope
The public pages and learner-dashboard foundation are implemented in the repository. Authentication, course playback, assessments, account settings, partner workflows and payment flows are not all connected yet, so those future experiences still require accessibility design and testing before launch.
Known limitations
This statement is not a certification and the application has not had an independent WCAG audit. Some contact, account and support workflows are still placeholders. The final contact route, assistive-technology test matrix and remediation targets need to be confirmed before production launch.
Tell us
If something is difficult to use, please use the Contact page once the confirmed support route is published. Include the page, the task you were trying to complete and the technology or browser involved if you can. We treat accessibility issues as product defects and will prioritise barriers that prevent people from learning, managing their data or asking for support.