Killing accessibility with five words
summary
Five words on Twitter — "Your framework is not accessible" — drive a developer away from accessibility, so the talk argues for concrete, framework-specific help instead. Cites npm and usage scale (React ~55M downloads, Angular ~18M, Vue ~8M) and a CSS poll of ~15,000 responses where only 43% answered correctly. Shows a working WAI-ARIA tab built as a reusable accessible React component (257 lines) and announces an npm library Tenon UI to package and reuse tested accessibility fixes.
AI-written summary · about
chapters (16)
- 0:00Start
- 4:23I come from a science background
- 6:32Development meant hard work to stay relevant
- 8:12Unexpected "attacks" from ally folk
- 16:59Frameworks and libraries
- 19:45Who uses Vue
- 20:47What are the current challenges?
- 22:43Inaccessible docs examples
- 23:16Lack of articles on accessibility in Frameworks
- 23:51Lack of accessible UI
- 24:10Accessibility easily gets hard in JS apps
- 24:57Careless comments from those who reach many
- 25:25Putting my money where my mouth is
- 25:46Frameworks work because they
- 29:13What makes an accessible tabbed interface?
- 34:07The resulting abstraction
related talks
34mBuilding Accessible Web Apps in React
31mHow to Be an A11Y - Creating Accessible React Apps
25mBuilding Inclusive Web Experiences: Web Accessibility in ReactJS
32mBuilding Empathy and Accessible Apps
52mMaking Single Page Apps Accessible: It's easier than you think
46mUpstream Accessibility: A Contributor's Guide
01h 00m60 Minutes to Accessibility
01h 07mA web for anyone, anywhere, anytime