Your Website is Not Accessible
summary
Website accessibility fails often come from missing semantics and small omissions that assistive tech can't recover from: images without alt tags and labels cause screen readers to read filenames; forms rely on placeholders instead of proper labels; interactive elements use divs instead of real buttons; lack of keyboard focus order breaks navigation. A live VoiceOver demo on the New York Times shows output becomes noisy and unusable. Recommended fixes: semantic HTML, ARIA where needed, captions/transcripts, and testing with ChromeVox/Chromebox plus automated checks like WAVE and Quail, which catch many easy wins.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:24Why accessibility matters
- 3:07Common user assumptions
- 4:10Screen reader demo
- 6:21WCAG principles overview
- 7:06Making content perceivable
- 9:58Text alternatives and ARIA
- 11:00Adaptable content structure
- 12:48Distinguishable design
- 13:09Operable interfaces
- 14:34Understandable content
- 16:44Robust compatibility
- 17:50Current state of accessibility
- 18:32Tools and resources
related talks
25mReal Life Accessibility: Have you HEARD your site?
49mLost in Translation
40mAccessibility, what, why and how?
25mPrevent, Catch and Fix Accessibility Issues
01h 07mA web for anyone, anywhere, anytime
41mBuilding Accessible Vue Components
40mWebsite Accessibility Examples That Hinder Accessibility
31mBringing the Web Back to the Blind