A Web for Anyone, Anywhere, Anytime
summary
Clear actionable items and measured problems: use semantic HTML, one H1 per page, and native controls instead of reinventing buttons; follow ARIA rules—ARIA: don’t use ARIA if native HTML suffices and don’t change native behavior. Test with VoiceOver NVDA JAWS and Chrome DevTools Accessibility. Fix contrast and alt text — WebAIM top million: ~48.84% low contrast; >50% images lack alt. Implement keyboard focus, tabindex 0 only, aria-expanded toggles for menus, skip-to-main links, labeled form errors, and client-side validation via the Constraint Validation API.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:51Why accessibility matters
- 3:36Speaker and basics
- 5:23WCAG principles
- 7:53Semantic HTML
- 10:20Native HTML vs buttons
- 13:11ARIA rules
- 18:04ARIA live regions
- 20:28ARIA roles and labels
- 25:19Perceivable content
- 26:22Color contrast challenges
- 30:13Device orientation
- 31:16Alt text for images
- 33:21Focus and keyboard
- 35:10Tab order and menus
- 38:45Skip links
- 39:06Form labels
- 41:57Error messages
- 42:37Simpler language
- 43:22Imperfect over indifference
- 43:44Q&A
related talks
01h 07mA web for anyone, anywhere, anytime
01h 01mA web for anyone, anywhere, anytime
22mWeb Accessibility - a better user experience for everyone!
33mAccessibility Done Right
50mAccessibility by Everyone (and for Everyone)
25mThe web is inherently accessible
41mBuilding Accessible Vue Components
35mAccelerating accessibility in web