Why WCAG is not enough for neurodivergent users
Neurodiversity Design Council
WCAG 2.2 is the global standard for digital accessibility. It is thorough, well-established, and legally referenced in accessibility regulations across the UK, EU, and beyond. If your product meets WCAG 2.2 AA, you have done something meaningful. You have addressed barriers for users with visual impairments, hearing loss, motor difficulties, and some cognitive needs.
But WCAG was not designed for neurodivergent users. And the gap between what it covers and what neurodivergent people actually need is wider than most organisations realise.
What WCAG covers well
WCAG is built around four principles: perceivable, operable, understandable, and robust. It covers colour contrast, keyboard navigation, text alternatives for images, captions for video, and hundreds of other specific technical criteria. These are real, important accessibility requirements. Meeting them is not optional and it is not trivial.
For visual, auditory, and motor disabilities, WCAG is comprehensive. It tells you what to build, how to test it, and what the pass/fail threshold is. That clarity is its greatest strength.
Where the gap starts
Around one in five people in the UK is neurodivergent. That includes ADHD, autism, dyslexia, dyspraxia, and a range of co-existing conditions that affect how people process information, manage attention, handle sensory input, and regulate emotional responses.
WCAG has a supplementary resource called COGA (Cognitive and Learning Disabilities Accessibility). It is useful but it is guidance, not a testable standard. There are no pass/fail criteria. No scoring. No certification. It tells you what to think about. It does not tell you what to measure.
That means a product can meet every WCAG 2.2 AA criterion and still be genuinely unusable for a neurodivergent person. Not because the product is technically inaccessible. Because it is cognitively hostile.
What cognitively hostile looks like
A dashboard with fourteen notification badges competing for attention. A form with twenty-three fields and no save button. A timed assessment where you know the answer but cannot get to it fast enough. An error message that says "invalid input" without telling you what was wrong or how to fix it.
Every one of these products can pass WCAG. The colour contrast is fine. The keyboard navigation works. The headings are properly structured. But the product is still failing the people using it, because the barriers are cognitive, not technical.
WCAG does not test for:
Cognitive load - how much mental effort the interface demands
Executive function support - whether the product helps you plan, sequence, and complete tasks
Sensory overload prevention - beyond colour contrast, into notification management, motion, and visual density
Emotional safety - whether error handling, feedback, and design patterns cause unnecessary distress
Dark pattern absence - whether the product manipulates users through urgency, shame, or deception
Personalisation depth - whether users can meaningfully adapt the product to their own needs
Why this matters commercially
The European Accessibility Act came into force on 28 June 2025 with no transition period and no cap on damages. UK employment tribunals are seeing a sharp increase in disability discrimination claims, with the average award exceeding £850,000 in the most recent data. Across 517 cases, not a single award was capped.
Organisations that can demonstrate they went beyond WCAG, that they proactively assessed for neurodivergent usability and addressed the findings, have a significantly stronger legal position than those who stopped at the technical minimum.
What the NDC standard adds
The NDC standard (NDC-2026-001) was built to fill this gap. Seven domains, thirty-five criteria, 140 maximum points. It covers cognitive load, reading and language accessibility, sensory design, predictability, executive function support, emotional safety, and personalisation. Each criterion has a defined scoring method. Each assessment produces a structured report with evidence and actionable remediation guidance.
It does not replace WCAG. It sits alongside it. A product should meet both WCAG 2.2 AA and the NDC standard for comprehensive accessibility coverage.
WCAG tells you whether a product is technically accessible. The NDC standard tells you whether it actually works for the people using it.
Technically compliant. Practically unusable. That is the gap. The NDC exists to close it.
The Neurodiversity Design Council is the UK's first standards body for neurodiversity-inclusive digital design. Read the full standard or submit your product for assessment.