Anna Built a Speed Typing Game With Accessibility Features For Her Friend

One of the clearest signs that a student has genuinely learned something is when they use it for someone else. Anna is 11, and she's a student in Strive's Coding programme. She built a Speed Typing Challenge — a fully playable game — and the reason she built it the way she did is the part worth knowing about.
Her friend has dyslexia. And Anna decided, on her own, that her game should work for her.
What Anna Built
The Speed Typing Challenge is a polished browser game. Players type words or phrases against the clock, competing for speed and accuracy. That alone takes real coding skill — tracking keystrokes, scoring in real time, managing game states between rounds.
But Anna went further. She added:
- Open Dyslexic font — a typeface specifically designed to be more readable for people with dyslexia, with weighted letter bases that help with visual orientation
- Audio mode — words are read aloud rather than displayed, so players can engage without relying on visual text processing
- Speech input — players can respond verbally rather than by typing, removing the keyboard barrier entirely
Each of these features required Anna to think carefully about how her game would feel for someone with different needs, and then work out how to implement that technically. She did this at age 11, without a template to copy, guided by her own clear intention.
Why This Kind of Project Matters
In Strive's Coding course, students build games, visualisations, and interactive tools from the first few weeks. The technical foundations — Python, loops, functions, logic — are learned through projects students care about, not through drills or fill-in-the-blank exercises.
Anna's project is a good illustration of where that approach leads. She didn't build an accessible game because accessibility was a lesson objective. She built it because she thought about who would play it and what they would need. The technical choices followed from the human reasoning.
That's coding in the real world: starting from a problem, thinking through what someone actually needs, and working out how to deliver it. It's also what professional software developers do every day.
What the Technical Implementation Involves
Adding Open Dyslexic requires loading an external typeface and wiring up a settings toggle that swaps the active font class on the page. Audio mode requires a text-to-speech implementation — either using the browser's built-in speech synthesis API or an external library — and logic to suppress the visual display when that mode is active. Speech input uses the browser's speech recognition API, which involves event listeners, parsing spoken input, and matching it against the expected answer.
None of these are trivial. Anna worked through each of them with her Strive teacher, asking questions and debugging as she went. The game works. Her friend can play it.
What Comes Next
Students who complete Strive's Coding foundations progress to Strive AI Coding, where they build production-grade software and work alongside AI tools the way professional developers do. The move to AI Coding happens once a student has a solid enough grasp of how code works to direct AI effectively — to catch errors, understand what generated code is actually doing, and build things that function reliably.
Anna is on that path. And she's already building things worth showing.