--- title: "ND-Friendly Web Design: UX for the overlooked 20%" lang: en type: knowledge canonical: https://www.arocom.de/en/knowledge/inclusion/nd-friendly-webdesign alternate: https://www.arocom.de/wissen/inklusion/nd-freundliches-webdesign author: "Axel Roth" last_updated: 2026-07-28 --- # ND-Friendly Web Design: UX for the overlooked 20% Around 15–20% of users are neurodivergent, ADHD, autism spectrum, high sensitivity, or dyslexia/dyscalculia. They are the most-overlooked accessibility audience. ND-friendly web design rests on four principles: plain language (B1 level, short sentences), reduced stimuli (no autoplay, motion only on user intent), predictable navigation (stable patterns, clear URLs, breadcrumbs), generous error tolerance (undo, auto-save, confirmation for irreversible actions). These patterns also deliver WCAG 2.1 AA, the minimum required by the European Accessibility Act. ## ND-Friendly Web Design, UX for the overlooked 20% ## 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](https://www.cdc.gov/adhd/data/index.html), [NIH 2024](https://www.ninds.nih.gov/health-information/disorders/autism-spectrum-disorder)). 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](https://www.arocom.de/en/knowledge/inclusion/neurodivergence-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)](https://www.arocom.de/en/accessibility) applies to many B2C businesses. The minimum standard is [WCAG 2.1 AA](https://www.w3.org/TR/WCAG21/). 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. ### 03 Predictable navigation Same elements in the same place. No scroll hijacks, no overlay pop-ups without user trigger. Breadcrumbs, clear URLs, and stable navigation structure act as cognitive anchors. ### 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](https://cdn.bdadyslexia.org.uk/uploads/documents/Advice/style-guide/BDA-Style-Guide-2023.pdf)). ### 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: **40%** Less reading effort with dyslexia-safe typography ([British Dyslexia Association, 2023](https://cdn.bdadyslexia.org.uk/uploads/documents/Advice/style-guide/BDA-Style-Guide-2023.pdf)) **15–20%** Of users are neurodivergent (DACH/EU) ([CDC, NIH, 2023–2024](https://www.cdc.gov/adhd/data/index.html)) **2.5×** Higher completion with auto-save ([Baymard Institute, 2024](https://baymard.com/blog/save-for-later-feature)) Qualitatively, moderated sessions with ND users, via [Fable](https://makeitfable.com/) 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](https://www.arocom.de/en/services/development) and into the [Future Check](https://www.arocom.de/en/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](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/), 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](https://link.springer.com/article/10.1007/s11881-016-0127-1)), 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.