Building in accessibility for broader value to all
summary
Argues for pushing accessibility shift left into discovery, design and requirements rather than as an add‑on, citing WCAG 2.1 AA, 15% of the world (1.3 billion) classified as disabled, and the $13 trillion purple dollar market. Recommends starting with simple fixes (fonts, contrast, consistent layout), using Pa11y, Selenium and Google Lighthouse which cover 80% with automated tools, and testing with real users to reach the final 10–20%. Live phone captions plus real‑time translation demo works in practice.
AI-written summary · about
chapters (4)
- 0:00Start
- 5:13Key facts about accessibility
- 16:03Where to start? Web Content Accessibility Guidelines WCAG 2.1
- 21:35Testing - don't base on assumption
related talks
12mAccessibility-First Development: Making Applications Inclusive from Day One
57mHow (and why) to 'shift-left' your accessibility testing
42mAccessibility is for everyone, including you!
33mAccessibility needs to be the future of better technology
36mThe Human Side of Accessibility
29mHow to bring accessibility into your teams
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
44mDesigning with Accessibility in Mind
