What is cognitive accessibility?
Cognitive accessibility means designing content and interactions that support different ways of thinking, learning and processing information. It is relevant to people with intellectual disabilities, dyslexia, ADHD, dementia, acquired brain injuries and other conditions. People’s needs vary, including among those with the same diagnosis. W3C’s introduction to cognitive accessibility explains how these differences can affect memory, attention, language and understanding.
Clear instructions and predictable navigation can also help someone reading in a second language, using an unfamiliar service or trying to concentrate while distracted. These are different circumstances, but they support the value of reducing unnecessary difficulty.
Here are some figures that help illustrate the context:
- 259,050 people, approximately 5% of the population, reported a long-lasting difficulty with learning, remembering or concentrating in Census 2022.
- 109,288 people reported an intellectual disability. Of these, 75% also reported difficulty with learning, remembering or concentrating. These groups overlap and should not be added together.
Both figures come from the CSO’s Census 2022 disability findings.
Separately, 18.7% of adults aged 18 and over reported a diagnosed neurodivergent condition or suspected they were neurodivergent in the Irish Health Survey 2024.
Language is also worth considering. Census 2022 recorded 751,507 residents who spoke a language other than English or Irish at home. While most reported speaking English well or very well, approximately 11% reported not speaking it well and 2% not at all. Clear language helps serve a diverse audience without assuming that everyone who speaks another language needs support.
Where WCAG fits
The Web Content Accessibility Guidelines (WCAG) already address aspects of cognitive accessibility, including instructions, predictable behaviour and error handling. WCAG 2.2 also includes criteria covering repeated data entry and accessible authentication.
However, WCAG does not cover every cognitive accessibility need. W3C’s supplementary cognitive accessibility guidance offers further recommendations beyond those required for conformance.
The blind spot appears when passing an assessment becomes the end of the conversation. An assessment is valuable, but observing people using the website can reveal difficulties that conformance checks alone miss.
The impact of cognitive load
Cognitive load is the mental effort involved in a task. On a website, you’re trying to understand instructions, compare options, remember information and decide what to do next. It can be a lot.
Some effort is unavoidable. Choosing a financial product or completing a detailed application requires thought. But the interface can add work that has little to do with the decision itself.
Small obstacles add up
Imagine you’re booking an appointment. A promotional pop-up appears while you’re trying to work out which service to select. You close it, find your place and continue.
Next, you’re asked to create an account and retrieve a verification code. A few steps later, you discover that you need a document you don’t have handy. You leave the screen to find it. By the time you return, the session has expired, and your answers are gone.
Each step adds another demand. A straightforward booking becomes mentally exhausting, even if you don’t have cognitive struggles.
W3C’s guidance on helping users focus explains that interruptions can make it particularly difficult for those with memory or attention difficulties. That is why reviewing individual pages is not enough. Walk through the whole process, including what happens when someone gets interrupted, makes a mistake or needs a break.
A completed form tells you that someone reached the end, not how much effort, uncertainty or outside help it took.
| Barrier | What it asks of the user |
|---|---|
| Dense pages with little hierarchy | Find the important information while filtering out everything else. |
| Unexplained jargon or changing terminology | Decode unfamiliar language and decide whether different words mean the same thing. |
| Instructions separated from the relevant field | Remember what to do while navigating elsewhere. |
| Pop-ups, moving content and competing calls to action | Repeatedly recover attention and find their place. |
| Vague errors such as “Invalid input” | Work out what went wrong and how to fix it. |
| Time limits and lost form entries | Work at the website’s pace or repeat completed work. |
Minimalism does not automatically solve these problems. Removing labels or hiding essential instructions may make a screen look cleaner while making its meaning harder to understand.
How to improve the user experience
Make the journey predictable
Explain up top what someone will need before they start a lengthy task. Make the process digestible with meaningful stages and make progress visible.
A label such as “Step 2 of 4: Your appointment” helps someone understand where they are, including after an interruption. W3C’s guidance on making each step clear recommends showing completed, current and upcoming steps, along with important choices already made.
Keep information available instead of testing memory
Place instructions beside the relevant field. Keep selected dates, products or options visible where they inform the next decision.
Avoid asking people to enter information they have already supplied in the same process. WCAG 2.2’s Redundant Entry criterion generally requires that information to be automatically populated or available for selection. Exceptions include essential repetition, security needs and information that is no longer valid.
Make pausing and correcting mistakes manageable
A single incorrect field should not mean starting the whole form again. Preserve valid answers and make it easy to find and correct the error.
Where a service sets a time limit, let people turn it off, adjust it or extend it, unless a WCAG exception applies. Clearly explain what happens when time expires and whether their work will be saved.
W3C’s guidance on avoiding data loss and timeouts highlights the importance of allowing people time to look up information or take a break without losing their progress.
Give the login journey proper attention
An accessible service is of limited use if people cannot get into it. Support password managers and allow pasting into password and verification-code fields.
WCAG 2.2’s Accessible Authentication criterion addresses cognitive tests during login, such as remembering a password or transcribing a code. It sets out the assistance, alternatives and exceptions that can satisfy the requirement.
Tell people what they need to know, when they need it
Use familiar words, descriptive headings and short sections. Explain necessary specialist terms. Keep the name of a service or action consistent throughout the journey.
W3C’s clear-content guidance recommends straightforward language and instructions that are easy to follow.
In practice, that can look like this:
| Instead of | Try |
|---|---|
| “Please provide the requisite documentation.” | “Upload proof of your address, such as a recent electricity bill.” |
| “Invalid date.” | “Enter the date as DD/MM/YYYY, for example 14/10/2026.” |
| “Proceed.” | “Review your booking.” |
| “Your request has been processed.” | “We’ve received your application. We’ll email you within five working days.” |
The principle is to replace uncertainty with useful information. In other words, error messages should explain the actual problem, and confirmation messages should accurately describe what has happened and what comes next.
Keep essential detail, but make it easier to find
Shorter copy is not automatically clearer. Removing an example or explanation might reduce the word count while making the task more difficult.
For a complicated service, give a concise overview, then organise the detail under descriptive headings. Help people find the explanation they need without making everyone read everything at once.
Where appropriate, provide an Easy Read version developed and tested with its intended audience. W3C’s guidance on alternative content recommends additional explanations and formats for complex information and tasks.
Test understanding, not just completion
Test a task on your site (like submitting a form) with people who have different cognitive and learning access needs, alongside your WCAG assessment.
W3C recommends combining user involvement with standards-based evaluation. Neither approach gives the full picture on its own, and one participant’s experience should not be taken to represent everyone with the same condition.
Those highly insightful moments give those creating and updating the site something specific to fix.
Universal design asks us to consider how people understand and use an experience from the beginning. So when you think about cognitive accessibility, first ask: how much unnecessary work are we asking someone to do?
At AccessPoint, we help organisations identify accessibility barriers and make practical improvements through auditing, remediation and universal design advice. For us, it’s about thinking beyond just WCAG guidelines and creating something that functions as it should, for everyone.