Accessibility

Last updated: August 24, 2026

Mathmatix is a math tutor for children, including children who use a screen reader, navigate by keyboard, or need extended time and read-aloud to work. This page says what we have done, what is checked automatically so it stays done, what we have not done yet, and how to tell us when something is in your way.

It is a statement of practice, not a conformance claim. We have not yet had a third-party audit against WCAG 2.1 AA, and we would rather say so than imply otherwise.

What is in place

Every interactive control has a name. Buttons, links, inputs and selects on every page announce what they do, not a glyph or nothing. Icon-only controls carry explicit labels; decorative icons are hidden from assistive technology.
No control is nested inside another control. A button inside a button cannot be reached separately by keyboard or screen reader; there are none.
Choosers work like radio groups. Where the interface offers a set of options to pick one from — tutors, avatar styles, colors — Tab moves between groups, arrow keys move within one, and focus is visible while it moves.
Skip links on public pages jump past the header to the content.
Visible focus on interactive elements, using an outline offset from the element rather than a color change that could be confused with selection.
Read-aloud of the tutor’s replies, available to every student on every plan.
Accommodations the tutor honors, set per student by a teacher or parent: extended time, chunked instructions, read-aloud, calculator access, breaks, reduced distraction, a digital multiplication chart, large print and high contrast, and math-anxiety support. The tutor re-reads these on every turn, not just at setup.
Reading level adapts to the student, separately from grade level.

What is enforced automatically

The first three items above are not promises kept by hand. Automated tests in our codebase parse every page and fail the build if a control loses its name, a control is nested in another, or an option chooser stops behaving as a radio group. A change that would regress them cannot be merged.

What is not done yet

No third-party WCAG audit and no VPAT. Schools that require one should ask us; we would rather tell you where we stand than have you find out.
Math on screen. Equations are rendered with KaTeX, which produces accessible markup, but how well a given screen reader voices complex notation varies by reader and by browser. We have not yet tested every combination.
Color contrast has been checked by eye against the brand palette, not measured against WCAG AA on every surface.
The interactive whiteboard and graphing tools are visual by nature and do not yet have non-visual equivalents. The tutor’s written explanation always accompanies them.

Tell us what is in your way

If you or your child hit something that does not work with a keyboard, a screen reader, magnification or voice control, contact us with the page, what you were trying to do, and the assistive technology you use. We treat these as bugs, not feedback.