How to bring accessibility into your teams
summary
Argues that accessibility must be in the definition of done and shift left rather than an afterthought, backing that with audits, Lighthouse/axe/wave/ARC scans and screen‑reader checks (and devtools emulation), citing surprising numbers—about 20% of working‑age people report a disability and colourblindness affects ~1 in 12 men—and real outcomes: audit reports, backlog tickets, coaching, an accessible alt site (Tesco) and NHS moving from 53% to 98% WCAG pass rates. axe wave lighthouse and screen readers
AI-written summary · about
chapters (14)
- 0:00Accessibility importance
- 2:28Why accessibility matters
- 3:53Accessibility successes and failures
- 6:41Benefits of early accessibility
- 7:22Personal accessibility testing journey
- 12:24Accessibility traps and consequences
- 13:49Overcoming team resistance
- 18:03Coaching teams on accessibility
- 20:13When to start accessibility testing
- 21:38Accessibility budget and tools
- 22:41Effective accessibility reports
- 24:31Quick accessibility checks
- 26:19Accessible content design
- 27:24Summary and call to action
related talks
09m"How to bring accessibility into your teams."
38mHow to set up an accessibility program in an imperfect world
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
57mHow (and why) to 'shift-left' your accessibility testing
45mTips from the Trenches: Accessibility Testing
28mBuilding in accessibility for broader value to all
14mAccessible Accessibility
50mShift Left on Accessibility: Beyond the Audit