> Markdown version of [/videos/100638-when-the-screen-reader-is-the-main-character?t=1455](https://www.wearedevelopers.com/videos/100638-when-the-screen-reader-is-the-main-character?t=1455). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # When the Screen Reader is the Main Character Imagine solving a crime mystery where your screen reader is the primary investigative weapon and pixel art is purely optional. See how building a TypeScript game for a blind detective exposes common DOM, focus, and ARIA pitfalls. - **Speakers:** Adrián Bolonio - **Event:** HalfStack Vienna 2026 - **Published:** November 19, 2026 - **Duration:** 26:49 - **URL:** https://www.wearedevelopers.com/videos/100638-when-the-screen-reader-is-the-main-character - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/06c0723817027ee987e9582128056bb0/thumbnails/thumbnail.jpg?time=30000ms ## Summary Most web applications treat accessibility (a11y) as an afterthought, designing around graphics first and sprinkling ARIA attributes in right before launch. However, because "no ARIA is better than bad ARIA," developers need a fundamental shift toward designing directly for screen readers from the very beginning. By combining Agatha Christie-style crime mysteries with classic point-and-click mechanics, an open-source educational game puts the player in the shoes of a blind detective where the screen reader is the primary investigative weapon. In this architecture, the text in the DOM *is* the game, and pixel art serves purely as an optional visual overlay that never adds or removes clues. Screen readers like Apple's VoiceOver, Windows Narrator, and the open-source NVDA do not read pixels; they interpret the browser's accessibility tree generated from semantic HTML. A common developer pitfall is confusing basic keyboard navigation—tabbing sequentially through interactive elements—with actual screen reader navigation. Screen reader users rely heavily on tools like the VoiceOver rotor to scan pages by headings (`h1`, `h2`), semantic landmarks, and explicitly named controls. Replacing vague labels like "click here" or "next" with descriptive accessible names like "examine the heavy footsteps" ensures the element's name, role, and state provide complete context without visual cues. Under the hood, the game's engine is built with pure TypeScript, using a state reducer and `localStorage` to map actions to simple JSON episode files without relying on spatial coordinates. Supporting both visual and screen reader modes requires careful DOM manipulation; for instance, a visual typewriter text effect will cause chaotic, letter-by-letter audio announcements unless separated from an `aria-live` region configured with `aria-atomic="true"`. Furthermore, hiding visual elements in screen reader mode requires visually hidden CSS patterns rather than `display: none`, which strips elements from the accessibility tree entirely. Managing focus is equally critical, requiring programmatic focus retention when moving between rooms and utilizing `tabindex="-1"` to reset focus to main headings during route changes. Developers can apply these same investigative mechanics to their own products by going "undercover" with a screen reader for ten minutes. Using the rotor to jump through headings and landmarks quickly reveals structural gaps, while tracking focus across route changes exposes context loss in complex views like dashboards or e-commerce checkouts. Developers should also "listen for the silences"—visual DOM updates like cart additions or deleted items that fail to trigger live region announcements—and ensure the HTML `lang` attribute is accurately set so screen readers load the correct localization grammar and pronunciation. **Keywords:** web accessibility a11y, screen reader navigation, semantic html structure, browser accessibility tree, apple voiceover rotor, nvda screen reader, aria live regions, aria-atomic attribute, focus management in spa, tabindex minus one, accessible element names, visually hidden css, typescript game engine, html lang attribute, multilingual internationalization i18n, accessibility testing techniques ## Chapters 1. **Combining crime fiction with accessibility to educate developers** (00:01) — Teaching screen reader usage through traditional documentation is often dry, so building a multilingual point-and-click detective game provides an engaging way to learn accessibility. 1. **Designing for accessibility first instead of visual overlays** (02:48) — Treating accessibility as an afterthought leads to poor user experiences, whereas embedding every game clue directly in the DOM ensures visual graphics remain strictly decorative. 1. **How screen readers interpret the DOM and accessibility tree** (04:50) — Screen readers cannot interpret visual pixels, requiring developers to provide explicit accessible names, roles, and states within the HTML to construct a meaningful accessibility tree. 1. **Distinguishing between keyboard navigation and screen reader navigation** (07:23) — While keyboard navigation relies on the tab key to move between interactive controls, screen reader users scan pages using semantic headings and landmarks. 1. **Live demonstration of playing the game with VoiceOver** (08:42) — Navigating an interface without visual cues requires using screen reader tools like the VoiceOver rotor to scan landmarks, headings, and action buttons. 1. **Building a data-driven game engine with TypeScript and JSON** (15:18) — Decoupling game logic from visual coordinates allows episodes, rooms, and clues to be defined entirely as JSON data mapped by pure TypeScript functions. 1. **Managing semantic HTML, live regions, and keyboard focus** (20:15) — Dynamic text effects and route changes can confuse assistive technologies, which is solved by implementing ARIA atomic live regions, programmatic focus management, and proper CSS hiding techniques. 1. **Auditing your own web applications using a screen reader** (24:15) — Developers can uncover hidden usability flaws in their own products by navigating exclusively with a screen reader to verify heading structures, focus tracking, live announcements, and language attributes. ## Related Moments - [Navigating cross-browser screen reader compatibility and testing](https://www.wearedevelopers.com/videos/1313-wearedeveloper-live-accessibility-in-the-eu-css-gaps-and-forms-with-emma-dawson) (from "WeAreDeveloper Live: Accessibility in the EU, CSS Gaps and forms with Emma Dawson") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/b1f7d2ecb121e5d8518ece99fe93241e/thumbnails/thumbnail.jpg?time=131215ms - [Evaluating user experience through screen readers and landmarks](https://www.wearedevelopers.com/videos/507-decoding-web-accessibility-through-audit) (from "Decoding web accessibility through audit") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/f05f03fffb8d14f982b3a58a87a8fb89/thumbnails/thumbnail.jpg?time=17400ms - [Browser rendering process and the accessibility tree](https://www.wearedevelopers.com/videos/1674-semantic-html-means-it-s-semantic-right-right) (from "Semantic HTML means it's semantic, right? Right?") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/bec28923b8a541a69f0f8274b17dd558/thumbnails/thumbnail.jpg?time=64635ms - [Practical strategies for enforcing accessibility in AI tools](https://www.wearedevelopers.com/videos/100568-vibe-coding-accessibility) (from "Vibe Coding Accessibility") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/45c1943effd8835713f1e7d628e8644e/thumbnails/thumbnail.jpg?time=134576ms - [Handling screen reader simulations using AI agents](https://www.wearedevelopers.com/videos/100170-continuous-accessibility) (from "Continuous Accessibility") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/f0019fd7fdd872506cf63f528f238a60/thumbnails/thumbnail.jpg?time=69047ms - [Testing interfaces with system screen readers](https://www.wearedevelopers.com/videos/1289-wad-live-22-01-2025-exploring-ai-web-development-and-accessibility-in-tech-with-stefan-judis) (from "WAD Live 22/01/2025: Exploring AI, Web Development, and Accessibility in Tech with Stefan Judis") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/ce0450c05adc9ec3f4c9a22227d4f5ea/thumbnails/thumbnail.jpg?time=286945ms ## Related Articles - [Dev Digest 112 - The True Crime of AI Development](https://www.wearedevelopers.com/magazine/421-dev-digest-112-the-true-crime-of-ai-development) - [3 JavaScript-Free Techniques for Accordions, Dialogs, and Table of Contents](https://www.wearedevelopers.com/magazine/684-3-javascript-free-techniques-for-accordions-dialogs-and-table-of-contents) - [Dev Digest 123 - Easy as A, B, C1](https://www.wearedevelopers.com/magazine/459-dev-digest-123-easy-as-a-b-c1) - [Dev Digest 105 - Security First](https://www.wearedevelopers.com/magazine/393-dev-digest-105-security-first) ## Related Jobs - [Senior Web Software Architect, AI Experiences](https://www.wearedevelopers.com/jobs/ext/4523834-senior-web-software-architect-ai-experiences) at **TeamViewer Germany GmbH** - [Senior Frontend Engineer](https://www.wearedevelopers.com/jobs/ext/4665402-senior-frontend-engineer) at **Almedia** - [Software Development Engineer 4 - Database Engineer](https://www.wearedevelopers.com/jobs/48591-software-development-engineer-4-database-engineer) at **WEX** - [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/3929243-staff-developer-advocate-github-security-lab) at **GitHub** - [Senior Engineer, Game Mathematician](https://www.wearedevelopers.com/jobs/48550-senior-engineer-game-mathematician) at **Sportradar Media Services GmbH** - [Principal Software Engineer, Copilot Code Review](https://www.wearedevelopers.com/jobs/ext/3926064-principal-software-engineer-copilot-code-review) at **GitHub**