Chrome Dino Accessibility: One-Hand and Switch Control

The Chrome Dino game looks like a two-input game — jump and duck, that’s the whole vocabulary. That simplicity is also what makes it one of the most accessible browser games out there. With the right setup, you can play with one finger, one switch, a sip-and-puff device, or assistive software that maps any custom gesture to a key press. Here’s a practical look at chrome dino accessibility, what works out of the box, and where the gaps are.

The input model is the accessibility win

Before talking about specific assistive setups, the headline: the Chrome Dino game uses two inputs and no menus. There’s nothing to click through, no settings, no multi-finger gestures, no quick-time events. To start a run, you tap or press once. To play, you press jump or duck. To restart after a game-over, you press jump again.

That’s a remarkably accessible design surface. Any input device that can produce a discrete key press or screen tap can run the game. The challenge isn’t access — it’s reaction time, which depends on how quickly your input setup translates intent to a registered press.

One-handed play on desktop

The default keys are space, up arrow, and down arrow. With one hand, you can comfortably reach all three from a resting position over the right side of a keyboard. The most common one-handed grip is thumb on space, index on up arrow, middle on down arrow. The reachability is fine.

If you want a more compact setup, remap the keys. Chrome Dino itself has no key-binding UI, but the open-source code is straightforward to fork, or you can use a keyboard remapping tool (Karabiner-Elements on macOS, AutoHotkey on Windows) to map any keys to the game’s listeners. Common alternatives include using number keys (1 to jump, 2 to duck) or a mouse button bound to jump via the same remap tools.

One-handed play on mobile

Mobile is even simpler. Tap anywhere to jump, press and hold to duck. The entire play area is the input zone, which means you can play with any single finger or thumb anywhere on the screen. There’s no second hand required at any point in the game.

For users with limited fine motor control, the large input zone is forgiving — you don’t need to hit a small button. Anywhere on the play area counts.

Switch control

Both iOS and Android ship with switch control built into the OS. The setup pairs a physical switch (anything from a large accessibility button to a sip-and-puff device) with a configured action — usually a screen tap at a specific location, or a key event. For the Chrome Dino game, the configuration is simple: map one switch to “tap center of screen” for the jump input. That single binding is enough to play.

For users who want both jump and duck via switches, the standard configuration is two switches: one for tap (jump) and one for press-and-hold (duck). Most switch-control setups support this with a second switch or a long-press gesture.

On desktop, similar setups are available through OS-level accessibility settings (Switch Control on macOS, Switch Access on Chromebooks, third-party software on Windows). The same logic applies: map one switch to space, optionally a second to down arrow.

Screen reader compatibility

This is where the game’s accessibility story has a real gap. The Chrome Dino game is canvas-rendered — the dino, the cacti, the score, all drawn into an HTML5 canvas element. Screen readers (VoiceOver, NVDA, JAWS) can’t introspect canvas contents the way they can introspect text or semantic HTML. There’s no announcement of “cactus approaching” or “pterodactyl at middle height” because the game doesn’t expose that data to the accessibility tree.

What screen readers can do: they’ll announce that you’ve reached the offline page, and they’ll read any surrounding page text. But the actual gameplay is fundamentally visual, and there’s no audio mode that translates obstacles into sound cues.

A few community-built accessibility forks have tried to address this — adding spatial audio cues that beep when an obstacle enters a certain distance — but none are official and none have been integrated into the canonical T-Rex Runner. It’s an open opportunity for the community.

Color and contrast

The Chrome Dino game uses high-contrast pixel art on a light background. The day-to-night palette flip switches to white-on-dark, which is also high-contrast. There’s no built-in option to force one palette or the other, but the contrast in both modes is well above accessibility minimums for game graphics.

Players who experience motion sensitivity or visual fatigue from the scrolling background should note that the scroll speed accelerates throughout a run. There’s no “slow mode” or motion-reduction option in the official game. The cap on maximum speed (which we cover in our piece on the speed limit) provides an upper bound, but the late-game scroll is fast by design.

Custom hardware

The Xbox Adaptive Controller, the Logitech Adaptive Gaming Kit, and similar hardware all work with the Chrome Dino game as long as the host OS recognizes the inputs as keyboard or mouse events. Most adaptive controllers can be configured to emit a space key for the primary button, which is all the game needs. The two-input model means even minimal adaptive setups are sufficient.

Eye-tracking input is another option. Tools like Tobii Eye Tracker, paired with software that maps gaze dwell to a key press, give a hands-free way to play. The latency is meaningfully higher than keyboard input, so high-score runs are tough, but casual play works.

Practicing input timing

For any assistive setup, the bottleneck is reaction time. The Chrome Dino game’s late game gets fast, and any added latency from a switch, an adaptive controller, or an eye tracker shrinks your dodge window. The good news: the early game is forgiving, and you can build comfort with the rhythm before pushing into difficulty. For a structured way to get the muscle memory in, see our Chrome Dino warm-up drills — they translate directly to any input method.

The source code makes everything possible

One reason the Chrome Dino game has so many accessibility options is that it’s open under a BSD-3 license. Anyone can fork it and add custom input handlers, alternate color palettes, audio cues for obstacles, or larger sprite sizes. The canonical source is in the Chromium tree, with a community mirror at github.com/wayou/t-rex-runner. If you have a specific accessibility need that the default game doesn’t meet, the code is short enough to read in an afternoon.

Frequently asked questions

Can you play Chrome Dino with one hand?

Yes. The desktop game uses three keys (space, up arrow, down arrow) that all sit within one-hand reach. The mobile game needs only single-finger taps and presses. Many players go further by remapping inputs to a more compact set.

Does Chrome Dino work with switch control?

Yes. The game’s two-input model maps cleanly to one or two assistive switches. On iOS and Android, OS-level switch control can emit the necessary taps. On desktop, the same is true through macOS Switch Control, Chromebook Switch Access, or third-party Windows tools.

Is Chrome Dino accessible to screen readers?

Partially. The game is canvas-rendered, so screen readers can’t read obstacles or the score in real time. They can announce that you’ve reached the offline page and read surrounding text. There’s no built-in audio mode that translates gameplay events into sound cues.

Can you change the controls in the Chrome Dino game?

There’s no in-game remapping option. To change controls, use an OS-level keyboard remapping tool (Karabiner-Elements, AutoHotkey, Chromebook key remapping) or fork the open-source code and edit the input handler directly.

Is the Chrome Dino game color-blind friendly?

The game uses high-contrast pixel art — dark sprites on a light background by day, light sprites on dark by night. Contrast is well above accessibility minimums in both palettes, and the gameplay doesn’t depend on color recognition (you respond to obstacle shape and position, not color).

The takeaway

The Chrome Dino game wasn’t designed as an accessibility showcase, but its minimalism gave it accessibility almost by accident. Two inputs, one canvas, no menus — everything an assistive setup needs to translate into. Switch users, one-handed players, eye-tracker users, and adaptive controller users can all play it without modification. The biggest gap is screen reader support, and that’s a community opportunity waiting for a fork. Try your own setup on the T-Rex Runner and see how it handles.

Related: How to Play Chrome Dino on iPhone (Browser & Workarounds) · How the Pterodactyl Works in Chrome Dino · How to Play Chrome Dino on Android Phones