Making Content Usable for People with Cognitive and Learning Disabilities (W3C WAI-COGA)
A W3C Working Group Note (published 29 April 2021) giving supplemental guidance, beyond WCAG’s own success criteria, for making web content usable by people with cognitive and learning disabilities. Following it isn’t required for WCAG conformance, but the working group frames it as raising accessibility for this group in ways WCAG’s existing criteria don’t fully reach.
License: W3C Document License — “W3C liability, trademark and permissive document license rules apply” per the document’s own copyright line; permits copying, modifying, and distributing with attribution (same license basis as Combobox Pattern (W3C WAI-ARIA Authoring Practices Guide)).
Key points
- The guidance is organized under eight objectives: help users understand what things are and how to use them; help users find what they need; use clear and understandable content; help users avoid mistakes and know how to correct them; help users focus; ensure processes do not rely on memory; provide help and support; and support adaptation and personalization. Each objective breaks down into individual design patterns, each stating a user need, what to do, how it helps, and use/avoid examples.
- Memory-dependent processes are treated as a distinct failure category, not folded into general error prevention: a login “cannot rely on a lot of words” or require puzzles/calculations, should allow a single simple step, and should offer a less-text alternative for users who struggle with reading. An automated phone/voice menu should let a caller reach a human by pressing one reserved digit, rather than requiring them to hold several spoken options in memory before choosing.
- Beyond memory specifically, the guidance repeats a broader rule across objectives: don’t rely on a user’s calculations or on memorizing information the interface already has or has already shown once.
- The document defines ten personas spanning distinct conditions — an aging user with mild cognitive impairment, an autistic computer scientist, a supermarket worker with Down syndrome, a retired lawyer with dementia, a therapist with dyscalculia, a traumatic-brain-injury survivor using speech recognition, someone with memory loss, a librarian with hemiplegia and aphasia, a student with dyslexia, and someone with ADHD — used throughout the patterns to check a design against a specific person’s actual barriers rather than an abstract “cognitive disability” category.
- Its recommended way to validate a design against this guidance is inclusive testing: involving people with cognitive and learning disabilities directly in usability testing, focus groups, and design/research teams, rather than relying only on the personas or a checklist review after the fact.