Designing inclusive and accessible experiences
summary
Design shows measurable failures and clear fixes: an audit finds 59.6 errors per homepage and 97.8% of homepages fail WCAG AA; 85% low contrast, 68% missing alt text, 52.8% missing input labels. Nearly 47% of accessibility errors originate in design. Practical moves are recommended: partner with users (the NASA soundscapes project designs with blind and low‑vision people), annotate wireframes for a11y, use Figma accessibility plugins, run WebAIM and contrast checkers, and bake accessibility into the workflow rather than treating it as an extra.
AI-written summary · about
chapters (8)
- 0:00Welcome and introduction
- 7:26Inclusive vs accessible design
- 17:55Global disability statistics
- 20:49Accessibility errors in design
- 22:19Universal design principles
- 27:37Tools and resources for designers
- 33:32Q&A on accessibility advocacy
- 51:12Closing and next sessions
related talks
44mDesigning with Accessibility in Mind
52mEssential Accessibility Annotations for a Smoother Design to Development Handoff
37mMaking A Strong Case For Accessibility
50mMaking a Strong Case for Accessibility
26mAuditing design systems for accessibility
40mAccessibility, what, why and how?
22mThe designer is the problem, design is the solution
31mWeb Accessibility: From Design to Code, How to Move Toward Greater Inclusion