Why We Never Get to Web Accessibility 102
summary
Shows that 19% of Americans identify as having a disability while tech companies report numbers like Slack 1.7% disabled workforce, explains NVDA as an open source screen reader you can patch, points to WCAG and WCAG 2.1, recommends automated linting, keyboard-only days, transcripts and image descriptions, and warns of legal risk under California’s Unruh Act with monetary damages up to $5,000 per infraction — concrete steps, tools, and hard numbers rather than vague slogans.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:35Disabled People Use Your Website!
- 7:46Ableism
- 12:26Whet Our Companies and Teams Prioritize
- 15:37What We Prioritize as Developers
- 17:51Structural Problems
- 21:45At the Society Level
- 25:56At the Company Level
- 29:01At the Team Level
- 31:25At the Personal Level
- 35:36Resources!
related talks
50mAccessibility in the Enterprise: The Relationship of A11y and ROI
37mAccessibility Matters: Creating a Better Web
41mAccessibility is a Requirement
33mWeb Accessibility: Why, How and What?
43mWhat is accessibility, and why I should care?
46mThis Talk Has Been Disabled
53mThe Human Side of Accessibility
25mBuilding empathy and accessible apps