How accessible is your website?Start free check

Cognitive Accessibility: Websites Easy to Understand

Also called: COGA, Accessibility for cognitive disabilities, Cognitive and learning disabilities accessibility, Neurodiversity-friendly design

Definition

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. 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 added several criteria with these users in mind:

  • Accessible authentication (3.3.8, AA) – no puzzles or memory tests to log in, paste and password managers must work.
  • Redundant entry (3.3.7, A) – information already entered in a process is filled in or selectable.
  • Consistent help (3.2.6, A) – help options appear in the same relative order on every page.

Older criteria such as timing adjustable, error suggestion and consistent navigation help as well.

Examples

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

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

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

    What are cognitive disabilities?

    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.

    Which WCAG criteria help people with cognitive disabilities?

    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 (3.1.5, Level AAA).

    Is cognitive accessibility required by law?

    Laws such as the European Accessibility Act 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.

    How can I find problems that affect cognitive accessibility?

    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.

    • Accessible Authentication: Logins Without Memory Tests

      Accessible Authentication (Minimum) is WCAG success criterion 3.3.8. No step of a login may require a cognitive function test – remembering a password, transcribing a code, solving a puzzle – unless an alternative, a helping mechanism or an allowed exception is available.

      Read definition: Accessible Authentication: Logins Without Memory Tests
    • Consistent Help: Keep Support in the Same Place

      Consistent Help is WCAG success criterion 3.2.6. If help mechanisms such as contact details, a contact form, a self-help page or a chatbot are repeated on multiple pages of a site, they occur in the same order relative to other page content, unless the user changes it.

      Read definition: Consistent Help: Keep Support in the Same Place
    • Redundant Entry: Don't Ask for the Same Data Twice

      Redundant Entry is WCAG success criterion 3.3.7. Information a user already entered or was given in the same process must be auto-populated or available to select when it is needed again – unless re-entry is essential, needed for security or the information is no longer valid.

      Read definition: Redundant Entry: Don't Ask for the Same Data Twice
    • Error Prevention: Safe Orders, Payments and Data

      Error prevention means that pages which create legal commitments or financial transactions, change or delete user data, or submit test answers give users a safety net: the submission is reversible, checked for errors, or can be reviewed and confirmed first. WCAG 3.3.4 requires it at Level AA.

      Read definition: Error Prevention: Safe Orders, Payments and Data

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done