Cognitive accessibility: designing for attention and memory
Cognitive accessibility makes an interface understandable without relying on perfect memory or attention. Principles, W3C patterns, examples, and mistakes.
What is cognitive accessibility?
It is the part of accessibility concerned with how we think, not only how we see or hear. It covers cognitive and learning disabilities, such as dyslexia or ADHD, but also situations anyone can face: tiredness, stress, a bad connection, or an interruption in the middle of a form.
The W3C works on it at two levels. The first is the WCAG 2.2 criteria, which can be verified and tested. The guidelines on enough time (2.2), input assistance (3.3), and predictable content (3.2) touch on cognitive needs. The second is the COGA guidance (Cognitive and Learning Disabilities Accessibility Task Force), titled “Making Content Usable for People with Cognitive and Learning Disabilities”, a 2021 Working Group Note with additional patterns. Its eight objectives are: 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.
The W3C itself acknowledges that some cognitive accessibility needs are not addressed by its current standards. That is why meeting WCAG is a starting point, not a guarantee.
Why does it matter to a designer?
Because almost every usability problem that looks like “visual design” has a cognitive cause. A ten-step form with no visible progress, a verification code that has to be copied from an email into another app, or a screen with forty options all demand that people remember and compare. When memory fails, people abandon or make mistakes.
Cognitive accessibility also tends to improve general usability. Shorter paths, plain language, and fewer distractions help everyone, not only people with a specific condition.
Which patterns does the COGA guidance recommend?
These are patterns from the guidance, with their numbers so you can find them in the document:
- A login that does not rely on memory (4.7.1). Do not ask people to remember codes or solve calculations. Allow password managers and pasting into the field. The guidance also covers a simple single-step login (4.7.2) and a login alternative with fewer words (4.7.3).
- Let users go back (4.5.2). If someone steps back in a flow, they should not lose what they typed.
- Limit interruptions (4.6.1). Avoid pop-ups, notifications, and elements that compete for attention during a task.
- Make short critical paths (4.6.2). Keep the route to an important task as short as possible.
- Avoid too much content (4.6.3). Show less information at once.
- Avoid data loss and timeouts (4.5.9). If there is a time limit, warn people and offer to extend it or save progress.
- Nothing moves unexpectedly (4.5.1). Controls and content should stay where people expect them.
In WCAG 2.2, criterion 3.3.8 (Accessible Authentication, Minimum, level AA) requires that no step of an authentication process depends on a cognitive function test, such as remembering a password or solving a puzzle, unless there is an alternative or an assistance mechanism. According to the W3C, allowing password managers and copy and paste are valid mechanisms, and blocking paste fails the criterion.
How do you apply it in a real interface?
A practical way to start is to review a complete flow with one question: “what does the person have to remember at this point?”. Each answer is a chance to show that information on screen instead of demanding it.
Some concrete decisions:
| Situation | Mental load | More supportive alternative |
|---|---|---|
| Verification code sent by email | Remembering it and copying it between apps | A field that accepts pasting and autofill |
| Long form | Remembering what is missing | A progress indicator and automatic saving |
| Menu with many options | Comparing and deciding | Categories with few options each, plus search |
| Animations and carousels | Following motion and losing the thread | Motion that can be paused (WCAG 2.2.2) |
| Session that expires | Redoing the work | Advance warning and an option to extend time (WCAG 2.2.1) |
For text, use short sentences and common words. The COGA guidance has patterns on clear words (4.4.1), literal language (4.4.4), and succinct text (4.4.5), and asks for icons that help the user (4.2.7), not decorative ones.
A quick test: ask someone to complete your flow while answering messages on another screen. The points where they lose their place are the ones that demand the most memory.
When should you NOT apply a pattern blindly?
Some patterns can backfire. A generous session timeout can leave sensitive data open on a shared device; automatic saving can confuse people if it is not visible. The fix is not to switch the protection off, but to make it visible and controllable.
Do not remove all content to “simplify” either. Reducing load means presenting information at the right moment, not hiding it.
Example
Illustrative example: a medical appointment app asked patients to remember a three-part code sent by SMS and type it on another screen. Some patients abandoned the process. The team changed the field to accept pasted codes, showed the code with its validity period, and kept the “Resend” button visible after a few seconds. The change reduced load without removing security.
Common mistakes
- Thinking it only matters for people with disabilities and not applying it to everyone else.
- Confusing simplifying with hiding, and removing information people need.
- Adding decorative animation on screens where people must concentrate.
- Time limits with no warning that wipe out someone’s work.
- Blocking paste in password or code fields.
- Using the product’s technical language in error and help messages.
- Assuming cognitive accessibility is covered by meeting WCAG without testing with people.
To go further, cognitive load explains the general framework of working memory in design, and Hick’s law shows why more options take longer to decide between. If you want the broader accessibility picture, accessibility UX complements this page. To check your decisions with people, triangulation of methods helps you avoid trusting a single test.