WCAG
Note: This is a living note, an auto generated page synthesized by my self updating second brain managed by Claude. While it's input was my actual organic writing, this is an AI summary/extraction/synthesis part of my The Living Notes section.
If you prefer to read my organically written words or work, please go to any of the other nav links besides living-note or a page, route, or tag without #living-note.
WCAG
What It Is
Web Content Accessibility Guidelines — the international standard for web accessibility. Published by W3C. Core framework for legal compliance (ADA, Section 508, EN 301 549) and practical implementation.
Current version: WCAG 2.2. WCAG 3.0 in development.
Structure
Four principles (POUR):
- Perceivable — info and UI must be presentable in ways users can perceive
- Operable — UI components and navigation must be operable
- Understandable — info and UI operation must be understandable
- Robust — content must be interpretable by assistive technologies
Three conformance levels: A, AA, AAA. Legal compliance typically requires AA.
What the Standard Misses
WCAG is designed for what can be standardized and tested. Real-world experience reveals gaps:
Cognitive load — COGA (Cognitive and Learning Disabilities Accessibility) task force addresses this but not yet in main WCAG. Issues: memory demands, distraction, anxiety-inducing UI, complex navigation. The COGA Research Modules (Group Note Draft, Feb 2026) cover: voice systems, indoor navigation, online safety/wellbeing, and supported decision-making.
Neurodivergent-specific barriers — autistic users experience sensory overload, unexpected motion, unpredictable interfaces, and social complexity in UI copy in ways WCAG doesn't fully address.
Dynamic interfaces — SPAs, infinite scroll, live regions, toast notifications — WCAG was written for documents; application patterns create failure modes not well specified.
Language complexity — reading level and plain language guidance is weak. Critical for cognitive and literacy accessibility.
Automated tool blind spots — axe and Lighthouse catch ~30–60% of real issues. Color contrast, missing alt text, form labels — yes. Context-dependent issues, cognitive barriers, focus management in complex apps — often missed.
WCAG Without the Jargon
Plain language translation of key concepts (for stakeholder communication):
- "Alternative text" → "descriptions of images for people who can't see them"
- "Keyboard navigable" → "works completely without a mouse"
- "Color contrast" → "text is readable against its background"
- "Focus indicators" → "you can always see where you are on the page"