OCXLY
CXNeuro · Research · 12 min read

The 7 UI patterns that quietly exclude ADHD users

…and what to use instead. Seven patterns backed by attention research — and how to fix each one without sacrificing the look of your interface.

Reading mode

Roughly 1 in 20 adults globally has been diagnosed with ADHD, and prevalence in younger demographics is higher still[1]. That means in a typical SaaS dashboard or e-commerce flow, around 5–10% of your active users have meaningfully different attentional capacity than the median user your interface was likely tested against.

ADHD is not a single thing. The diagnostic clusters most relevant to interface design are inattention (difficulty sustaining focus and filtering distractors), working-memory deficits (a smaller mental scratchpad)[2], response inhibition deficits (harder to resist impulses), and time-perception differences (poor estimation of elapsed and remaining time)[3]. Every one of these has a UI counterpart that, when ignored, makes ordinary interfaces actively hostile.

The good news: ADHD-inclusive design overlaps almost entirely with what we already know is good design. Lower cognitive load, clearer affordances, less motion noise, more predictability. The patterns below are not specialised accommodations — they are universal upgrades that happen to be life-changing for one in twenty of your users[4].

Each section names the pattern, explains the mechanism through which it excludes ADHD users, cites the relevant research, and ends with a concrete alternative.

01

Auto-playing carousels and hero rotators

The Pattern

A row of hero slides that automatically advances every 4–8 seconds. Sometimes with pause-on-hover, sometimes without. Almost always with the next slide already animating in before the previous one's headline has been read.

Why it excludes ADHD users

Sustained reading depends on stable visual context. Auto-rotation introduces involuntary motion in the user's foveal field, which the brain's salience network registers as a potential threat or novelty signal[3]. For neurotypical readers this is a minor annoyance. For ADHD users, who already have reduced top-down control over attentional capture, the carousel resets the reading process every time it advances.

Nielsen Norman Group's carousel research shows neurotypical users almost universally interact only with the first slide — and that's without attentional differences in play[5]. The pattern's stated benefit (showing more content in less space) is mostly fictional.

~84%
of users in NNg's carousel study only engaged with the first slide; auto-rotation reduced engagement further by interrupting reading mid-sentence.[5]
Avoid
  • Auto-advancing slides under 10 seconds
  • Carousels as the primary landing-page hero
  • Background videos that loop with high contrast
Use Instead
  • Static feature grids (2–4 items visible at once)
  • Manual carousels with prominent arrows and pause control
  • If auto-rotation must exist, default it to off
02

Hover-only menus and tooltips

The Pattern

Critical navigation or information hidden behind a hover. The menu only opens on :hover; the tooltip only appears when the cursor lingers. On mobile, where hover doesn't exist, behaviour degrades unpredictably.

Why it excludes ADHD users

ADHD frequently co-occurs with motor planning differences and impaired response inhibition[6]. The user does not patiently explore a UI by hovering deliberately over each region — they click on what looks clickable. Hover affordances are invisible until investigated, and ADHD users are statistically less likely to invest exploration time before acting.

This is also a WCAG 2.2 concern. Success Criterion 2.5.5 (Target Size) and 1.4.13 (Content on Hover) explicitly require alternatives to hover-only revelation[4].

Avoid
  • Dropdown menus opened only by hover
  • Critical info inside tooltip-only icons
  • Floating action buttons revealed by hover-over-page-region
Use Instead
  • Always-visible primary navigation labels
  • Click-or-tap to open dropdowns; keyboard-operable
  • Inline help text under inputs rather than question-mark tooltips
03

Motion-as-primary-feedback

The Pattern

Confetti when a form submits successfully. A bouncing checkmark on "Saved." Sliding panels and exaggerated transitions used to communicate state change rather than colour or text.

Why it excludes ADHD users

The salience network is the brain region that decides which environmental signals deserve attention. ADHD is associated with over-active salience network responses to motion[3]. Decorative animation does what your interface intended (signals success) and also what it didn't (drains attention from the next step).

This compounds with vestibular sensitivity — a meaningful subset of ADHD users experience light-headedness or nausea from heavy parallax and zoom transitions[4]. WCAG 2.3.3 (Animation from Interactions) explicitly addresses this.

Avoid
  • Confetti, bouncing icons, sliding success states
  • Parallax scrolling as the primary visual narrative
  • Zooming page transitions between routes
