Accessibility statement

This platform targets WCAG 2.1 Level AA and treats accessibility as a per-student feature, not a checkbox: many accommodations can be assigned individually and follow the student to every lesson.

Implemented across the platform

• Keyboard & screen reader: skip links, focus-trapped dialogs with focus restore, aria-live announcements, labeled controls, and semantic landmarks in the lesson engine and supports UI.
• Vision: high-contrast mode, color tint overlays, reversible text sizing, and contrast-checked design tokens on lesson pages.
• Reading & focus: text-to-speech read-aloud with adjustable rate, reading ruler, focus mode that softens non-active content, chunked presentation, and a distraction-free directions tool with audio.
• Motor & devices: large tap targets, a dedicated mobile-access layer on 1,754 pages, and full functionality on shared Chromebooks and phones.
• Cognitive & emotional: no timed pressure anywhere, no public failure states, consistent navigation, plain-language directions, break and check-in tools, and progress that saves automatically.

How it is tested

• Automated axe-core WCAG 2.1 A/AA scans run inside the end-to-end browser test suite on every supports surface (dialogs, tool panels, student modals); serious or critical violations fail the build.
• Structural validation gates every deploy; failed checks block the release.
• Real-classroom testing: the platform is used daily on district Chromebooks by the students it was built for, and issues students hit are fixed as they appear.

Known limitations

• Some 3D/AR manipulatives require pointer or touch interaction and device WebGL/WebXR support; every lesson's core content remains fully usable without them.
• Text-to-speech voice quality and available languages depend on the student's device/browser voices.
• Legacy activity pages outside the core curriculum are being brought up to the same standard progressively.

Feedback

If you or your student hits an accessibility barrier anywhere on this site, please report it through the class's usual channels (or a family letter reply) — accessibility reports are treated as bugs and prioritized.

Statement last reviewed: July 14, 2026.