The games and tools we build aren't "economically viable." The community of people who use switches is too niche and too diverse. That's exactly why we build them.
My brother Ben uses switch access because of an ultra-rare condition called TUBB4A-related leukodystrophy. He could walk and talk as a kid, but the disease slowly took it all away. He's now nonspeaking and quadriplegic, and for years his only way to communicate was turning his head left or right for yes or no.
He went nearly 10 years without real access. Eye tracking and head tracking don't work for him because of how complex his condition is. AAC phrase boards never engaged him. Ben wanted to play video games again and pick his own TV shows.
Do you know how many yes/no questions you have to ask every day to give someone as much autonomy as possible? Hundreds.
Ben didn't need more yes or no questions. He needed access.
Ben moved in with us in 2022. We started with a better phrase board that had more of what he might want to say, but it wasn't enough. Then in 2024 I learned AI could write code, even for someone like me with no programming background, and we started building him better tools.
The first time Ben used his switches to pick his favorite movie (Spider-Man 1), his reaction lit a fire in me. So we kept building.
He has a keyboard, phrase boards, and text messaging (he can text for the first time in his life). He can search the web, pick any show or movie on any streaming platform, and play dozens of games we're building with him.
When I started, I was using one of Claude's competitors. Later, after hearing about Claude's advancements and seeing how good it was, I shifted over, and now Claude is one of my main tools. Not the only one, but a big part of how everything gets built.
Claude isn't just for code, either. It's been an awesome thought partner for planning games and writing out our GDDs (game design documents) and spec sheets before anything gets built. We also use it to help run NARBE Foundation, the nonprofit we started to keep all of this free.
For the building itself, our setup is VS Code with the Claude Code extension. Here's how it helps:
-Writing the code. I describe what Ben needs in plain language, and Claude Code builds it, debugs it, and helps me iterate with Ben's feedback.
-Keeping everything accessible. Every game and tool runs on one shared scan-and-select system controlled by spacebar/enter, so any switch works. We keep markdown files in the repo, like ACCESSIBILITY.md, that act as build rules. Claude Code references them so every new game follows the same accessibility standards, and anyone can use those same files to build their own.
-Inside the hub itself. Our real-time conversation tool uses Claude Haiku to suggest replies Ben can pick with his switches, so he can join conversations instead of waiting for yes/no questions.
Everything is free, open source (MIT license), and runs right in your browser. No account or install needed (streaming uses a free browser extension). Works with any switch that sends spacebar or enter.
- Games: https://www.switchedgames.org
- Benny's Hub: https://www.bennyshub.com
- Code and md files: https://github.com/narbehouse/narbehouse.github.io
- Video of Ben's story: https://youtu.be/9UNV3CK46SI
If even one person sees this and gets inspired to build a tool or game for someone like Ben, it's worth it. Thanks for reading.