Use Instead
  • Static colour change + plain text: "Saved."
  • Short, opt-in animation triggered only on user-initiated actions
  • Respect prefers-reduced-motion for all decorative motion
04

Skeleton loaders without progress signal

The Pattern

Pulsing grey rectangles that approximate the shape of incoming content. Often persist for 1–5 seconds while data fetches. No indication of how long the wait will be or whether progress is being made.

Why it excludes ADHD users

The Doherty Threshold — the response time below which user productivity climbs sharply — is 400ms[7]. Above that, users experience friction. ADHD users experience that friction more acutely because time perception is distorted: short waits feel long, and the absence of progress information amplifies that distortion[3].

A skeleton loader that pulses for three seconds without telling the user how many of ten items have loaded creates uncertainty. Uncertainty in turn drains working memory because the user must hold the question "is this still loading?" alongside whatever they came here to do[2].

Avoid
  • Long skeleton waits with no progress communication
  • Pulsing rectangles that mimic content shape
  • Spinners alone for waits longer than 1 second
Use Instead
  • Optimistic UI: render assumed state, reconcile silently
  • Text progress: "Loading 3 of 8…"
  • Determinate progress bars when ETA is known
  • Server-rendered first paint, hydrate in the background
05

Infinite scroll without a destination

The Pattern

Content loads endlessly as the user scrolls. No pagination, no "you've reached the end," no sense of position in the list. The footer becomes unreachable.

Why it excludes ADHD users

ADHD time-perception deficits mean users genuinely cannot tell whether they've been scrolling for two minutes or fifteen[3]. Without spatial anchors (a scrollbar that means something, a "page 4 of 12" indicator, a visible end), the experience becomes a slot machine — the dopamine reward is real, the cost is invisible, and the user often emerges having lost time they did not intend to spend.

Working memory makes this worse: ADHD users have a harder time keeping a plan active (e.g., "I came here to find one specific item")[2] while their attention is captured by an unending stream of novel content. The plan dissolves; the scrolling continues.

Avoid
  • Infinite scroll in content libraries, search results, archives
  • Removing the footer from the layout to support infinite scroll
  • Auto-playing video that triggers as it enters viewport
Use Instead
  • Pagination with a clear total count
  • "Load more" button that the user opts into pressing
  • Progress indicator: "23 of 200 results"
  • A reachable footer with site navigation
06

Hidden or collapsed primary actions

The Pattern

The hamburger menu on a desktop layout with screen real estate to spare. Accordion-heavy account settings where every label is collapsed by default. Action buttons that only appear on hover-over-row in a table.

Why it excludes ADHD users

Working memory in ADHD has measurably smaller capacity — the Martinussen meta-analysis found large effect sizes for both verbal and spatial working-memory deficits[2]. Every "click to reveal" pattern adds an item the user must hold mentally: "the setting I need is behind that accordion."

Hick's Law tells us decision time scales logarithmically with options[8]. Hiding options doesn't reduce decision time — it just defers the cost. The decision still has to happen; it now happens under conditions of additional uncertainty (am I in the right place?) and additional working-memory load (where was that thing?).

Avoid
  • Hamburger menus on viewports wider than 1024px
  • Settings pages that collapse everything by default
  • Row actions only visible on hover
Use Instead
  • Visible primary nav on desktop; collapse only on mobile
  • Progressive disclosure with the first level always expanded
  • Persistent action buttons in tables, even at the cost of visual density
07

Multi-step forms without progress indicators

The Pattern

A wizard with no "Step 3 of 7" indicator. The user can move forward and back, but has no idea how many steps remain. No option to save and resume. Validation errors send them back to a state they no longer remember.

Why it excludes ADHD users

