Website Accessibility for Dyslexia, ADHD, and Memory Differences

Dyslexia, ADHD, and memory differences change how people experience a website, and each one does it differently. Every page makes four demands of its visitors: reading the text, holding attention, remembering what came before, and keeping up with the pace. When a site asks too much on any of them, users stall or leave.

This page covers where websites make those demands too heavy, the tools people use to cope, and the WCAG success criteria that apply. It also covers where WCAG stops short and what a review should check.

Common Accessibility Barriers on Websites

These barriers are easy to build in and easy to miss, because they rarely break a page for users who read quickly and remember easily.

Dense or Rigid Text Presentation

Long lines of text are hard to track, especially for users with dyslexia. Past roughly 80 characters, the eye loses its place on the way back to the next line. Justified text adds uneven gaps between words, tight line spacing makes lines blur together, and all caps or italics slow reading further because letter shapes lose their familiar outlines.

Backgrounds matter too. Text over photos or patterns forces the reader to separate letters from the image, and text baked into an image cannot be resized or restyled at all. Dyslexia friendly website design starts with real text, left-aligned, with generous spacing on a plain background.

Figurative and Ambiguous Language

Idioms such as “ballpark figure” or “touch base” depend on shared cultural knowledge, and a literal reader may take them at face value. Unexplained abbreviations and unusual words create the same problem: the user has to stop, decode, and hold the meaning in mind while reading on.

This is different from reading level. A sentence can use short words and still be unclear if it relies on a phrase the reader does not know. Spell out abbreviations on first use, define specialized terms where they appear, and use one name for each thing throughout the site.

Placeholder-Only Labels and Hidden Instructions

Some forms use placeholder text inside the field as the only label. The moment a user starts typing, the label disappears. Someone with a memory difference then has to remember what the field asked for, and anyone who steps away mid-form returns to a row of unlabeled boxes.

Hidden instructions cause the same problem. Format rules tucked into a tooltip or shown only on hover vanish when the pointer moves. Memory impairment website design works when the page holds the information, not the user. Keep a visible label above every field and show instructions next to the field, where they stay while the user types.

Lost Sense of Location

Users with memory differences can lose track of where they are in a multi-step process or a large site. A checkout with no step count, or a page with no breadcrumb or section title, leaves them guessing how far along they are and how to get back.

Show the current step and the total, such as “Step 2 of 4,” mark the active page in the menu, and use breadcrumbs on pages that sit several levels deep. Accessible navigation depends on cues like these, because each one answers the question “where am I?” so the user does not have to remember.

Urgency Timers and Auto-Changing Content

Countdown timers, auto-advancing carousels, and auto-refreshing feeds work against creating accessible content, because they set the pace for the user instead of letting the user set it. A banner that rotates every few seconds can disappear before a reader with a processing difference finishes the first line. A “sale ends in 10 minutes” timer adds pressure that makes it harder for anyone to weigh a decision.

ADHD friendly website design gives control back. Let users pause or stop moving content, keep important information on screen until the user dismisses it, and avoid timers that push people to decide before they are ready.

Unexpected Changes on Input

Some pages change the moment a user touches a control. Choosing an option from a dropdown submits the form or loads a new page. Focus jumps to another part of the screen. A link opens in a new window with no warning, which is a common link accessibility failure. For a user with attention or memory differences, each surprise breaks the thread of the task and forces a restart.

The rule is simple: the user should trigger every major change on purpose. Give forms a visible submit button, avoid moving focus automatically, and tell users before a link opens a new window.

Tools and Technologies People Use

People with dyslexia, ADHD, and memory differences often rely on tools built into their devices and browsers, not specialized equipment. A site works with these tools only if it provides real text, correct language attributes, and semantic structure, such as proper headings, lists, and form labels. Text locked in images, or markup that hides a page’s structure, defeats most of them.

Text-to-Speech and Read-Aloud Features

Read-aloud features speak page text while highlighting each word or sentence, which helps users who find decoding slow or tiring. Correct language attributes help them pronounce words properly, and headings and lists tell them where one section ends and the next begins.

Reading Rulers, Line Focus, and Reader Modes

Reading rulers and line-focus tools dim or highlight everything except the line being read, which helps users keep their place. Reader modes strip a page down to its main text, removing sidebars, popups, and ads. Both depend on clean structure, and a page built from unstructured containers can come out scrambled or incomplete.

Dictation, Spell Check, and Word Prediction

Dictation lets users speak instead of type, while spell check and word prediction reduce the effort of spelling. These tools work inside standard text fields, so a form that blocks pasting, swaps a field for a custom control, or clears input after an error works against them.

