How to Program with Accessibility in Mind
summary
Argues accessibility must be built first not bolted on, showing screen reader demos that repeatedly read 17 items and trap navigation on real sites like Home Depot and the New York Times. Recommends concrete fixes: use ARIA roles, provide skip links and alt text, avoid placeholders in forms, keep one-column flow, larger click targets, and 16px minimum font size. Notes practical wins: Kickstarter adds closed captions and Netflix adds audio description, and suggests linters, checklists, and user tests.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:51What is Accessibility
- 1:37Why do we care
- 2:04Who are we talking about
- 2:48Assistant Technologies
- 3:40Visual Impairment
- 6:27ARIA
- 11:20Recap
- 11:37Home Depot
- 15:41Screen Reader
- 15:51Low Contrast
- 17:15Color Blindness
- 17:59Mobility
- 19:26Cognitive Impairment
- 20:15Neurological Impairment
- 21:08Hearing Impairment
- 22:23Scaling
- 23:14Kickstarter
- 24:03Netflix
- 25:39Readability
- 26:08Layout
- 28:21Click Targets
- 29:11Scale
- 29:39Integration
- 30:15Advocacy
- 30:36User Trials
related talks
52mCommon Accessibility Pitfalls
16mAccessibility: More than Just Screen Readers and ARIA
33mAccessibility needs to be the future of better technology
41mTales of Accessibility Failures
33mAccessibility Done Right
26mAccessibility Is a Marathon, not a Sprint
26mMake the internet a better place - with coding for accessibility
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov