Accessibility

Learning should be legible for everyone.

Last updated · 5 June 2026

Our target conformance is WCAG 2.2 Level AA. We don’t always hit it perfectly — below, what we currently support, and what we know we still need to fix.

What we support today

  • Keyboard navigation with visible focus rings on every interactive element
  • Screen-reader semantic markup (landmarks, headings, ARIA only when needed)
  • Minimum 4.5:1 contrast in both light and dark themes
  • prefers-reduced-motion respected throughout
  • Offline-readable curriculum via service-worker (NetworkFirst on static, CacheFirst on read-only API responses)
  • Text-to-speech available for coach greetings, with a text fallback

Known limitations

  • The Live Debate Arena’s side-by-side streams are currently read as a flat sequence by screen readers — we’re working on landmark grouping.
  • User-submitted workbench artefacts may carry embedded formatting (PDFs, screenshots) we don’t fully control.
  • The PWA install prompt is browser-controlled and can’t be styled to our standards.

How we test

Keyboard-only navigation, VoiceOver (macOS/iOS), NVDA (Windows), and automated axe checks in CI. A formal third-party audit is on the 2026 roadmap.

Report a barrier

Email [email protected] or use /contact with topic “Product support”. We triage accessibility reports with higher priority than feature requests.