Getting the Most Out of Your Shift Left Regardless of Your Program Maturity
summary
Argues that shifting accessibility left into design catches most defects early, claiming reduce defects by 67% when designers, developers, and testers collaborate; recommends documenting tab order, ARIA role/name/value, color choices and design annotations so builds match designs; proposes a maturity model from table stakes to niche small-batch solutions and multi-channel coverage; cites large deployments used in practice — 1,500+ Axe Auditor deployments and ~4,000 axe DevTools installs — and promotes micro‑curricula and agile retrospectives to fix recurring defects.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:30History of Design
- 3:52Universal Design
- 6:30Sensory Design
- 8:50Inclusive Design
- 11:11Niche Design
- 13:42Horizons
- 14:44Twins Day
- 18:52Multichannel Success
- 20:53Tactics to Mature
- 24:13Who
- 26:57Documentation
- 29:30Design Thinking
- 30:28Agile retrospectives
- 31:39User complaints
- 32:08Personas
- 34:43Glen Lake Minnesota
- 36:11Questions
- 36:55Dont fight it
- 39:03Tab order
- 41:50Writing requirements
- 48:11Retrospectives
related talks
59mActually Shifting Left: Technical Accessibility for Designers
57mHow (and why) to 'shift-left' your accessibility testing
18mShift Left
48mGet It Right the 1st Time: Stop 80%+ of A11Y Bugs During Development
29mHow to bring accessibility into your teams
45mAccessibility at all stages
43mDesign Beyond Deliverables
45mGreat UX, Despite Agile: How to Get the Best Out of Your Design Team in Agile Projects