Accessibility statement
We aim for WCAG 2.2 AA everywhere, and want to hear when we miss.
Our commitment
whytyping is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Every page works with a keyboard alone, text meets contrast minimums in both themes, and the site follows your reduced-motion setting.
What is built in
- The test is fully keyboard-operable: Tab then Enter restarts, Esc resets, and focus is always visible.
- Correct, incorrect and pending characters differ by more than colour: errors are underlined and extra characters are struck through.
- The mistake map gives each key's error count or rate as text, not colour alone.
- Results and the next word are announced through a live region, without announcing every keystroke.
- The typing text can be set to 100%, 120%, 140% or 160%, and pages can be zoomed to 200% without losing function.
- Count-up, wobble and press animations switch off with your system's reduced-motion setting, or from Settings.
- Content pages, lessons, guides and the FAQ are readable without JavaScript.
How we test
Each release passes an automated accessibility scan and a manual check with VoiceOver and NVDA, at text sizes up to 160%, in light and dark themes.
Known limitations
The finger guide in lessons is visual. The next key and finger are also given as text, but the colour-coded keyboard has no spoken equivalent yet.
A typing test measures typing on a keyboard, so the test itself cannot be completed by voice input or switch access. Guides and lesson instructions remain available.
Report a barrier
Tell us what you were trying to do and what got in the way: corpsach@gmail.com. We read every report and reply as soon as we can.