Designing Digital Spaces for Neurodivergent Individuals
A digital space can make the work easier or harder
A website can be technically functional and still ask too much of the person using it. The instructions are scattered. A menu changes position. A form erases an answer after an error. A video starts unexpectedly. Every one of those decisions uses attention that someone came to spend on the actual task.
In the video, I ask what happens when we design digital spaces with neurodivergent people in mind. The answer is not a single visual style or a checklist labelled “neurodivergent friendly.” People differ, and the same person may need different things on a tired day. We can still make useful choices: clearer language, predictable paths, fewer avoidable interruptions, and ways to control how content is presented.
This is an invitation to look at the whole journey. Can someone understand where they are, find what they need, complete the next step, recover from a mistake, and leave without feeling foolish? Those questions belong in the first design meeting, not at the end of a build.
Start with the task, not a diagnosis
“Neurodivergent” covers varied experiences, including ADHD, autism, dyslexia, dyspraxia and more. It does not describe one set of preferences. A dense page may be manageable for one person and exhausting for another. An animation that helps explain a process may distract someone else. A text-heavy instruction may be easier to revisit than a video; another person may prefer to hear it.
Ask what people are trying to do and where they lose their place. A person applying for a service may need to know what information to gather before starting. Someone reading a long explanation may need headings and a useful summary. A customer with limited time may need to pause a form and return. These are observable needs you can test without making assumptions about a visitor’s identity.
The W3C’s cognitive accessibility guidance covers clear structure, familiar controls, understandable steps and user testing. It is broader than a single diagnosis and useful alongside the Web Content Accessibility Guidelines (WCAG) 2.2. WCAG gives testable accessibility criteria; cognitive usability also asks whether a person can actually follow the experience. Both matter.
Make orientation easy
A visitor should be able to tell what a page is for in a few seconds. Give it a specific title. Use headings that say what is in each section. Put the answer to the main question early, then give detail for those who want it. Avoid a wall of introductory copy that delays the point.
Keep navigation in a consistent place across pages. Name links by their destination or action. “See eligibility requirements” tells me more than “Learn more.” Where a process has several stages, show the steps, what has been completed and what comes next. Do not make someone hold the entire process in working memory.
A predictable layout does not have to be dull. It gives people a reliable map so they can focus on the content. WCAG’s consistent navigation criterion addresses repeated navigation mechanisms. Real usability testing can then show whether people recognize the labels and find their way.
Write for the next decision
Plain language respects the reader’s time. It is not childish language. Use familiar words, explain necessary terms, and keep instructions close to the action they describe. Break a complex task into small steps without hiding vital information in separate screens.
Consider the difference between “Your submission has encountered an error” and “We could not save your form. Check the postcode field; your other answers are still here.” The second sentence tells someone what happened and what to do. It also reduces the fear that their work disappeared.
If a page explains a choice, state the consequences before the button. If a fee, deadline or required document matters, bring it into the decision itself. Do not rely on colour alone to show a warning. Clear wording and a visible label help a person notice and understand it.
Long content can still work. A summary, meaningful headings, short paragraphs and a table of contents make a detailed page easier to navigate. Let people skim and return. Avoid treating a fixed word count as a sign of accessibility; the useful length is the length needed to answer the question well.
Give people control over stimulation
Unexpected movement, sound and interruptions can make a task harder. Avoid autoplaying audio and video. Let people pause, stop or hide movement where appropriate. Keep flashing effects out of the experience. Do not place a shifting carousel between a person and the action they came to complete.
Use legible text, sufficient contrast, responsive spacing and layouts that work when text is enlarged. A user’s browser settings and assistive technology are part of their control. Do not block zoom or force a particular font as if it were a universal solution. Choices such as captions, a transcript and an adjustable playback speed can make video more usable for different people.
A calm default is helpful, but the key is agency. Let a visitor open additional detail when they want it. Make notifications relevant and dismissible. If something changes on the page, tell them in a way they can perceive without taking away focus. A design can be expressive while still giving the user room to think.
Build forms that remember and explain
Forms are where friction becomes expensive. Tell people what they will need before they start. Label every field clearly. Show which fields are required and give examples for unfamiliar formats. Avoid asking for the same information twice without a good reason.
When validation fails, identify the field and explain the correction in words. Keep answers already entered. Make errors visible near the field and in an overview if the form is long. Do not make someone hunt through a page for a red outline. If there is a time limit, explain it and offer a way to extend or save progress when possible.
A form should work with a keyboard, screen reader, zoom and touch. Focus should move in a sensible order and remain visible. WCAG guidance on focus order and input assistance are practical starting points. Test real tasks, including a deliberate mistake and recovery, rather than only the happy path.
Offer more than one useful route
A transcript can help someone who cannot listen to a video, someone who processes text more comfortably, or someone who wants to find one sentence again. Captions help in many situations but do a different job from a transcript. For an important graphic, give the essential meaning in accessible text. For instructions, consider a written sequence alongside a demonstration.
Alternative routes should lead to the same important information. Do not put the critical deadline in a video while the text only says “watch to find out.” Equally, do not assume an icon explains a complex choice. Labels are usually more reliable than guesswork.
This does not mean making every page in five formats. Start with the task and its stakes. If someone misses a key point because the only route was hard for them to use, that is a design problem you can fix.
Test with people, then listen to what failed
Automated checks can catch missing labels, contrast issues and some structural errors. They cannot tell you whether a menu makes sense or whether a person trusts the next step. Include neurodivergent people in research and usability testing, compensate them for their time, and ask them to perform realistic tasks. The W3C guidance specifically calls for involving people with cognitive and learning disabilities in design and testing.
Watch for hesitation, backtracking and abandonment without interpreting every pause as a personal deficit. Ask what the person expected to happen. Allow different ways of giving feedback, including written comments after the session. One tester does not speak for everyone, so look for patterns and keep testing after changes.
Your analytics can show where people leave a form, but not why. Combine them with direct feedback. If the same step fails repeatedly, inspect the language, order, labels and feedback before blaming the visitor. Accessibility is ongoing work: content, products and people’s circumstances change.
A practical review you can do today
Pick one important journey, such as finding a service, booking a call or completing a contact form. Start on the homepage and try to finish using only the keyboard. Increase the text size. Read the headings without the body copy and ask if the page still makes sense. Then make a mistake in the form and see whether you can recover without starting again.
Next, ask a person who did not build the page to attempt the same task. Give them the goal, not a guided tour. Note each place where the interface asks them to remember something, guess a label or reverse course. Fix the most disruptive points first. A clear heading or a retained form answer can have more value than a decorative redesign.
Document what you learned. Repeat the review when the content or flow changes. A digital space becomes more welcoming through specific improvements that people can actually feel while using it.
Questions people ask
Is there one design that works for every neurodivergent person?
No. Needs and preferences vary. Clear structure, predictable controls and user choice create a better starting point, then testing with people doing real tasks shows what needs to change.
Does passing WCAG mean the site is easy to use?
WCAG conformance matters, but it does not answer every usability question. Test whether people can find, understand and complete the task, including error recovery.
Should I replace long text with video or icons?
Not automatically. Give the essential information in accessible text, and use video, captions, transcripts or visuals when they add a useful route. A labelled control is easier to understand than an unexplained icon.
What should I fix first if my resources are limited?
Choose a high-value journey and remove the biggest obstacles: unclear instructions, inconsistent navigation, missing labels, lost form answers or inaccessible media. Verify the change with users.
Keep exploring
For the wider AI and access question, watch How AI Bias Can Exclude Neurodivergent People. For a related design decision, see How AI Can Affect Mental Health and Emotional Well-Being. If you are interested in how a specific learning difference can show up in digital work, read Dyslexia: More Than Reading Problems.
The question I keep coming back to is simple: what does this design ask the person to carry, and what could the system carry for them? A clear path gives people more of their attention back for the reason they came.
Go deeper
Read Feeling Seen by a Machine online, or keep the complete edition on Kindle or in paperback.
Read the book