How to conduct accessibility research with neurodivergent participants for complex data visualization tools

Data visualization tools—dashboards, charting platforms, analytics suites—are among the most cognitively demanding software products people use. They require users to interpret spatial relationships, decode color-coded information, read dense labels, hold multiple variables in working memory, and switch between overview and detail views. For neurodivergent users, these demands can create barriers that conventional usability testing rarely surfaces.

Conducting accessibility research with neurodivergent participants is not fundamentally different from good research practice in general. But it does require deliberate adjustments to recruitment, session design, facilitation, and analysis. This guide walks through each phase.

Why data visualization tools need neurodivergent accessibility research

Most accessibility work in software focuses on screen reader compatibility, keyboard navigation, and color contrast—important work, but insufficient for complex data visualization. Neurodivergent users may have no difficulty with screen readers or keyboard shortcuts and still struggle with a product that overwhelms working memory, relies on implicit visual hierarchies, or presents information in rigid, linear sequences.

Consider a few examples:

• A user with ADHD may find a dense, multi-panel dashboard difficult to parse because there is no clear entry point or visual hierarchy guiding attention.
• A user with dyscalculia may misinterpret axis scales, percentages, or numerical labels, especially when the formatting is inconsistent.
• An autistic user may process a complex scatter plot more accurately than a neurotypical user but struggle when the interface requires rapid context-switching between views.
• A dyslexic user may have difficulty reading rotated axis labels, small-font legends, or tooltips that disappear too quickly.

These are not edge cases. An estimated 15–20% of the global population is neurodivergent. If your data visualization tool does not work for these users, you are excluding a significant portion of your potential user base—and likely degrading the experience for many neurotypical users as well, since the barriers neurodivergent users encounter often reflect general usability problems.

Scoping your research

Neurodivergence is not a single condition but a spectrum of cognitive differences. Trying to study "neurodivergent accessibility" as a single research question will produce unfocused findings that are difficult to act on. Scope your research by identifying:

Which cognitive profiles are most relevant

Consider the core interactions your data visualization tool requires. If the tool relies heavily on numerical interpretation, users with dyscalculia are a priority. If the tool demands sustained attention across long workflows, users with ADHD are a priority. If the tool uses unconventional or metaphorical visualizations, autistic users who may interpret visual information literally are a priority.

You do not need to cover every form of neurodivergence in a single study. It is better to run a well-scoped study with one or two participant groups and produce actionable findings than to attempt comprehensive coverage and produce vague ones.

Which tasks and views to evaluate

Complex data visualization tools often have dozens of views and hundreds of possible interactions. Select the tasks that are most common, most critical, or most likely to present cognitive barriers. Good candidates include:

• Reading and interpreting a default dashboard view
• Filtering, sorting, or drilling into data
• Comparing two or more data series
• Configuring a custom visualization
• Exporting or sharing a chart or report

What outcomes you are measuring

Decide upfront whether you are evaluating comprehension accuracy (did the user correctly interpret the data?), task efficiency (how long did it take?), cognitive load (how effortful did the task feel?), or emotional response (did the experience cause frustration, anxiety, or disengagement?). Each requires different methods.

Recruiting neurodivergent participants

Recruitment is where many accessibility research projects stall. Neurodivergent participants are not hard to find—they are hard to find if you rely on the same recruitment channels and screening processes you use for general usability studies.

Build relationships with communities

Partner with neurodivergent advocacy organizations, online communities (subreddits, Discord servers, forums), and professional networks. Many neurodivergent adults are eager to participate in research that will improve the tools they use, but they want to know that researchers understand and respect their experience. Cold outreach to a community you have never engaged with will not produce good results.

Allow self-identification

Many neurodivergent adults do not have formal clinical diagnoses, particularly those who were socialized as women or who grew up in communities with limited access to diagnostic services. Requiring a formal diagnosis as a screening criterion will exclude a significant portion of your target participants and introduce demographic bias into your sample. Allow participants to self-identify.

Be transparent about the study

Your screener and recruitment materials should clearly state:

