Our target
We target WCAG 2.2 AA across the whole platform. The design system enforces colour-contrast ratios, focus rings that are visible in both themes, motion that respectsprefers-reduced-motion, and keyboard operability on every interactive control.
What we test with
- Keyboard-only navigation across the top user journeys (sign in, browse catalog, enrol, complete a lesson, submit an assessment, open the help drawer).
- VoiceOver on macOS and iOS.
- NVDA on Windows.
- Talkback on Android for the responsive surfaces.
- Browser zoom up to 200% without layout breakage.
Known gaps
We’re being honest here rather than aspirational.
- Some third-party content packages (SCORM, H5P) carry their own accessibility posture that we do not control. We recommend authors follow WCAG guidance inside their content.
- The AI authoring and skills-generation panels are new and receive AT testing on a rolling basis; if you hit a barrier there, please report it and we’ll prioritise the fix.
- The rich-text editors used for course authoring have keyboard-operability gaps in a handful of secondary formatting controls; these are on the near-term backlog.
How to report a barrier
Email [email protected] with the page URL, the AT you were using, and what happened. We treat accessibility reports the same way we treat critical bugs and typically respond within 5 business days.
Alternative access
If you cannot access something on the Service, please contact us and we will help you complete the task — whether that means pairing on a workaround or supplying the information a different way.