# Cognitive Accessibility: Websites Easy to Understand

Source: https://allyway.ai/glossary/cognitive-accessibility

Cognitive accessibility means designing websites so that people with cognitive and learning disabilities can understand and use them – including difficulties with memory, attention, language, reading and math. It covers clear content, predictable navigation, forgiving forms and processes that do not rely on memory.

Cognitive accessibility is about websites that people can understand, remember and use without getting lost – including people with dyslexia, ADHD, autism, intellectual disabilities, dementia or the effects of a brain injury. Unlike many other barriers, these problems rarely show up in code: a page can pass every technical test and still be confusing. Clear language, consistent layouts and forms that forgive mistakes help everyone, especially under stress or on a small screen.

## What it means

W3C covers this in the Working Group Note [Making Content Usable for People with Cognitive and Learning Disabilities](https://www.w3.org/TR/coga-usable/). It describes these disabilities as long-term, short-term or permanent difficulties with cognitive functions such as memory, attention, language, reading and math, and groups its advice into eight objectives:

| Objective | In practice |
|---|---|
| 1. Help users understand what things are and how to use them | Familiar icons, clear labels, standard controls |
| 2. Help users find what they need | Clear headings, search, simple navigation |
| 3. Use clear and understandable content | Short sentences, common words, one idea per paragraph |
| 4. Help users avoid mistakes and know how to correct them | Clear error messages with a solution |
| 5. Help users focus | Few interruptions, no auto-playing content |
| 6. Ensure processes do not rely on memory | No retyping, no codes to remember |
| 7. Provide help and support | Contact and help always in the same place |
| 8. Support adaptation and personalization | Respect user settings, allow simplification |

The W3C note is supplemental: following it "is not required for conformance to WCAG", and it addresses barriers that WCAG 2.x does not fully cover. Still, [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2) added several criteria with these users in mind:

- [Accessible authentication](https://allyway.ai/glossary/accessible-authentication) (3.3.8, AA) – no puzzles or memory tests to log in, paste and password managers must work.
- [Redundant entry](https://allyway.ai/glossary/redundant-entry) (3.3.7, A) – information already entered in a process is filled in or selectable.
- [Consistent help](https://allyway.ai/glossary/consistent-help) (3.2.6, A) – help options appear in the same relative order on every page.

Older criteria such as [timing adjustable](https://allyway.ai/glossary/timing-adjustable), [error suggestion](https://allyway.ai/glossary/error-suggestion) and [consistent navigation](https://allyway.ai/glossary/consistent-navigation) help as well.

> **Tip:** > **Involve the experts**
> W3C recommends involving people with cognitive and learning disabilities throughout design and testing – they are the experts in what works for them.

## Examples

```html title="Example"
<!-- Hard to understand: jargon, no hint, error only after submit -->
<label for="d">DOB</label>
<input id="d" name="d">

<!-- Easier: plain label, format shown, autocomplete, helpful error -->
<label for="birthday">Date of birth</label>
<p id="birthday-hint">For example 24 03 1985</p>
<input id="birthday" name="birthday" autocomplete="bday"
       aria-describedby="birthday-hint">
```

**Do:** Do

Write short sentences with everyday words, keep navigation and buttons in the same place on every page, split long forms into steps with a progress indicator, explain errors with a way to fix them and give enough time.

**Don't:** Don't

Use jargon and abbreviations without explanation, time out sessions without warning, demand that users remember codes or retype data, use CAPTCHAs with puzzles, or fill the page with pop-ups and moving content.

## How to check cognitive accessibility



## Questions

Q: What are cognitive disabilities?
A: W3C's note includes cognitive disabilities, learning disabilities, neurodiversity, intellectual disabilities and specific learning disabilities, with long-term, short-term or permanent difficulties in memory, attention, language, reading or math.

Q: Which WCAG criteria help people with cognitive disabilities?
A: Among others Accessible Authentication (3.3.8), Redundant Entry (3.3.7), Consistent Help (3.2.6), Timing Adjustable (2.2.1), Error Identification (3.3.1) and [Reading Level](https://allyway.ai/glossary/plain-language) (3.1.5, Level AAA).

Q: Is cognitive accessibility required by law?
A: Laws such as the [European Accessibility Act](https://allyway.ai/regulations/eaa) require WCAG Level AA through EN 301 549, which includes several criteria for cognitive needs. W3C's additional cognitive guidance itself is not required for WCAG conformance.

Q: How can I find problems that affect cognitive accessibility?
A: Many of them need a human review. Technical issues that also confuse people – unlabeled fields, missing headings, unclear link texts – can be found automatically with the [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites).
