Accessibility: More than Just Screen Readers and ARIA
summary
Argues that ARIA and screen readers are necessary but not sufficient and pushes accessibility-first design over bolt-on fixes; explains three user groups—permanent, temporary, situational—and gives concrete fixes that work: Twitter auto-switch by sunset for legibility, YouTube auto-generated captions to enable silent viewing, and United caches boarding passes and forces brightness to protect check-in flows; warns that accessibility is subjective, needs design decisions, and that small, targeted changes prevent large negative user moments.
AI-written summary · about
chapters (12)
- 0:00Introduction to accessibility
- 1:07Learning accessibility basics
- 2:30Limitations of ARIA and screen readers
- 3:52Accessibility as a design problem
- 5:21Mobile-first to accessibility-first
- 6:53Permanent temporary situational disabilities
- 7:56Theme switching for readability
- 8:58Auto-generated subtitles on YouTube
- 10:02Stressful travel app improvements
- 12:51Negativity bias in user feedback
- 14:19Subjectivity of accessibility
- 15:43Summary and Q&A
related talks
31mHow to Program with Accessibility in Mind
26mAccessibility Is a Marathon, not a Sprint
40mThe Importance of #a11y-ship
29mAccessibility first is the new Mobile first
33mAccessibility Done Right
28mBuilding in accessibility for broader value to all
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
33mAccessibility needs to be the future of better technology