We are committed to ensuring our platform is accessible to everyone, including people with disabilities.
The LMS Platform partially conforms to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. "Partially conforms" means that some parts of the content do not yet fully conform to the accessibility standard — see the "Known Limitations" section below for the current inventory. Remediation is tracked publicly in our technical-debt register (Wave 42 audit, May 2026) and addressed each engineering cycle. The full breakdown is published in our VPAT. Automated coverage is enforced in CI via @axe-core/playwright across all marketing routes; see axe-core.
| Technology | Support Level |
|---|---|
| Screen readers (NVDA, JAWS, VoiceOver, TalkBack) | Tested & Supported |
| Keyboard-only navigation | Full support |
| Text-to-speech | Built-in TTS (TD-741) |
| Browser zoom up to 400% | Supported (no content loss) |
| High-contrast OS modes | Supported |
| Voice control (Dragon NaturallySpeaking) | Partial |
| Switch access | Partial (keyboard-compatible UI) |
For in-scope service categories under Article 2(2) of the European Accessibility Act, this statement covers the functional accessibility requirements set out in Annex I (information, identification of interactive elements, perceivability, operability, understandability, robustness). The deadline for compliance is 28 June 2025. Final legal review of this statement is outstanding — see docs/COMMERCIAL_LAUNCH_STATUS.md.
Enforcement body in Spain: Oficina de Atención a la Discapacidad (OADIS). Enforcement body in Kazakhstan: Министерство труда и социальной защиты населения РК (out of EU AA Act scope, but the platform applies equivalent technical standards under Закон РК «О социальной защите инвалидов»).
If you encounter accessibility barriers or need content in an alternative format, please contact us:
This statement was last reviewed on 2026-05-08 (Wave 43 update — partial conformance disclosure refresh per EAA Annex II). WCAG conformance claim is verified continuously through automated CI enforcement (axe-core baseline diff per route); manual screen reader and keyboard sweeps are scheduled quarterly per docs/standards/A11Y_AUDIT_PROCESS.md.