HalfStack Vienna 2026 • Nov 19, 2026

When the Screen Reader is the Main Character

Adrián Bolonio

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.

Starting at 24:15 · Watch from the beginning

Pause
Mute Enter Fullscreen
#1 about 3 min

Combining crime fiction with accessibility to educate developers

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.

#2 about 3 min

Designing for accessibility first instead of visual overlays

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.

#3 about 3 min

How screen readers interpret the DOM and accessibility tree

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.

#4 about 2 min

Distinguishing between keyboard navigation and screen reader navigation

While keyboard navigation relies on the tab key to move between interactive controls, screen reader users scan pages using semantic headings and landmarks.

#5 about 7 min

Live demonstration of playing the game with VoiceOver

Navigating an interface without visual cues requires using screen reader tools like the VoiceOver rotor to scan landmarks, headings, and action buttons.

#6 about 5 min

Building a data-driven game engine with TypeScript and JSON

Decoupling game logic from visual coordinates allows episodes, rooms, and clues to be defined entirely as JSON data mapped by pure TypeScript functions.

#7 about 4 min

Managing semantic HTML, live regions, and keyboard focus

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.

#8 about 3 min

Auditing your own web applications using a screen reader

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.

Matching moments

4:33 min

Navigating cross-browser screen reader compatibility and testing

Emma Dawson Emma Dawson · LIVE

4:26 min

Evaluating user experience through screen readers and landmarks

Anuradha Kumari · World Congress 2022

1:38 min

Browser rendering process and the accessibility tree

Emma Dawson Emma Dawson · World Congress 2025

2:30 min

Practical strategies for enforcing accessibility in AI tools

Karl Groves Karl Groves · World Congress 2026 North America

1:21 min

Handling screen reader simulations using AI agents

Jörg Jakoby Jörg Jakoby · World Congress 2026 Europe

3:21 min

Testing interfaces with system screen readers

Upcoming sessions on this topic

Starts in 6 days

Conference India 2026

November 25–26, 2026

Bengaluru, India