Keyboard Navigation in EchoQuest: Play Without a Mouse

Whether you're a keyboard power user, a blind player using a screen reader, or someone whose mouse just broke ten minutes before a session, EchoQuest is designed to work completely without one. Every feature is reachable by keyboard. Every action is triggerable by shortcut. There is no place in the game — main menu, world library, character creation, active session, settings, account management — where you'll be forced to grab a mouse to make progress. We test that promise constantly, including with users who literally cannot use a mouse, and we treat any keyboard trap as a release-blocking bug.

This post is the complete reference for keyboard players. We cover the basics first (tab, focus, escape), then in-game shortcuts during a session, then the screen-reader integration story, and finally power-user tricks that experienced keyboard players love. If you're brand new to keyboard-first navigation, the first section is everything you need; the rest you can pick up over your first few sessions.

The Core Navigation Model

EchoQuest follows standard web accessibility patterns, so if you know how to navigate a webpage by keyboard, most things will feel familiar:

• Tab moves focus forward through interactive elements
• Shift+Tab moves focus backward
• Enter or Space activates the focused button or link
• Escape closes modals and dismisses overlays
• Arrow keys move within compound widgets (lists, sliders, tab panels)

Focus is always visible — there's a clear highlight ring around whichever element is active. We chose a high-contrast indicator that meets WCAG 2.2's focus-visible criterion, so it remains visible against every background colour in the app, including the dark theme. Sighted keyboard users sometimes complain that focus rings are "ugly"; ours is intentionally noticeable so blind-with-residual-vision players and motor-disabled players who navigate slowly never lose track of where they are.

The tab order is logical, not visual. Reading order goes top-to-bottom, left-to-right within a section, then forward to the next section. We deliberately don't use CSS tricks that would visually rearrange content without rearranging the DOM, because that desynchronises tab order from what's on screen. If you ever encounter a place where tab order seems wrong, that's a bug — please report it.

In-Game Shortcuts

During a play session, these shortcuts let you act quickly without reaching for a mouse:

Key	Action
1, 2, 3	Select choice 1, 2, or 3
T	Focus the text input to type a custom action
Enter	Submit your action
R	Replay the last narration
Space	Pause / resume TTS narration
↑ / ↓	Adjust narration volume
M	Toggle ambient sound on/off
?	Open the keyboard shortcuts help overlay
Esc	Close any open menu or dialog

A few notes on the design choices behind these:

The number keys for choices were chosen because they're consistent across keyboard layouts worldwide and don't conflict with screen reader pass-through modes. The "T" for text input is intentionally a single letter so switch users (who often map a single key to "type") can engage the input in one keystroke. The "R" for replay is one of the most-used keys in screen-reader sessions — re-listening to narration is the equivalent of re-reading a paragraph for sighted players, and we made it a single keypress for that reason.

The shortcut overlay (?) is your safety net. If you ever forget what key does what, press ? from anywhere in the app and you'll get an accessible dialog listing all current shortcuts. The dialog itself is fully keyboard-navigable and announces its content to screen readers automatically.

Screen Reader Compatibility

EchoQuest is tested with NVDA, JAWS, and VoiceOver, with regular smoke tests on TalkBack (Android) and Orca (Linux). Key accessibility features:

• All game text is rendered as semantic HTML, not images, so screen readers can read it natively
• Narration log entries are marked as ARIA live regions so screen readers announce new content automatically as the AI GM responds
• Choice buttons have descriptive labels (not just "Option 1") — they include the actual choice text, so a screen reader user gets the same information as a sighted player
• Status changes — HP updates, inventory changes, location shifts — are announced via a screen reader-only live region (using a polite ARIA live setting), so they don't interrupt the main narration
• Heading structure is consistent: each scene opens with a level-2 heading announcing the location, so screen reader users can navigate by heading like they would on a well-structured webpage
• Form fields have visible and programmatically associated labels (no placeholder-only inputs)

The result: a screen reader user playing EchoQuest hears the narration, knows when their HP changes, can hear what choices are available, and can act on them, all without ever leaving their preferred screen-reader rhythm.

The Skip Link

At the top of every page, before any navigation, there's a hidden skip link that becomes visible on focus: "Skip to main content." This lets screen reader and keyboard users jump straight to the game area without tabbing through the nav bar on every page load. It's the single most useful accessibility feature on the site for repeat visitors — once you know it's there, you'll use it constantly.

If you're a sighted user who has never noticed the skip link, that's intentional; it's positioned off-screen visually until it receives focus, then it pops into view at the top-left. Tab from the address bar on any EchoQuest page and it's the very first thing you'll hit.

Setting Up Your Preferred Voice

If you're using a system screen reader alongside EchoQuest's built-in TTS, you may want to mute the browser TTS to avoid double-narration. Go to Settings → Voice and set TTS Provider to "Off" — the screen reader will then read game text through your preferred voice. This is the configuration most blind players who use NVDA or JAWS prefer, because it keeps narration consistent with the rest of their browsing experience and respects whatever voice rate they've already trained themselves to listen at.

If you're not using a system screen reader, the built-in TTS gives you ElevenLabs-quality narration on paid tiers and a clean browser-TTS fallback on free. Either way, narration speed is adjustable in two-step increments from 0.7× to 2.0×. Most experienced screen reader users will turn EchoQuest's narration off entirely and let their own screen reader handle text, then enable our ambient sound layer separately for atmosphere.

Tips for Power Users

• Keep the game in a dedicated browser tab and use your browser's tab shortcut (Ctrl+Tab / Cmd+Option+arrow) to switch back without losing focus position. EchoQuest preserves focus across re-entry, so coming back from another tab puts you exactly where you left off.
• Use browser zoom (Ctrl+plus / Cmd+plus) to increase text size without affecting the game layout. We use relative units throughout, so zoom up to 200% and the layout still works.
• The text input field supports standard browser editing shortcuts — Home/End, Ctrl+A, Ctrl+Z for undo, Ctrl+Backspace to delete the previous word. If you write long custom actions, those shortcuts make a real difference.
• If you're on a screen reader, use heading navigation (H key in NVDA/JAWS, Ctrl+Option+Cmd+H in VoiceOver) to jump between scene transitions in a long log
• The R key replays the last narration. We hear from blind players that this is the most-used keyboard shortcut on the entire site — it's the audio equivalent of re-reading a sentence
• If a session feels stuck, Tab through the game area to find the focused choice or text field. Sometimes focus has landed somewhere unexpected after a slow network response

Reporting Issues

If something doesn't work for you with the keyboard or your screen reader, please tell us. We treat every accessibility report as a release-blocking bug. The fastest channel is the contact link in the footer of every page. Include the browser, screen reader, and the exact action you were trying to take. We respond to every message.

EchoQuest is built on the principle that accessibility isn't a separate experience — it's the same experience, available through whatever input modality you prefer. Keyboard-only play isn't a "lite" version of the game. It's the same world, the same AI GM, the same stories, reached through different keys. Start playing →