Accessibility for UX: Don't worry, it's much worse than you think
summary
Shows concrete tests and fixes: use a straw test (hold a straw to narrow your viewport) to reveal poor form grouping, then fix layout with simple CSS and button visual weight changes so the primary action becomes obvious. Demonstrates a successful build — MIT’s Eclipse Soundscapes (iOS/Android) — that maps audio and haptics to eclipse phases. Gives measurable claims: about 60–70% of accessibility issues trace to missed best practices, ~15% of users have disabilities, and recommends inclusive personas, remote moderated testing, and paying participants.
AI-written summary · about
chapters (8)
- 0:00Start
- 9:24answer Accessibility is intimidating.
- 11:26answer Accessibility is hard.
- 16:42Disability is a usability amplifier
- 17:19ECLIPSE SOUNDSCAPES
- 19:42Accessibility is hard because good design is hard.
- 20:09answer Accessibility is not my job.
- 39:16Design and build with progressive enhancement.
related talks
56mAccessibility for UX: Don't worry, it's much worse than you think
51mAccessible UX: Going beyond WCAG
44mCrafting Great Accessible Experiences
01h 05mAccessibility Testing 101
52mDesigning inclusive and accessible experiences
59mAccessibility in UX: A panel discussion
45mTips from the Trenches: Accessibility Testing
39mHow to win at mobile accessibility