How to make your application accessible (and keep it that way!)
summary
Industry estimate of ~70% inaccessible sites prompts concrete moves at GitHub: run axe automated scanner across ~100 domains, reporting to DataDog and erblint; convert system tests to keyboard-driven flows to catch screen‑reader bugs; catalog ~2,000 pages into a service catalog with scorecards covering ~220 services and on‑call ownership; train champions who close ~450 issues; hire external audits (Prime Access Consulting); spend roughly $5–10M/year. Measured reductions (e.g., 18 homepage violations, 1,800 total) drive funding and enforcement.
AI-written summary · about
chapters (11)
- 0:00Accessibility introduction
- 3:16Scaling accessibility
- 9:16Accessibility investment principles
- 10:40Measuring accessibility progress
- 15:00Maintaining accessibility
- 18:49Ownership systems
- 21:14Lived experience in testing
- 26:09Legal considerations
- 27:13Practical accessibility testing
- 30:46Leadership for accessibility
- 31:29Call to action
related talks
43mHow to make your application accessible (and keep it that way!)
43mHow to make your application accessible (and keep it that way!)
14mAccessible Accessibility
28mEnterprise Grade Accessibility for Everyone
54mAccessibility by everyone (and for everyone)
34mBuilding Accessible Careers
53mAccessing Accessible Accessibility
21mPrevent, Catch and Fix Accessibility Issues