Embedding Accessibility
summary
Argues that accessibility must be embedded early by building a diverse inclusive culture and shifting left in product lifecycles, citing concrete wins: progressive enhancement lets a login redesign reach 1300 user agents and finish at half time and half budget, retrofitting later takes twice as much time, and accessible products open markets to 1.3 billion people; recommends tools like Accessibility Insights and Axe, CI checks (AXS), Figma plugins, and sensible metrics (cost per accessibility bug, revenue upside like WhatsApp’s cross‑platform growth).
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker background
- 4:24Early web experiences shaping views
- 10:27Disability as design mismatch
- 17:15Diverse teams and market opportunities
- 23:13Costs of reactive accessibility
- 25:42Embedding accessibility early
- 32:03Accessibility as ongoing journey
related talks
45mAccessibility at all stages
12mAccessibility-First Development: Making Applications Inclusive from Day One
28mBuilding in accessibility for broader value to all
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
42mAccessibility is for everyone, including you!
29mHow to bring accessibility into your teams
48mProgramming for accessibility
15mBeyond Compliance Creating Inclusive and Usable Digital Products