ND-Friendly Web Design — UX for the overlooked 20%
Last updated: April 2026 · Reading time: 8 minutes
The overlooked accessibility audience
When teams talk about accessibility, most think of screen readers, colour contrast, keyboard navigation. That is right and important. It is only part of the picture.
Around 15–20% of all users are neurodivergent — they process information differently. ADHD, autism spectrum, high sensitivity, and dyslexia/dyscalculia are included (CDC 2023, NIH 2024). For them, what decides is not the colour contrast but the stimulus load. Not the ARIA label but sentence length. Not the tab order but the predictability of navigation.
Our neurodivergence self-test shows which of these four areas you personally recognise. This article shows what follows for digital products.
Why ND-friendliness delivers EAA compliance
Since June 2025, the European Accessibility Act (EAA) applies to many B2C businesses. The minimum standard is WCAG 2.1 AA. Three success criteria particularly affect ND users:
- 3.1.5 Reading Level (AAA): understandable language for users with lower reading literacy — covers dyslexia.
- 2.2.2 Pause, Stop, Hide (A): automatic motion is pausable — covers HSP and ADHD.
- 3.2.3 Consistent Navigation (AA): same elements in the same place — covers autism spectrum.
Building ND-friendly delivers these criteria automatically. Checking WCAG boxes alone often misses the ND users.
Four principles for ND-friendly UX
01 Plain language
Short sentences, active verbs, concrete nouns. Target level B1–B2 for main navigation and error messages. Reduces load for dyslexic users, cognitively tired users, and anyone who scans rather than reads.
02 Reduced stimuli
No autoplay videos. No rotating banners. No notification flood. Motion only on user intent and respecting `prefers-reduced-motion`. Audio never surprises.
04 Generous error tolerance
Forms that handle typos and different orderings. Undo and auto-save. Confirmation before irreversible actions. Clear, helpful error messages — never just “invalid input”.
Four concrete patterns from our practice
Principles stay abstract. Here are four patterns we have shipped in client projects, and that measurably move the needle.
Forms with auto-save and visible progress
Every field change persists the draft. The user sees a subtle “Saved” indicator. Closing the browser tab or losing network does not lose input. Users with time-blindness (often ADHD) benefit most.
Typography dials for dyslexia
Minimum font size 18 px, line height 1.6, max 75 characters per line. Optional OpenDyslexic font via toggle. Paragraphs no longer than 3–4 sentences. Lowers reading effort for dyslexic users by up to 40% (British Dyslexia Association 2023).
Stimulus reduction as a theme option
Alongside light and dark mode, add a “Focus” mode: no animation, monochrome accents, wider spacing, larger touch targets. Reachable in one click from the theme toggle. HSP and autistic users stay on the page longer.
Predictable CTA positioning
Primary CTA always right, secondary always left, tertiary as plain text link only. No floating buttons that change position with scroll depth. Autistic users build mental maps — don't destroy them.
How to measure ND UX
Standard UX metrics (bounce, time-on-page, conversion) are not enough. Add:
Qualitatively, moderated sessions with ND users — via Fable or your own tester pool — surface patterns no heatmap reveals: the moment a user drops out because three stimuli compete.
How arocom builds ND-friendly
We evaluate our projects against two layers by default: the WCAG 2.1 AA checklist and an in-house ND heuristic that covers:
- Stimulus inventory per page: how many competing motions, colours, elements run in parallel?
- Language score: Hemingway-App readability, target level B1–B2 for navigation and error text.
- Reversibility check: which actions are irreversible, which need confirmation?
- Consistency audit: do the same functions show up differently in different places?
Findings feed into our development service and into the Future Check audit.
Frequently asked
Isn't ND-friendly design just good UX for everyone?
Partly. Plain language and predictable navigation help everyone. But certain calls — OpenDyslexic as an option, per-field auto-save, a focus mode — help ND users more noticeably. Neurotypical users barely register them; ND users feel the difference between “works” and “doesn't work”.
Is WCAG 2.2 required or does 2.1 AA suffice?
The EAA mandates EN 301 549, which aligns with WCAG 2.1 AA as the minimum. WCAG 2.2 adds 9 new criteria that further help ND users — notably 3.3.7 “Redundant Entry” (less re-typing in forms). We build new projects against 2.2 directly.
How plain must the plain language on the homepage be?
Main nav and CTAs: B1–B2. Introductory copy: B2. Specialist articles: B2–C1 allowed, as long as a B1-level summary exists. Our editorial workflow checks Hemingway readability for every new article.
Must we offer a dyslexia font?
Not required, but recommended. Studies are mixed (Wery/Diliberto 2017), but some dyslexic users swear by it, and the toggle costs little (webfont + switch). As a default font, pick easily distinguishable sans-serifs like Atkinson Hyperlegible, Lexend, or Inter.
How does Inclusion & Accessibility hold up on your website? The Future Check shows where the biggest levers are — in 2–4 weeks.
Kopiert diesen Prompt und fügt ihn in ChatGPT, Claude oder eine andere KI ein — ihr bekommt einen persönlichen Lernplan zu „ND-Friendly Web Design“.
Du bist ein erfahrener Coach für Inclusion & Accessibility. Ich möchte das Thema "ND-Friendly Web Design" verstehen und ...Was this article helpful?