The Things Nobody Tells You About Building a Successful Accessibility Program
summary
Concrete tactics and outcomes: automation finds about 40% coverage of accessibility issues so experts must fill the rest; a single engineer builds a complete accessible Yahoo Mail iOS in six weeks after pairing with accessibility guidance; an offsite accessibility lab demo convinces execs and unlocks funding and VP support; build internal tooling for scale, expect staffing ratios from one‑to‑10 up to one‑to‑1000, and pair community testing with big bets like VoiceOver and automated alt text.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 2:01Adapting to company culture
- 8:33Doing more with less
- 10:11The power of hero products
- 13:35Getting work done versus belief
- 15:48The role of automation
- 17:57The impact of good demos
- 20:47Engaging the community
- 23:50Measuring real progress
- 29:25Success without presence
- 34:39Leaving a lasting legacy
- 39:41Q&A and closing thoughts
related talks
50mHow to Build an Accessibility Program and Culture
28mBuilding an Accessibility Culture, One Step at a Time
26mHow (Not) to Fail at Accessibility
42mThings I Wish I Knew When I Started in Digital Accessibility
38mHow to set up an accessibility program in an imperfect world
14mAccessible Accessibility
49mProgramming for Accessibility
45mTips from the Trenches: Accessibility Testing