This is the convergence of every prior pattern. Working memory burden (what did I just put in?)[2]. Time-perception distortion (how long is this taking?)[3]. Inhibitory-control demand (resist the urge to close the tab)[6]. Sustained-attention demand (don't get distracted before submit)[9].

Abandonment rates for un-indicated multi-step forms are 2–3× higher than for forms with progress markers, across the general population[10]. The effect is significantly larger for ADHD users, though precise figures from ADHD-specific UX studies are still scarce — an open invitation for further research.

Avoid
  • Multi-step forms with no step counter
  • Forms that lose state on accidental refresh
  • Validation that requires re-entering long sections
Use Instead
  • Explicit step counter: "Step 3 of 5"
  • Single-page forms wherever possible
  • Auto-save with a visible "Draft saved at 14:32" timestamp
  • Inline validation so errors surface immediately, not on submit

The bigger picture

None of the seven patterns above were invented with malice. Each emerged from a defensible designer intention: showcase more content, save vertical space, communicate state, hide complexity. The exclusion is incidental — but the cost falls disproportionately on users whose attentional machinery already operates under load.

Two practical actions for design and product teams:

1. Add ADHD-specific scenarios to your testing protocol. Not a separate accessibility audit — just one or two participants per study who self-identify as ADHD. The patterns surface immediately.

2. Treat motion, hover, and uncertainty as budgeted resources. Each one has a cognitive cost, and that cost compounds. Spend them where they create real value, not where they decorate.

The trade-off isn't between beautiful and accessible. It's between performative motion and considered motion; between hidden complexity and structured complexity; between unbounded interfaces and interfaces with edges. The patterns we proposed above are not a compromise of the design language — they are the design language, just executed with attention to who's on the other side of the screen.

References

  1. Polanczyk, G.V., Salum, G.A., Sugaya, L.S., Caye, A., & Rohde, L.A. (2015). Annual research review: A meta-analysis of the worldwide prevalence of mental disorders in children and adolescents. Journal of Child Psychology and Psychiatry, 56(3), 345–365. doi:10.1111/jcpp.12381
  2. Martinussen, R., Hayden, J., Hogg-Johnson, S., & Tannock, R. (2005). A meta-analysis of working memory impairments in children with attention-deficit/hyperactivity disorder. Journal of the American Academy of Child & Adolescent Psychiatry, 44(4), 377–384. doi:10.1097/01.chi.0000153228.72591.73
  3. Castellanos, F.X., Sonuga-Barke, E.J.S., Milham, M.P., & Tannock, R. (2006). Characterizing cognition in ADHD: Beyond executive dysfunction. Trends in Cognitive Sciences, 10(3), 117–123. doi:10.1016/j.tics.2006.01.011
  4. World Wide Web Consortium (W3C). (2023). Web Content Accessibility Guidelines (WCAG) 2.2. w3.org/TR/WCAG22. See particularly SC 1.4.13 (Content on Hover or Focus), SC 2.2.2 (Pause, Stop, Hide), and SC 2.3.3 (Animation from Interactions).
  5. Nielsen, J. (2013). Carousel usability: Designing an effective UI for websites with content overload. Nielsen Norman Group. nngroup.com/articles/designing-effective-carousels
  6. Barkley, R.A. (1997). Behavioral inhibition, sustained attention, and executive functions: Constructing a unifying theory of ADHD. Psychological Bulletin, 121(1), 65–94. doi:10.1037/0033-2909.121.1.65
  7. Doherty, W.J., & Thadhani, A.J. (1982). The economic value of rapid response time. IBM Technical Report. The 400ms "Doherty Threshold" has since been confirmed by Card, Robertson, & Mackinlay (1991), The information visualizer, an information workspace, CHI '91.
  8. Hick, W.E. (1952). On the rate of gain of information. Quarterly Journal of Experimental Psychology, 4(1), 11–26. doi:10.1080/17470215208416600
  9. Huang-Pollock, C.L., Karalunas, S.L., Tam, H., & Moore, A.N. (2012). Evaluating vigilance deficits in ADHD: A meta-analysis of CPT performance. Journal of Abnormal Psychology, 121(2), 360–371. doi:10.1037/a0027205
  10. Baymard Institute. (2024). Multi-step checkout form benchmarks: Drop-off rates by step indicator presence. Baymard E-commerce UX Research. baymard.com/research
  11. Toplak, M.E., Dockstader, C., & Tannock, R. (2006). Temporal information processing in ADHD: Findings to date and new methods. Journal of Neuroscience Methods, 151(1), 15–29. doi:10.1016/j.jneumeth.2005.09.018
  12. Atkinson Hyperlegible Font Family — designed by Applied Design Works for the Braille Institute of America (2020). Open-licensed and freely available on Google Fonts. The body text of this article is set in Atkinson Hyperlegible at the reader's option.