The standard we work to
We target the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Tara is used by children as young as six, including children who are still learning to read, so several choices go beyond the minimum.
What is built in
- Large text by default. Body text never drops below 18px, with generous line spacing and short line lengths.
- Big targets. Every button and link is at least 44px tall; the PIN pad and main actions are considerably larger.
- No typing required to sign in. A child picks a character and taps four numbers, so reading and spelling are not barriers to entry.
- Keyboard support throughout, with a visible focus ring that we never remove.
- Reduced motion respected.If your device asks for less motion, animations stop — including the looping demonstration on the home page.
- Colour is never the only signal. Completed work shows a tick as well as a colour change.
- Meaningful labels. Icon-only buttons carry text labels for screen readers, and images have descriptions.
- Hindi and English at equal typographic weight, so Devanagari is not an afterthought.
What still needs work
We would rather publish this than let you find it the hard way. As of 31 July 2026:
- Voice input relies on the browser’s own speech recognition, which is unavailable in some browsers and handles Indian accents unevenly. Typing is always available as an alternative.
- The homework scanner depends on a camera and on a printed or handwritten page. There is currently no non-visual route to enter a question other than typing it.
- We have not yet completed a full audit with an external screen-reader user. Our testing so far has been internal.
- Some colour pairings on decorative tinted cards are close to, rather than comfortably above, the 4.5:1 contrast ratio.
If something is in your way
Tell us and we will fix it. Use the contact form and describe what happened, what you expected, and what device or assistive technology you were using. Accessibility reports are prioritised, not queued behind feature work.