How to make your application accessible (and keep it that way!)
summary
Shows concrete wins and costs: GitHub runs ax scanner across ~100 public domains and 2,000 pages, drops violations from ~18 to near zero on targeted runs, and spends single‑digit millions per year on an accessibility program. Uses system tests turned into keyboard‑only flows to catch bugs, a service catalog + codeowners mapping to give durable ownership, 60 trained Champions, plus paid consultants and annual ACRs; these measures scale and work.
AI-written summary · about
chapters (8)
- 0:00Introduction to accessibility
- 3:53Why accessibility matters
- 9:31Measuring accessibility
- 15:35Durable ownership with catalogs
- 21:57Lived experience and audits
- 30:47Keyboard testing and automation
- 35:22Challenges and the way forward
- 36:03Q&A
related talks
33mHow to make your application accessible (and keep it that way!)
45mAccessible by default
49mProgramming for Accessibility
24mAccessibility needs better marketing
54mAccessibility by everyone (and for everyone)
29mProgramming for Accessibility
01h 02mAccessibility - how to get the job done in a highly collaborative manner
28mEnterprise Grade Accessibility for Everyone