Accessibility-First Development: Making Applications Inclusive from Day One
summary
WHO estimates 1.3 billion people have disabilities, so building accessibility from day one reduces expensive rework, increases reach and prevents lawsuits (Gimlet Media, MIT/Harvard, Target, Domino’s cited). Practical steps include embedding WCAG AA criteria in design systems and Jira definitions of done, running Lighthouse audits plus Figma and IDE plugins, and adding unit/integration tests with screen readers. Example: live-stock countdowns create harmful time pressure for users with ADHD, so remove or make them optional.
AI-written summary · about
chapters (14)
- 0:00Accessibility-first development
- 1:04Why accessibility matters
- 2:10Ethics, law, and business
- 2:53Common accessibility barriers
- 4:16Cognitive and sensory inclusivity
- 4:37Accessibility in workflows
- 5:21WCAG guidelines explained
- 6:27Perceivable content and assistive tech
- 6:49Operable functionality
- 7:29Clear content design
- 8:10Robust device compatibility
- 8:50Accessibility tools
- 9:33Success stories
- 9:55Conclusion
related talks
28mBuilding in accessibility for broader value to all
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
29mAccessibility first is the new Mobile first
25mBuilding empathy and accessible apps
32mBuilding Empathy and Accessible Apps
29mHow to bring accessibility into your teams
33mAccessibility needs to be the future of better technology
42mArchitecting for Accessibility