Accessibility: Why You Should Learn About WCAG
summary
WCAG is a usable standard not a philosophy: it lists 87 requirements, classifies them as A AA AAA so teams can prioritize, and specifies concrete rules like audio that plays more than 3 seconds must have pause or separate volume control. Laws (EU Accessibility Act) map to WCAG AA and real lawsuits (e.g., Domino’s) show enforcement. Practical tooling mentioned: Axe, Lighthouse, linters, Fable for manual testing, with automated checks catching only ~30% of issues.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:18What is WCAG
- 3:01WCAG history and W3C standards
- 5:09WCAG global standard
- 8:20WCAG structure and sections
- 10:48WCAG criteria and requirements
- 12:32WCAG audio control
- 16:51Why learn WCAG
- 17:33Prioritizing WCAG levels
- 19:42Key reasons to learn WCAG
- 20:43Q&A
- 22:09Q&A
- 24:38Q&A
- 26:44Q&A
- 27:06Q&A
- 28:11Q&A
- 28:54Q&A
- 31:01Q&A
- 33:06Q&A
- 34:08Q&A
- 35:32Q&A
- 36:39Q&A
- 38:24Q&A
- 41:01Q&A
related talks
56mAccessibility Testing or: How I Learned to Stop Worrying and Ignore WCAG
01h 03mAccessibility: Making your websites more inclusive
33mWeb Accessibility: Why, How and What?
29mAccessibility Matters: Creating a Better Web
50mAccessibility in the Enterprise: The Relationship of A11y and ROI
15mAccess-what? why and how. A11Y for all
43mWhat is accessibility, and why I should care?
16mWeb Accessibility is actually well-forgotten old