⭐ 0🔥 0🏆 0 pts

Accessibility statement

Typing is a route to independence for many disabled learners, so accessibility is part of the core design rather than an add-on.

Our goal

We aim for TypePlay to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We have not had a formal third-party audit yet, so this statement describes what is built, how we test it, and the gaps we know about. It will be updated as those gaps close.

Accessibility presets

Open Settings → Accessibility on any lesson or practice page. Each preset is one tap, can be combined with others, and puts your old settings back when you turn it off. Settings are remembered on your device.

Blind / low vision
Speaks each key as you type it (and says “wrong” with the expected key on a miss), speaks each completed word, announces the next key, switches on high contrast and extra-large text, and stops the cursor from moving past a mistake so you always know where you are.
Dyslexia
Switches typing text to the Lexend typeface with wider letter and word spacing.
Motor
Removes time pressure (timers count up instead of down) and ignores accidental repeated presses within a quarter of a second, which helps with tremor and bounce keys.
Reduce motion
Stops animations across the site. TypePlay also follows the “reduce motion” setting of your operating system automatically.
High contrast
Strong colours and clearly visible focus outlines.

Other features that help

Known limitations

How we check

Changes are checked with keyboard-only navigation and with the presets switched on. A full audit with screen readers and an external reviewer is planned; its results will be published here.

Tell us about a barrier

If something stops you or a learner from using TypePlay, email [email protected] with the page, what happened and the assistive technology you use. Accessibility reports are prioritised over new features. More advice is in our guide to accessible typing.

Last updated: 3 November 2026