Accessibility in the Enterprise: The Relationship of A11y and ROI
summary
Argues that following WCAG Level AA is the practical defense and target, notes 2,000+ lawsuits in 2020 and examples of six-figure settlements (one cited at $66.6M), warns that overlays don't fix underlying code and usually do more harm than good, shows testing workflow using axe-core and Lighthouse plus manual checks with NVDA/VoiceOver and a "no-mouse day," reports automated tools only catch ~20–50% of issues, and urges color-contrast, alt attributes, keyboard and screen‑reader verification.
AI-written summary · about
chapters (10)
- 0:00Introduction and opening
- 6:10What is accessibility?
- 13:20Understanding A11y and numeronyms
- 18:16Why accessibility matters
- 24:39Consequences of inaccessible design
- 32:49Accessibility and ROI
- 37:02The problem with overlays
- 39:32Testing for accessibility
- 42:04Reflecting on your why
- 48:49Closing and resources
related talks
41mAccessibility is a Requirement
53mThe Human Side of Accessibility
45mAccessibility: Why You Should Learn About WCAG
33mAccessibility needs to be the future of better technology
38mWeb Accessibility Deep Dive
01h 03mAccessibility: Making your websites more inclusive
07mAccessibility Through the Eyes of Users
28mBuilding in accessibility for broader value to all