Web accessibility in practice, more than just WCAG
summary
Shows that 1.3 billion people face significant disabilities and WebAIM’s WebAIM Million finds almost every homepage has accessibility failures, then builds a contact form and implements concrete fixes: connected label for/id, hidden visual markers with aria-hidden, aria-required, aria-describedby for hints, aria-invalid on error and aria-live="assertive" to announce validation. Recommends automation with Lighthouse and "upscore" and using Testing Library for scripted checks, plus manual screen reader and keyboard runs.
AI-written summary · about
chapters (13)
- 0:00Web accessibility intro
- 1:13Why accessibility matters
- 4:27Common disabilities
- 6:58Impact of failures
- 8:23Curb cut effect
- 9:46Understanding WCAG
- 13:38Accessible form coding
- 23:40Automated testing
- 24:42Closing remarks
- 25:24Q&A on pushback
- 28:34Experience accessibility tools
- 29:59Accessibility tools
- 31:26Visible features
related talks
50mMaking a Strong Case for Accessibility
50mAccessibility by Everyone (and for Everyone)
33mWeb Accessibility: Why, How and What?
37mMaking A Strong Case For Accessibility
25mPrevent, Catch and Fix Accessibility Issues
22mWeb Accessibility?
37mAccessibility Matters: Creating a Better Web
41mAccessibility is a Requirement