Accessible by default
summary
GitHub makes a concrete claim: a 15‑year‑old, 1,435‑controller Rails monolith with ~2,000 screens becomes more accessible by embedding axe in dev and CI to fail builds, using Playwright for fast checks, and shipping an accessibility-first form builder that generates labels so WCAG 4.1.2 (labels) is effectively impossible to break. Preview tooling and preview-driven development (Lookbook + render/visit previews) drive repeatable component tests and discoverability; hundreds of components get automated scans and regressions catch before deploy.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:01What accessibility means
- 7:09GitHub’s scale and culture
- 12:25Automated accessibility scanning
- 17:25Building accessible forms
- 23:26Preview driven UI development
- 29:07Universal Design blind spots
- 32:18Q&A
related talks
45mAccessible by default
43mHow to make your application accessible (and keep it that way!)
53mAutomating Accessibility Assurance
24mAutomated Visual Regression & Accessibility Testing
28mEnterprise Grade Accessibility for Everyone
35mAutomated Accessibility Testing
29mBuilding Accessibility Testing into Your Workflow
33mAutomated Accessibility Testing