Programming for accessibility
summary
Argument: build accessibility from design not bolt-on, with concrete tooling and CI. Uses Accessibility Insights + its FastPass checks inside Chrome/Edge, runs tests in Azure DevOps pipelines, and demo site shows a missing alt fixed, committed and auto‑deployed so the pipeline catches regressions. Cites scale of need — 1 billion people with disabilities and persona spectrum examples that expand niche groups into ~21 million users — and shows AI work (DeepMoji training on ~55B tweets → 1.6B cleaned) and TensorFlow gesture controls that actually work.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 6:49Why accessibility matters now
- 7:11Inclusive design fundamentals
- 8:15Website accessibility standards
- 15:21WCAG compliance levels explained
- 19:21Perceivable content best practices
- 21:49Operable interface requirements
- 23:13Understandable design principles
- 24:37Robust and scalable solutions
- 26:46ARIA usage guidelines
- 28:09Demo accessibility tooling
- 34:15AI and emotional context awareness
- 40:11Building inclusive AI teams
- 43:22Summary and key takeaways
- 44:29Q&A session
