Cognitive Accessibility
Date: 2026-08-17
Designing for differences in memory, attention, language processing and executive function. It’s the least-covered area of accessibility standards, it affects the largest group of people, and almost everything that helps here helps everyone.
Cognitive accessibility addresses barriers arising from how people process, remember and act on information — learning disabilities, ADHD, autism, dyslexia, acquired brain injury, dementia, and situational states like stress, fatigue and distraction.
It’s the largest affected group and the least specified, because the barriers resist the pass/fail form that makes WCAG criteria testable — WCAG.
The barriers
MEMORY holding information
across steps
→ a reference number on
one screen, needed on
the next
ATTENTION interruptions, movement,
competing elements
LANGUAGE jargon, long sentences,
ambiguity, idiom,
double negatives
EXECUTIVE multi-step tasks,
FUNCTION planning, unclear
sequences
TIME PRESSURE timeouts, countdowns
ANXIETY unclear consequences,
irreversible actions
What helps
Almost all of it is ordinary good design applied consistently:
PLAIN LANGUAGE
short sentences, common words
→ "we'll email you" not "an email
notification will be dispatched"
— Readability
CONSISTENCY
the same thing in the same place,
named the same way
→ learning once instead of per page
— Design Systems
REDUCE MEMORY DEMAND
show information where it's needed
rather than requiring recall
→ the order summary visible during
checkout
ONE THING AT A TIME
break long tasks into clear steps
with visible progress
— Progressive Disclosure
PREDICTABILITY
no unexpected changes, no auto
advancing, no context shift on focus
CLEAR CONSEQUENCES
say what a button will do before
it's pressed
FORGIVENESS
undo, confirmation on destructive
actions, saved progress
— Error Prevention and Recovery
NO TIME PRESSURE
or a way to extend it
See: Readability · Design Systems · Progressive Disclosure · Error Prevention and Recovery
Timeouts are a specific failure
A checkout that expires while someone is finding their card is a cognitive accessibility barrier, and it’s common.
IF A TIMEOUT IS NECESSARY
warn before it expires
offer a simple extension
preserve the input on expiry
← this last one is the real fix
Manufactured urgency compounds it directly. A countdown timer on a product page adds time pressure to a task that already requires planning — which is one more reason the fabricated versions are a problem — Scarcity and Urgency.
Language, specifically
| Avoid | Prefer |
|---|---|
| ”Failure to complete all mandatory fields will prevent submission" | "You must enter your postcode to continue” |
| Utilise | Use |
| Commence | Start |
| P&P | Delivery |
| Double negatives | A positive statement |
| Idiom and metaphor | Literal description |
Literal language matters for autistic users specifically, where idiom and figurative phrasing can be genuinely ambiguous rather than merely inelegant — Microcopy, Voice and Tone.
The overlap argument
Everything in this note helps everyone.
plain language helps non-native
speakers, and
everyone in a hurry
consistency helps first-time
users
saved progress helps anyone
interrupted
clear consequences helps everyone
reduce anxiety
no timeouts helps anyone
distracted
The situational overlap is the strongest commercial argument. Someone shopping on a phone, on a train, holding a child, is temporarily in every category in this note — which is a large share of retail traffic — Inclusive Design.
Where standards are thin
WCAG 2.x addresses some of this — consistent navigation, error identification, no unexpected context changes — and much of the area sits outside testable criteria.
[CHECK: the current status of WCAG cognitive-accessibility guidance and any supplementary W3C material before treating this as fully covered by conformance.]
So conformance doesn’t establish it. The test remains whether someone can complete the task under realistic conditions — which is what usability testing with a genuinely varied group tells you and an audit doesn’t — Usability Testing.