Why WCAG is not enough
summary
Research shows that carefully rewritten plain text reaches only 50–60% understood (test subjects); adding images or video raises comprehension by 20–30% more, and adding synthetic speech adds another 8–10%. WCAG treats text as the default content and requires text alternatives for non‑text, but lacks requirements for equal multimodal delivery, cognitive/readability guidance, or touch‑first interaction patterns, so accessible outcomes require designing and testing multimodal content, not just meeting technical checklist items.
AI-written summary · about
chapters (9)
- 0:00Start
- 9:32Tested in real life
- 10:27From the users point of view
- 13:05Standards are key
- 17:02Text manual or filmed instruction
- 20:303.1.5 Reading Level (AAA)
- 24:03Reading ability, level AAA
- 27:26Could be interpreted as ..
- 30:00No trace in WCAG
related talks
48mLet's break some WCAG rules
38mGuidelines on Designing for Accessibility in UX Design
53mLet's break some WCAG rules
01h 03mAccessibility: Making your websites more inclusive
56mAccessibility Testing or: How I Learned to Stop Worrying and Ignore WCAG
51mAccessible UX: Going beyond WCAG
45mAccessibility: Why You Should Learn About WCAG
54mWhat’s new in WCAG 2.1?