You're only supposed to blow the bloody doors off!
summary
Clear examination of concrete accessibility traps: why Windows screen readers gobble keystrokes and break JavaScript letter shortcuts, how rebuilding buttons and links with spans or ARIA requires extra keyboard scripting, the surprise that role=application disables native navigation and that roving tabindex plus arrow-key handling is essential for tab panels, plus a warning about the Accessibility Object Model (AOM) now in Chrome behind a flag and its power to both fix and further confuse real-world assistive workflows.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:25What Are Screen Readers Do
- 5:14Virtual Buffer
- 6:24What Happens When a Website Provides Javascript Shortcuts
- 8:25How Screen Readers and Browsers Work Together
- 9:30Platform Accessibility Api
- 11:40Accessibility Tree
- 19:15Break Native Semantics
- 20:30Keyboard Accessibility
- 22:18Interactions
- 24:11Tab Lists
- 26:27The Accessibility Object Model
related talks
45mYou're only supposed to blow the bloody doors off!
31mThree Cheers for Keyboard Accessibility
47mBuilding Accessible Web Components
41mWhat If We Talked About Web Accessibility?
27mTime Traveller's Guide to Accessibility Mechanics
41mTales of Accessibility Failures
31mBringing the Web Back to the Blind
33mAccessibility Done Right