You're only supposed to blow the bloody doors off!
summary
Shows that JavaScript and ARIA can help or break accessibility with concrete demos: VoiceOver NVDA JAWS and Narrator behavior is recorded, Twitter keyboard shortcuts collide with Windows screen readers, and an application role on the body disables most screen reader navigation. Presents working fixes—add roles, manage tabindex and keyboard handlers, use a roving tabindex for tabs—and previews the Accessibility Object Model phases that let scripts read and modify the accessibility tree. Live examples prove what fails and what actually works.
AI-written summary · about
chapters (14)
- 0:00Accessibility pitfalls in development
- 3:25Screen readers and web content
- 9:49Browser-screen reader interaction
- 16:25ARIA: when to use or avoid
- 24:17Dangers of ARIA application role
- 30:59Building accessible tab panels
- 32:46Accessibility Object Model future
- 33:34Q&A: Keyboard shortcuts for screen readers
- 36:04Q&A: Modifying Accessibility Object Model
- 36:25Q&A: Measuring screen reader usage
- 37:28Q&A: Screen readers in non-English
- 39:33Q&A: Screen reader behavior differences
- 41:46Q&A: Redundant ARIA roles
- 43:10Q&A: Headings and SEO myths
related talks
28mYou're only supposed to blow the bloody doors off!
31mBringing the Web Back to the Blind
31mThree Cheers for Keyboard Accessibility
40mWebsite Accessibility Examples That Hinder Accessibility
33mAccessibility Done Right
47mBuilding Accessible Web Components
41mWhat If We Talked About Web Accessibility?
26mAccessibleJS