Accessibility
Mental math should be open to every learner. NumThink aims to meet WCAG 2.2 level AA, and you can adjust how the site looks at any time from the Display button at the top of every page.
What you can change
- Theme: light, dark, dark blue, or high contrast (white and yellow on black). “Automatic” follows your device's light/dark and contrast settings.
- Text size: normal, large or extra large — the whole page scales, including practice questions.
- Easy-to-read font: Atkinson Hyperlegible (designed by the Braille Institute for low-vision readers) with Noto Sans Arabic, plus wider line spacing.
- Reduce motion: turns off animations and transitions. We also follow your device's reduce-motion setting automatically.
- Color-blind friendly colors: correct and wrong answers use blue and orange instead of green and red. Feedback never relies on color alone — it always has a ✓/✗ or words too.
Your choices are saved on this device only (in your browser) and are never sent to us. They also apply to worksheets your teacher sends you by link.
How we check
- Every text and background color pair in every theme is tested automatically for at least 4.5:1 contrast (7:1 for body text in high contrast) before the site is published.
- Everything works with a keyboard: Tab moves between fields, Enter submits an answer, and a visible focus ring shows where you are. A “Skip to content” link is the first thing on every page.
- Math is written as real text (not images), so screen readers and browser zoom work on it.
- Pages use proper headings, labels and language tags (English and Arabic, right-to-left).
Known limits and what's next
- The result image a student can share after a worksheet is a picture; the same result is always also sent as text.
- We are working on a spoken mode for blind and low-vision learners (questions read aloud, answers by voice or keyboard).
Tell us what doesn't work
If something on NumThink is hard to use with your device, assistive technology or settings, please contact us — describe the page and what happened. Accessibility reports are treated as bugs and fixed first.