Browser Settings and Extensions for Text Spacing and Color

Many users change line spacing, letter spacing, font, and color through browser settings or extensions. Making fonts accessible includes making sure a site supports those changes, which means the layout holds up afterward: text stays visible, nothing overlaps, and buttons stay usable. Fixed-height containers and text in images are the usual causes of breakage.

Relevant WCAG Success Criteria

These are the WCAG requirements for cognitive disabilities that map most directly to the barriers above.

• 1.4.5 Images of Text (Level AA) requires real text instead of images of text, apart from logos and cases where an image is essential, so users can resize and restyle it.
• 1.4.12 Text Spacing (Level AA) requires content to stay readable when users set line height to 1.5 times the font size, paragraph spacing to 2 times, letter spacing to 0.12 times, and word spacing to 0.16 times.
• 3.2.2 On Input (Level A) requires that changing a form control does not trigger an unexpected change of context unless users are warned first.
• 3.3.2 Labels or Instructions (Level A) requires labels or instructions wherever users must enter information.
• 1.4.8 Visual Presentation (Level AAA) sets targets such as lines no longer than 80 characters, no justified text, line spacing of at least 1.5, and user control over colors.
• 3.1.3 Unusual Words (Level AAA) calls for a way to find the meaning of idioms, jargon, and other unusual words.
• 3.1.4 Abbreviations (Level AAA) calls for a way to find the expanded form or meaning of abbreviations.
• 2.4.8 Location (Level AAA) requires that users can find out where they are within a set of pages.

Where WCAG Falls Short for Cognitive Needs

WCAG is the legal baseline for digital accessibility, and cognitive needs are where that baseline is thinnest, because many of the criteria that matter most for reading, attention, and memory are optional Level AAA requirements that the laws covered in this series do not require.

Many Supportive Criteria Sit at Level AAA

Several of the criteria most useful for dyslexia, ADHD, and memory differences, including 1.4.8, 3.1.3, 3.1.4, and 2.4.8, are Level AAA. The laws covered in this series point to Level A and AA: ADA Title II requires WCAG 2.1 AA, the HHS Section 504 rule requires WCAG 2.1 Levels A and AA, and Section 508 names WCAG 2.0 Levels A and AA.

That makes the AAA criteria optional in practice. A site can meet every legal requirement and still make these users work harder than necessary.

Practices That Go Beyond Conformance

Level AA is the floor. Several practices help these users even where no criterion applies:

• Left-align body text and keep lines short.
• Define terms the first time they appear.
• Use the same word for the same thing across the site.
• Show step counts in multi-step flows.
• Keep instructions visible next to the field they describe.

None of these changes the look of a site much, and each lowers the effort of using it.

What a Cognitive Accessibility Review Looks At

A manual review tests how a page behaves for someone who reads slowly, loses focus, or forgets context. Automated scans cannot judge any of these, so a review checks:

• Read-aloud: listen to the page with a text-to-speech feature and note mispronounced words, wrong reading order, and skipped content.
• Text spacing: apply the 1.4.12 values and confirm that nothing is cut off or overlaps.
• Labels and instructions: confirm that every field has a visible label and that instructions stay on screen.
• Language and abbreviations: flag idioms, unexplained abbreviations, and inconsistent terms.
• Orientation cues and auto-updating content: look for step indicators and breadcrumbs, and for carousels, timers, and feeds that users cannot pause.

Get a free accessibility audit quote to find out where your pages stand.

FAQ

Which WCAG criteria help users with dyslexia?

The most relevant are 1.4.5 Images of Text and 1.4.12 Text Spacing at Level AA, which keep text real and adjustable, and 3.3.2 Labels or Instructions at Level A. At Level AAA, 1.4.8 Visual Presentation adds targets for line length, justification, and spacing.

Can automated scans detect barriers for users with dyslexia, ADHD, and memory differences?

Only a small portion. A scan can flag a missing label, but it cannot tell whether instructions stay visible, whether language is clear, whether text survives spacing changes, or whether moving content can be paused. Those barriers need manual review.

Which WCAG level should a site meet for cognitive accessibility?

Level AA is the floor, because the laws covered in this series point to Levels A and AA. Many of the criteria that help most sit at Level AAA, so meeting selected AAA criteria, such as 1.4.8 and 3.1.4, goes beyond the legal minimum.

Can placeholder text replace a form label?

No. A placeholder disappears when typing starts, often has low contrast, and is handled inconsistently by assistive technology. A visible label above the field is the dependable way to meet WCAG 3.3.2 and to keep users from having to remember what a field needed.