• The purpose of the research (improving the product's accessibility)
• What participants will be asked to do
• How long the session will take
• What accommodations are available
• How data will be used and stored
• Compensation amount and payment timeline

Vague descriptions create uncertainty, and uncertainty disproportionately discourages neurodivergent participants who may have had negative experiences with research or clinical settings in the past.

Offer flexibility in participation format

Some participants will prefer remote sessions; others will prefer in-person. Some will do their best work in a live, moderated session; others will produce richer feedback in an asynchronous, self-paced format. Offering multiple participation options is not just a courtesy—it directly affects data quality.

Designing your research sessions

Session design requires more deliberate planning than standard usability testing. The goal is to create conditions that allow every participant to demonstrate their actual capabilities with the product, rather than measuring their ability to perform under conditions that disadvantage them.

Provide materials in advance

Send participants a session guide at least 48 hours before the session. Include the schedule, the types of tasks they will be asked to do (without revealing specific details that would bias the results), and any technical requirements. Neurodivergent participants often perform better when they know what to expect.

Build in breaks

Sessions for complex data visualization tools should include explicit break points. A 60-minute session might include a five-minute break at the halfway point. Let participants know they can also take unscheduled breaks at any time. Cognitive fatigue accumulates faster when a user is navigating both a complex interface and the social demands of a research session.

Use concrete, unambiguous task prompts

Avoid task prompts that require participants to infer what you mean. Instead of "explore this dashboard and share your thoughts," try "look at this dashboard and tell me which product category had the highest sales in March." Concrete tasks produce clearer behavioral data and reduce the anxiety some participants feel when given open-ended instructions.

This does not mean you should avoid open-ended exploration entirely. It means you should separate structured tasks from open exploration and signal the shift clearly: "Now I'd like you to spend a few minutes looking around the dashboard freely. There are no right answers—I'm interested in what you notice."

Offer multiple response modes

Some participants will articulate their experience fluently in a think-aloud protocol. Others will find concurrent verbalization disruptive to their cognitive process. Offer alternatives:

• Retrospective think-aloud (complete the task silently, then walk through what happened)
• Written responses (typed or handwritten)
• Annotation (marking up a screenshot to indicate areas of confusion or difficulty)
• Rating scales with follow-up questions

Manage sensory environment

If sessions are in person, control for lighting, noise, and visual clutter in the testing space. If sessions are remote, ask participants in advance whether they have any preferences—some may want cameras off, some may want to use chat instead of voice for parts of the session.

Facilitation

The facilitator's role in accessibility research with neurodivergent participants requires particular care in a few areas.

Avoid pathologizing language

Frame questions around the participant's experience with the product, not around their neurodivergence. Instead of "does your ADHD make it hard to focus on this dashboard?" ask "how easy or difficult is it to find the information you need on this screen?" The participant will share context about their cognitive experience if and when it is relevant.

Allow processing time

Some neurodivergent participants need more time to process questions and formulate responses. Resist the urge to rephrase or prompt after a few seconds of silence. Wait. If a participant seems stuck, ask "would you like me to repeat the question?" rather than restating it in different words, which introduces a new processing demand.

Check in on comfort and fatigue

Periodically ask participants how they are doing. A simple "how are you feeling—ready to continue, or would a break be helpful?" gives participants explicit permission to pause without having to initiate the request themselves.

Analyzing your findings

Analysis of accessibility research with neurodivergent participants follows the same principles as any qualitative research analysis, with a few additional considerations.

Look for patterns across and within cognitive profiles

Some findings will be specific to a particular type of neurodivergence—for example, axis label formatting issues that specifically affect dyslexic users. Others will surface across multiple cognitive profiles—for example, a lack of visual hierarchy that makes the dashboard difficult for users with ADHD, autism, and dyslexia alike. Distinguish between these in your analysis, because they lead to different design responses.

Document the accommodations that helped

If a participant used a browser zoom, changed a color theme, or asked to see data in a table instead of a chart, document that. These workarounds are design insights—they tell you what the product should offer natively.

Avoid generalizing from small samples

Neurodivergent experiences are highly individual. Two autistic users may have completely different responses to the same visualization. Report your findings as observations from specific participants rather than universal statements about how neurodivergent people experience your product.

Tools like Dovetail can help during this phase by centralizing session recordings, transcripts, and tagged observations in one place. When you are tracking findings across multiple participants with different cognitive profiles, having a structured repository prevents insights from getting lost and makes it easier to identify which patterns are strong enough to act on.

Turning findings into design changes

Accessibility research only matters if it changes the product. When presenting findings to your team, focus on specificity and feasibility.

Prioritize by severity and frequency

A finding that affects comprehension accuracy (the user misread the data) is more severe than one that affects preference (the user found the color palette unpleasant). A finding that appeared across most participants is more urgent than one that appeared once.

Propose design responses, not just problems

Instead of reporting "participants with ADHD struggled with the dashboard," describe what specifically caused the difficulty and what might resolve it: "Participants with ADHD had difficulty identifying the primary metric on the default dashboard view. Adding a visual entry point—such as a larger, more prominent summary card at the top—could reduce the scanning effort required."

Build accessibility checks into your ongoing research practice

Neurodivergent accessibility research should not be a one-time project. Include neurodivergent participants in your regular usability studies, and evaluate new features for cognitive accessibility before launch. Over time, this shifts accessibility from a remediation effort to a design standard.

Common mistakes to avoid

Treating neurodivergent participants as a monolith. A study that recruits "neurodivergent users" without distinguishing between cognitive profiles will produce findings that are too diffuse to act on.

Over-accommodating to the point of invalidating findings. If you simplify tasks so much that they no longer reflect real product usage, your findings will not generalize. The goal is to remove unnecessary barriers while preserving ecological validity.

Focusing only on deficits. Neurodivergent users often have cognitive strengths that are relevant to data visualization—strong pattern recognition, high tolerance for detail, systematic thinking. Your research should surface these strengths as well as difficulties, because they inform design decisions too.

Running the study without neurodivergent input on study design. If possible, involve neurodivergent consultants or advisors in designing your research protocol. They will catch assumptions and barriers that neurotypical researchers may miss.

Building a more inclusive research practice

Accessibility research with neurodivergent participants for data visualization tools is demanding work. It requires careful scoping, deliberate recruitment, flexible session design, and analysis that resists easy generalizations. But the payoff is substantial: products that are more usable for everyone, not just the users whose cognitive profiles happen to match the designer's assumptions.

The insights that come from this research tend to be specific, concrete, and directly actionable—exactly the kind of findings that product teams can turn into meaningful improvements. And when those findings are organized and shared effectively across a team, using a research repository like Dovetail, they compound over time into a deeper, more nuanced understanding of how diverse users actually experience your product.