Accessibility

Designed to be usable by every learner.

A short statement of what we aim for, where we are, and how to flag what we miss.

Last updated: 2026-06-05

Our standard

We design and test Aria against WCAG 2.1 Level AA as the baseline, with selected AAA criteria where the surface allows it (e.g. enhanced contrast on instructional text, captioning on all voice output).

Concrete commitments

Voice is optional. Every voice interaction has a text-and-chat equivalent. A learner who can't hear or speak can complete the same session via the chat panel + on-screen whiteboard.
Keyboard-only operation. All learner workflows — lobby, session, answer submission, hints, exit — are reachable without a mouse or touchscreen.
Screen-reader compatibility. Live ARIA announcements for Aria's voice content, whiteboard updates, and turn outcomes. Tested on VoiceOver (macOS, iOS) and NVDA (Windows).
Color contrast. All instructional content meets WCAG AA contrast ratios at default zoom; UI chrome meets AAA where practical.
Motion control. Auto-advancing animations respect the prefers-reduced-motion setting.
Form factor. Tablet-first (iPad, Android tablets, Fire HD) with a mobile-graceful layout. Touch targets meet WCAG 2.5.5 minimum size.

Where we're still working

Some manipulatives (FractionBars, Base10Blocks, Geoboard, AlgebraTiles) currently lean on touch/drag input. We're shipping keyboard alternatives in the next quarter. The live whiteboard's freehand pen input has limited screen-reader narration; we surface the same content as text under the canvas, but the lived experience for SR users is still being improved.

Reporting a barrier

If you hit something that doesn't work for you, please tell us: contact us with the page, assistive technology, and what happened. We treat accessibility reports as P1 product bugs — not feature requests.