Accessible by default
summary
GitHub makes a concrete claim: a 15‑year‑old, 1,400‑controller Ruby on Rails monolith becomes more accessible by adding specific tools and patterns. It runs automated accessibility scanning (Axe in CI, plus custom rules and Playwright checks) against every deploy, builds an accessibility‑first form builder so labels are generated by default, and adopts preview‑driven development (Lookbook/primer previews used in tests) to catch and fix real regressions rather than rely on vague guidelines.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:21What accessibility means
- 8:28GitHub’s accessibility challenges
- 11:13GitHub’s culture shift
- 13:19Inclusive technology commitment
- 14:20Automated scanning with Axe
- 21:01Accessible Rails forms
- 27:49Preview driven UI development
- 32:44Universal Design blind spots
- 37:56Empathy and unknowns
- 39:00Q&A
related talks
42mAccessible by default
43mHow to make your application accessible (and keep it that way!)
53mAutomating Accessibility Assurance
43mHow to make your application accessible (and keep it that way!)
28mEnterprise Grade Accessibility for Everyone
27mContinuous Accessibility
56mAccessibility Testing 101
50mShift Left on Accessibility: Beyond the Audit