Web accessibility for cognitive disabilities
Cognitive accessibility is designing websites for users with ADHD, dyslexia, autism, and memory conditions. Covers WCAG criteria, tips, and testing tools.
Cognitive Accessibility Guide for Web Designers
Key takeaways
- Cognitive disabilities affect approximately 12.8% of U.S. adults, but many more users benefit from cognitive accessibility design, including people with ADHD, dyslexia, and autism spectrum disorder.
- WCAG 2.1 and WCAG 2.2 include specific success criteria that directly address cognitive accessibility needs, including new requirements added in 2023.
- Simple design choices such as plain language, consistent navigation, no time limits, and clear error messages significantly reduce cognitive load for all users.
- Web accessibility lawsuits citing WCAG non-compliance are increasing, particularly in the US under ADA Title III and in Europe under the European Accessibility Act.
- Testing for cognitive accessibility requires both automated scanning and structured manual review against WCAG success criteria.
More than 1 in 10 American adults has a cognitive disability. According to the CDC, approximately 12.8% of U.S. adults report serious difficulty concentrating, remembering, or making decisions. The true number of people who benefit from cognitive accessibility design is significantly higher, covering anyone whose experience of ADHD, dyslexia, autism spectrum disorder, or other neurodivergent traits affects how they use the web.
If your website isn't built with cognitive accessibility in mind, you are not just creating friction for a significant segment of your users. You could be exposing your business to legal risk, given that web accessibility lawsuits under the ADA continue to rise and WCAG standards underpin accessibility laws worldwide.
We’ll walk you through what cognitive accessibility means, which WCAG success criteria are most relevant, practical design steps that can help reduce barriers, and ways to assess how well your website supports users with cognitive disabilities.
What is cognitive accessibility?
Definition: cognitive accessibility Cognitive accessibility refers to designing digital content and interfaces in ways that are understandable, predictable, and operable for people with cognitive or learning disabilities. It means removing barriers that affect how users process information, make decisions, navigate content, and complete tasks online.
The term covers a wide spectrum of conditions and traits. These include ADHD (attention deficit hyperactivity disorder), dyslexia, autism spectrum disorder, dyscalculia, memory impairments, acquired brain injuries, anxiety disorders, and age-related cognitive decline.
It is worth distinguishing cognitive accessibility from general accessibility. General accessibility addresses barriers for people with visual, auditory, or motor impairments. Cognitive accessibility specifically addresses how people process and understand information. The two overlap considerably in WCAG, but cognitive accessibility often requires design decisions that traditional accessibility checklists underemphasise.
The World Wide Web Consortium (W3C) has a dedicated Cognitive and Learning Disabilities Accessibility Task Force (COGA) that produces guidance on making content usable for people with cognitive impairments. Their work has directly informed recent WCAG updates.
Why cognitive accessibility matters for your business
The business case for cognitive accessibility is straightforward. According to CDC data, approximately 12.8% of U.S. adults report a cognitive disability. That figure does not include the many people who experience reading difficulties, attention challenges, or processing differences without a formal diagnosis.
Beyond user reach, there is an increasing legal dimension. In the United States, websites serving the general public are subject to ADA Title III, and courts have repeatedly confirmed that WCAG 2.1 Level AA is the applicable standard. Web accessibility lawsuits are on the rise.
In Europe, the European Accessibility Act (EAA) came into force in June 2025, requiring most businesses selling to EU consumers to meet accessibility standards. Section 508 applies to US federal agencies and their contractors. The ADA Title II final rule extended WCAG 2.1 AA requirements to state and local government websites from 2024.
There is also a strong commercial argument. Designing for cognitive accessibility produces cleaner, more navigable interfaces that benefit all users. Reduced cognitive load means fewer abandoned forms, lower support ticket volumes, and higher task completion rates.
Types of cognitive disabilities and how they affect website use
Cognitive disability is not a single condition. Understanding the different ways users experience the web helps you make more targeted design decisions.
Condition | How it affects web use | Key design considerations |
|---|---|---|
ADHD | Difficulty sustaining attention; easily distracted by animations, pop-ups, or busy layouts; may struggle to complete multi-step processes | Remove auto-playing animations; keep CTAs single and clear; allow users to control time limits |
Dyslexia | Difficulty decoding text; crowded lines and certain fonts increase reading difficulty; may lose place when scanning long paragraphs | Use clear, readable fonts with adequate line spacing; short paragraphs; avoid justified text |
Autism spectrum disorder | Strong need for predictability; may be sensitive to unexpected changes in layout or content; tendency to take language literally | Consistent navigation; explicit, literal instructions; avoid idioms and metaphors |
Memory impairments | Difficulty completing multi-step tasks; may lose track of where they are in a process; easily disoriented on complex sites | Progress indicators; breadcrumb navigation; avoid session timeouts; allow form data to persist |
Language and reading disorders | Difficulty processing complex or dense text; reading level affects comprehension | Plain language; WCAG SC 3.1.5 reading level; supplement text with visuals or icons |
Dyscalculia | Difficulty processing numbers and numerical relationships | Avoid number-heavy interfaces; use visual progress bars instead of percentages; spell out quantities |
Acquired brain injuries / age-related decline | Variable and unpredictable mix of attention, memory, and processing challenges | Applies broadly: consistent layout, plain language, no time pressure, clear error guidance |
WCAG success criteria for cognitive accessibility
The Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2 include multiple success criteria with direct relevance to cognitive accessibility. Level AA is the standard referenced in most accessibility laws worldwide. The table below shows the criteria most significant for cognitive needs.
Success criterion | Level | Cognitive relevance |
|---|---|---|
1.3.5 Identify input purpose | AA (WCAG 2.1) | Allows browsers and assistive tools to auto-fill form fields, reducing the cognitive load of remembering personal information. |
2.2.1 Timing adjustable | A | If a time limit exists, users must be able to turn it off, adjust it, or extend it. Essential for users with ADHD or processing difficulties. |
2.2.2 Pause, stop, hide | A | Moving, blinking, or auto-updating content must be pausable. Helps users with attention disorders or vestibular conditions. |
2.4.6 Headings and labels | AA | Descriptive headings and labels help users understand page structure and navigate content without reading everything. |
3.1.5 Reading level | AAA | Where possible, provide a simpler version of content that does not require a reading level higher than lower secondary education. |
3.2.1 On focus | A | Components do not trigger unexpected context changes when they receive focus. |
3.3.1 Error identification | A | If an input error is detected, the item in error is identified and described to the user in text. |
3.3.2 Labels or instructions | A | Labels or instructions are provided when content requires user input. |
3.3.3 Error suggestion | AA | If an error is detected and suggestions for correction are known, the suggestion is provided. |
3.3.7 Redundant entry (NEW in WCAG 2.2) | A | Information previously entered by the user is either auto-populated or available for the user to select. Directly addresses memory load. |
3.3.8 Accessible authentication (NEW in WCAG 2.2) | AA | Authentication processes cannot require users to solve a cognitive function test (such as a CAPTCHA) unless an alternative is available. |
WCAG 2.2 update note
WCAG 2.2 was published in October 2023 as an update to WCAG 2.1. The two new criteria above (3.3.7 and 3.3.8) directly address cognitive barriers. WCAG 2.2 was approved as ISO/IEC 40500:2025, giving it formal international standard status. Any audit or compliance program should now test against WCAG 2.2 AA as the baseline.
10 practical design tips for cognitive accessibility
These are the changes that have the highest impact on cognitive accessibility and are most actionable without a full site redesign.
1. Use plain language
Write at a reading level accessible to a wide audience. Keep sentences short. Avoid jargon, double negatives, and complex subordinate clauses. The W3C recommends aiming for a reading level no higher than lower secondary education for general-audience content.
2. Make navigation consistent and predictable
WCAG SC 3.2.3 requires navigation mechanisms repeated across pages to appear in the same relative order. Beyond compliance, consistent navigation reduces the mental overhead of learning a new pattern on every page. Your header, footer, and sidebar structure should be identical across all pages.
3. Remove time limits where possible
Time limits create anxiety for users with ADHD, cognitive fatigue, or slower processing speeds. Where a time limit is necessary (for example, in a payment flow), provide a visible warning and an easy way to extend. Do not simply expire a session without notice.
4. Write clear, descriptive error messages
Generic error messages like 'Invalid entry' are barriers for users with cognitive disabilities. Tell users what went wrong and exactly how to fix it. Place error messages adjacent to the relevant field, not at the top of a form, away from the problem.
5. Do not require CAPTCHA without an alternative
WCAG 2.2 SC 3.3.8 is explicit: cognitive function tests used for authentication must have an alternative method. Standard CAPTCHA, math puzzles, and pattern matching are barriers. Provide alternatives such as email link authentication, biometric login, or trusted device recognition.
6. Use meaningful headings and labels
Structure your content with descriptive H2 and H3 headings that explain what each section contains. This allows users to scan and jump to relevant content without reading everything. Headings are not decorative; they are navigational tools.
7. Support assistive technology for cognition (ATC)
Many users with cognitive disabilities rely on tools such as screen magnifiers, reading masks, text-to-speech software, and browser extensions that simplify or reformat content. Your website should continue to function when CSS is modified, images are disabled, or font sizes are changed. Accessibility widgets can also support the user experience by giving visitors additional ways to adjust colors, fonts, spacing, and navigation based on their individual needs.
8. Break multi-step processes into clear steps
For checkout flows, registration forms, and other multi-step processes, show users where they are (for example, 'Step 2 of 4'), what they have already completed, and what comes next. Do not lose user data between steps. Auto-save progress where possible.
9. Do not auto-populate unexpected context changes
Do not trigger significant changes in context (navigating to a new page, submitting a form, opening a modal) on focus or on minor interaction unless the user initiates it deliberately. Unexpected changes disorient users with memory or attention difficulties.
10. Provide alt text and meaningful image descriptions
Well-written alt text supports users who rely on screen readers, but supplemental imagery also helps users with reading difficulties understand content through visual context. Icons, diagrams, and illustrations reduce the reading burden when paired with text.
How to test your website for cognitive accessibility
Testing for cognitive accessibility is a combination of automated scanning and structured manual review. Automated tools catch a significant portion of WCAG failures but cannot evaluate readability, plain language, or cognitive load, which require human judgment.
Automated testing
Automated accessibility scanners check your site against a subset of WCAG success criteria, flagging missing labels, broken focus order, absent alt text, and colour contrast failures. Clym's free accessibility testing tools and accessibility testing and audit solution run comprehensive checks against all WCAG success criteria and generate professional audit documentation. They provide actionable remediation guidance for each identified issue, not just a list of failures.
Manual review checklist for cognitive accessibility
Check | WCAG criterion | Pass / Fail / N/A |
|---|---|---|
All form fields have visible, descriptive labels | SC 3.3.2 |
|
Error messages specify what went wrong and how to fix it | SC 3.3.1 / 3.3.3 |
|
No time limits without a user-controlled extension option | SC 2.2.1 |
|
Auto-playing or moving content can be paused or stopped | SC 2.2.2 |
|
Navigation is consistent across all pages | SC 3.2.3 |
|
Page headings describe section content accurately | SC 2.4.6 |
|
No context changes triggered on focus alone | SC 3.2.1 |
|
CAPTCHA has a cognitive-function-free alternative | SC 3.3.8 (WCAG 2.2) |
|
Forms do not ask users to re-enter previously provided info | SC 3.3.7 (WCAG 2.2) |
|
Input fields support browser autocomplete | SC 1.3.5 |
|
The content reading level is appropriate for a general audience | SC 3.1.5 (AAA) |
|
User testing with people with cognitive disabilities
Automated tools and checklists have limitations. Where possible, conduct usability testing with participants who have cognitive disabilities. Organisations like the International Association of Accessibility Professionals (IAAP) can connect you with testing resources and guidance.
How Clym supports cognitive accessibility on your website
Clym brings accessibility, privacy, and compliance management tools together in a single platform. For cognitive accessibility, Clym supports teams in three key areas: user experience adjustments, accessibility testing, and accessibility documentation.
Accessibility widget: Clym’s widget gives visitors additional ways to adjust their browsing experience based on their individual needs. It includes six pre-configured accessibility profiles, including a cognitive accessibility profile, and allows users to adjust text size, line spacing, font type, highlight colors, animation settings, and navigation preferences.
These controls can help improve usability for some visitors, but they are not a substitute for fixing accessibility barriers in the website’s code, structure, content, and design.
Accessibility testing and audit: Clym’s open-source desktop testing tool helps teams identify accessibility issues that need to be addressed at the website level. It evaluates websites against WCAG success criteria using automated checks and guided manual testing procedures, then generates reports in WCAG-EM, ATAG, and VPAT formats.
These reports can help your team understand where barriers exist, prioritize remediation work, and document accessibility efforts internally.
Accessibility issue reporting: Clym also supports accessibility issue reporting, giving visitors a way to report accessibility barriers they encounter on your website. This helps your team collect direct feedback from users and identify issues that automated testing alone may not catch.
Accessibility statement: Clym’s accessibility statement solution helps teams create and publish an accessibility statement for their website. This can support transparency by explaining your current accessibility efforts, known limitations, and the process users can follow to report accessibility issues.
Clym does not make a website compliant on its own, and an accessibility widget should not be treated as a replacement for proper remediation. Instead, Clym gives your team tools to identify accessibility barriers, improve the user experience, document your accessibility work, and support ongoing efforts around ADA, WCAG, Section 508, the European Accessibility Act, and other accessibility frameworks.
Conclusion
Cognitive accessibility is not a niche concern. Over 12% of U.S. adults have a formal cognitive disability, and millions more navigate the web with ADHD, dyslexia, or other conditions that affect how they process information. Designing for cognitive accessibility means cleaner navigation, plainer language, better error handling, and fewer barriers for every user.
The key actions are clear: update your content to reflect WCAG 2.2, specifically the new requirements around authentication and redundant data entry; audit your forms and navigation for cognitive load; make your design predictable and your error messages helpful; and give users the controls they need to adapt their experience.
The good news is that most cognitive accessibility improvements also improve usability for everyone. Fewer timed sessions, cleaner layouts, and better instructions are not accommodations. They are well-designed.
Frequently asked questions
Cognitive accessibility means designing a website so that users with cognitive disabilities, such as ADHD, dyslexia, memory impairments, or autism, can understand, navigate, and use it without barriers. It covers plain language, consistent navigation, clear error guidance, and removes requirements that place unnecessary demands on memory or attention.
Multiple WCAG criteria address cognitive needs, including SC 3.3.1 (error identification), SC 3.3.2 (labels or instructions), SC 3.3.3 (error suggestion), SC 2.2.1 (timing adjustable), SC 3.2.3 (consistent navigation), and the WCAG 2.2 additions SC 3.3.7 (redundant entry) and SC 3.3.8 (accessible authentication). Level AA is the most commonly required standard.
A clear example is removing CAPTCHA puzzles from login forms or providing a non-cognitive alternative, such as email link authentication. Another is adding 'Step 2 of 4' indicators to checkout flows so users with memory difficulties can track their progress. Replacing vague error messages like 'Invalid input' with 'Your email address must include the @ symbol' is a third.
General web accessibility covers visual, auditory, and motor barriers alongside cognitive ones. Cognitive accessibility specifically addresses how users process information, make decisions, and understand content. While there is significant overlap in WCAG, cognitive accessibility focuses on readability, predictability, and reducing memory and attention demands rather than on screen reader compatibility or keyboard navigation.
Start with an automated accessibility scan to identify WCAG failures. Then conduct a manual review using the success criteria most relevant to cognitive needs, particularly SC 3.3.1, 3.3.2, 3.3.3, 3.3.7, 3.3.8, 2.2.1, and 3.2.3. Where possible, test with real users who have cognitive disabilities. Document your findings and remediation in an accessibility audit report.
Yes. WCAG 2.2, published in October 2023, added two success criteria directly relevant to cognitive accessibility: SC 3.3.7 (Redundant entry, Level A) prevents requiring users to re-enter information they have already provided. SC 3.3.8 (Accessible authentication minimum, Level AA) prohibits requiring users to solve cognitive function tests like CAPTCHAs without providing an alternative method.
Compliance Content Manager | CPACC (IAAP)
Alex is a Compliance Content Manager at Clym, where he researches and writes about everything related to data privacy and web accessibility compliance for businesses, helping them stay informed on their compliance needs and spreading awareness about making the web safer and more inclusive. When he's not writing about compliance, Alex has his nose in a book or is hiking in the great outdoors.
