Assistive Technology for Gaming: Switches, Braille Displays and Adaptive Controllers
For plenty of disabled players, the game was never the real obstacle. The input was. A standard controller quietly assumes two steady, nimble hands, and it takes for granted that you can see what you're pressing. A keyboard makes much the same bet. That's a lot of assumptions to mould into one lump of plastic. Assistive technology knocks them over, so a player can reach a game through whatever their body happens to do well.
This is hardly a fringe audience, either. The World Health Organization estimates that 1.3 billion people experience significant disability, which works out at roughly 1 in 6 of us. A good share of them want to play games, and they've been patching together workarounds for decades.
I've spent a surprising amount of my time building EchoQuest fretting about input, mostly because an audio game lives or dies on how you talk back to it. So this guide walks through the main families of assistive tech for gaming and what each one asks of a game. I'll also be straight about where EchoQuest fits, including which parts I built on purpose and which parts simply work because the game sticks to standard, well-behaved web pages.
Adaptive Controllers
Adaptive controllers are hubs. You plug in big buttons, joysticks, foot pedals and switches, and each one gets mapped to an ordinary controller input. Microsoft and Sony each sell an official one now, and a lively third-party scene has grown up around them.
The Xbox Adaptive Controller is the one most people have heard of. Microsoft says it was designed with extensive input from gamers with disabilities, and its spec sheet lists nineteen 3.5mm ports plus two USB ports for external inputs. It pairs with Xbox One and Xbox Series X and S consoles and Windows 10 and 11 PCs, and Microsoft also lists iOS, Android and some smart TVs over Bluetooth or USB. The Xbox Accessories app handles button remapping and profiles, and a Profile button on the controller flips between three of them. Sony answered with the Access controller for PS5, which launched worldwide in December 2023 after a five-year effort in which Sony worked with AbleGamers, Stack-Up and SpecialEffect. It ships with swappable button and stick caps and four standard 3.5mm expansion ports. You can set up as many as 30 control profiles in the PS5's settings and keep three on the controller itself. Around the Xbox pad in particular there's a healthy market of add-ons, such as Logitech's Adaptive Gaming Kit: a dozen buttons and triggers, light-touch buttons and pressure-sensitive variable triggers among them, that you fix with hook-and-loop boards or ties wherever suits you.
Best for: players with limited hand mobility, strength or dexterity. What games need: full button remapping and hold-to-toggle options.
Now a confession, because I'd rather you hear it from me than find out mid-session. EchoQuest doesn't read controller input directly. It's a web app you drive by keyboard, touch, pointer or voice, so an adaptive controller only reaches it if something on your system turns those buttons into keystrokes or clicks. On Windows or Linux, a free mapper such as AntiMicroX, which maps gamepad buttons to keystrokes and mouse actions, can be that bridge for an Xbox Adaptive Controller plugged into a PC. Then the controller is simply pressing EchoQuest's ordinary keyboard shortcuts. If you'd rather skip the gamepad altogether, Microsoft's Adaptive Hub and Adaptive Buttons are a tidy fit. Microsoft built them to replace or augment a regular mouse and keyboard, the buttons can be programmed with macros, and the hub also accepts ordinary assistive switches through 3.5mm ports. Nothing in EchoQuest needs holding down, either, so hold-to-toggle never comes up. Proper controller support is on my wish list. Until it ships, though, I won't pretend it exists.
Switches
A switch is a single input. It might be a large button, a sip-and-puff tube, a head switch or a blink sensor. Switch users often get around an interface by scanning: the interface highlights options one at a time, and pressing the switch picks whichever one is lit.
Both phone platforms have this baked in. Apple's Switch Control works with Bluetooth and Made for iPhone switches, and it can even turn the front camera into a pair of switches that you trigger by turning your head left or right. Its item scanning "highlights items or groups on the screen one at a time," in Apple's own words. Over on Android, Switch Access does the same job and happily accepts dedicated USB or Bluetooth switches, a plain keyboard, or the phone's own volume buttons.
Best for: players with very limited movement. What games need: turn-based play, no time pressure, and interfaces with a small number of clear choices.
Turn-based and narrative games suit switch users especially well, and honestly, that's one area where an RPG built around conversation has a head start. At the end of every scene, EchoQuest offers suggested choices: three to five plainly labelled options, one of them an open-ended "something else" option. Each is an ordinary button in a numbered list, which is exactly the sort of thing Switch Control and Switch Access know how to scan. To be clear, I didn't write any switch-specific code for this. Scanning works because the choices are plain, properly labelled buttons, which is what these tools expect from any well-built web page. You never have to type, and no clock is ticking while you decide.
I did learn one lesson here the hard way. At one point EchoQuest announced and focused the choices while the narrator was still talking, so screen reader users got two voices at once. Scanning through options while somebody talks over you is no fun, either. So now the choices wait. Once the narrator falls quiet, the game reads them out and, by default, puts focus on the first one, so scanning can start from there.
Braille Displays
A refreshable braille display shows text as tiny pins that rise and drop to form braille cells, changing as the text changes. Paired with a screen reader, it lets deafblind players and braille readers take in game text by touch.
Support runs wider than most people guess. NVDA, the free Windows screen reader, can output its information in braille and detects a long roster of displays automatically, from HumanWare's Brailliant series to any display that speaks the Standard HID Braille protocol. On Apple devices, VoiceOver pairs with a Bluetooth refreshable braille display so you can read the screen and control the phone from it, with contracted or uncontracted braille tables in plenty of languages.
Best for: deafblind players and braille-first readers. What games need: real text (not images of text), proper screen-reader support, and no timed reading.
Text-based and web-based games built on accessible HTML work with braille displays through screen readers like NVDA, JAWS and VoiceOver. To be clear, EchoQuest contains no braille-specific code, and it doesn't need any. Every scene is real text on the page, inside a region labelled "Story narration", and system messages such as auto-save notices go out through live regions. Your screen reader takes it from there and passes the text along to your display.
One detail is worth knowing, though. While the narrator voice reads a scene aloud, I hide that scene's text from screen readers, because otherwise VoiceOver or TalkBack would read it straight over the top of the voice. Drag the narrator's Volume slider (it's under "Fine-tune audio settings") down to zero and the text comes right back for your screen reader, and for your braille display with it. Then read at your own speed. Nothing moves on until you pick something.
Braille users are also the reason I'm glad the page stays tidy. Raw JSON once leaked into the spoken narration, curly braces and all. It's long fixed, but it was a good reminder that whatever lands on the page is exactly what a braille reader gets under their fingertips.
Eye Tracking
Eye-tracking devices let players steer a pointer or select things with their gaze. A handful of games support eye tracking natively, and system-level software can map gaze onto ordinary mouse input.
The built-in options have become genuinely capable. Windows has an eye control feature for supported Tobii and EyeTech trackers that lets you control the mouse cursor and type on an on-screen keyboard, and you activate things by dwelling, which Microsoft describes as fixing your eyes on part of the screen for a set amount of time. Apple went a step further with Eye Tracking on iPhone, which uses the phone's built-in front-facing camera on supported models, with no extra hardware: a pointer follows your eyes, and holding your gaze steady performs a tap by default.
Best for: players with severe motor disabilities but good eye control. What games need: large targets, dwell-time selection, and no precision aiming.
There's no eye-tracking code in EchoQuest. Your tracker drives it the way it drives any web page, as a pointer, and EchoQuest asks very little of that pointer. The choice buttons stretch across the width of the panel, and there's nothing to aim at or react to in a hurry. Dwell timing comes from your eye-tracking software rather than from the game, so you can tune it to whatever feels comfortable.
Voice Input
Speech recognition turns spoken words into commands or text. It's increasingly built into operating systems and games. On Windows 11, for example, voice access lets people control the PC and write text using only their voice, and it does that without an internet connection.
Best for: players who can speak clearly but have limited hand use. What games need: natural language support or a voice-friendly command set.
Voice is where AI games really earn their keep. You can say "I climb onto the cart and shout for the crowd's attention" instead of rummaging through menus. EchoQuest's voice input uses the speech recognition built into your browser, so support depends on which browser you use, and for now it listens for US English. Short commands like "pick two", "where am I" or "save game" act straight away. A free-form action gets read back to you first and then sends itself after a few seconds unless you press Cancel, because a misheard "lizard" instead of "wizard" shouldn't cost you a turn.
Voice taught me some humility as well. At one point the microphone was blocked on my own pages, so voice input quietly did nothing at all until I tracked it down. Want the full picture? See Voice-Controlled Games: The Complete Guide.
One-Handed Keyboards and Mice
Specialised keyboards, programmable keypads and ergonomic mice help people who game one-handed. Macro software can squash several keys into a single press, and adaptive gear like the Microsoft buttons mentioned above can be programmed with macros too.
What games need: full keyboard remapping and minimal simultaneous key presses.
The Game Accessibility Guidelines call remappable controls "one of the best value accessibility features", and I agree with them. They point out that it helps people with motor impairments of very different kinds, from someone living with the effects of a stroke to someone with a broken arm. So here's where EchoQuest stands. The good news: every shortcut is a single key with no modifiers and no chords. Space or P pauses narration, the number keys pick a choice, U undoes your last turn, and nothing ever has to be held down. The gap: EchoQuest has no remapping screen of its own yet. If a key sits somewhere awkward for you, your keypad's software or your operating system's remapping tool is the way round it for now. That's a gap I'd like to close.
Screen Readers and Magnifiers
These are software, not hardware, but they're at the heart of blind and low-vision gaming. EchoQuest has skip links that jump straight to the audio controls or the action box, and its display settings cover high contrast, large text, reduced motion and a light theme. It also picks up the display preferences you've already set on your device, such as reduced motion or extra contrast, so you don't have to set them twice. For the details, see my guides on screen reader gaming and gaming with low vision.
What Makes a Game Assistive-Tech Friendly?
If you're sizing up a new game for your setup, these are the things I'd check first:
- Full input remapping
- No mandatory time pressure
- Few simultaneous inputs
- Real text exposed to the OS for screen readers and braille
- Large, clear interactive targets
- Standard keyboard navigation (Tab, Enter, arrow keys)
- Choice-based alternatives to free input
Notice how few of those cost a studio anything exotic. Most of them come down to building with standard parts and resisting the urge to put a timer on everything.
How EchoQuest Supports Assistive Tech
Here's the honest scorecard, based on what's actually in the game today:
- Fully keyboard-navigable with a logical focus order, which works with switch access and with external remapping tools (there's no in-game remapping yet)
- Suggested choices after every scene, three to five numbered buttons, for scanning and switch users
- Voice input for speech users, with free-form actions read back before they're sent
- Screen reader and braille support through semantic HTML and live regions, plus screen reader announcements when your HP or inventory changes
- No time limits on any decision, and single-step undo if you pick something you didn't mean to
- Large-text, high-contrast and reduced-motion options, plus a light theme
What's missing is direct controller support, as I said above. I'd rather list that plainly than let you buy an adaptive pad on the strength of a vague promise.
Everyone Deserves to Play
Assistive technology has come a remarkably long way, yet it only pays off when games are built to accept it. My aim with EchoQuest is simple: however you reach the world, you should be able to play. So what does your setup look like? If something in EchoQuest trips it up, tell me, because that kind of report is the most useful message I get.