Dyslexia-Friendly Fonts: What the Evidence Actually Says (and the Typography Choices That Do Help)
Search for "dyslexia friendly fonts" and you will find dozens of lists recommending OpenDyslexic, Dyslexie, Lexend and friends. Some organisations have switched their whole website to one of them. It feels like an easy, visible accessibility win.
The research does not back it up. A 2026 meta-analysis of 15 studies found that specialist dyslexia fonts have no consistent or reliable effect on reading speed or accuracy. What does help is less glamorous: sensible type size, generous spacing, short lines, strong contrast, and - above all - letting readers change the text to suit themselves.
This guide covers what the evidence says, why the myth persists, and the typography specification that actually serves dyslexic readers and meets WCAG and the European Accessibility Act.
Dyslexia in one paragraph
Dyslexia is a specific learning difference that mainly affects word decoding, spelling and reading fluency. It is not a visual problem and it is not related to intelligence. Estimates of prevalence vary with the definition used, but figures of around one in ten people are commonly cited by organisations such as the British Dyslexia Association. That makes dyslexic readers one of the largest groups affected by how you set text - and one of the most frequently overlooked in accessibility programmes that focus on screen readers and keyboards.
The claim behind dyslexia fonts
Specialist fonts are designed on the idea that dyslexic readers confuse or "flip" letters, so each glyph should be made more distinctive. OpenDyslexic, for example, uses heavily weighted bottoms on letters so they appear anchored; Dyslexie uses enlarged openings and varied letter shapes to reduce confusion between characters like b, d, p and q.
The idea is intuitive. The problem is that dyslexia is primarily a phonological processing difference, not a problem of seeing letters, so changing letter shapes was always going to be a weak lever.
What the evidence says
The 2026 meta-analysis. A meta-analysis published in Annals of Dyslexia in 2026 pooled 15 empirical studies on dyslexia-friendly fonts and dyslexic children's reading. Its conclusion: these fonts show no consistent or reliable effect on reading speed or accuracy, and they do not offer substantial benefits over conventional fonts. The authors did note that certain typographic features may aid legibility - a point we come back to below. (Annals of Dyslexia, 2026; PubMed)
OpenDyslexic in children. A 2017 study tested OpenDyslexic against Arial and Times New Roman with young students with dyslexia. It did not improve reading rate or accuracy, and none of the students said they preferred it. (Wery and Diliberto, 2017)
Dyslexie in children. A larger 2018 study of Dyslexie found no benefit to reading speed or accuracy compared with Arial and Times New Roman. (Edutopia summary)
What does show an effect. Eye-tracking research by Luz Rello and Ricardo Baeza-Yates found that ordinary typographic properties mattered more than "dyslexia" branding: sans serif, monospaced and roman (upright) fonts improved reading performance for people with dyslexia, while italic text made it worse. (Good Fonts for Dyslexia)
The counter-evidence, fairly stated. Not every study is negative. One study of adults found that OpenDyslexic changed visual reading strategy and was associated with better comprehension on longer standardised texts (Franzen et al., Annals of Eye Science). Other researchers have reported that some readers find a specialist font more comfortable and less anxiety-inducing even when their measured performance does not change.
Put together, the honest reading is this: specialist fonts are not an evidence-based fix, but individual preference is real. That points to a design principle rather than a font choice - give people control.
Why the myth persists
- It is visible. Switching a font is a change everyone can see, which makes it attractive as a signal of commitment.
- It is cheap. It feels like accessibility for the price of a CSS line - the same appeal that sells overlay widgets.
- Preference is mistaken for performance. A reader saying "this feels easier" is valuable feedback, but it is not the same as reading faster or understanding more.
- The real work is less dramatic. Spacing, line length and plain language do not make headlines.
None of this means you should ban Lexend or OpenDyslexic. It means that picking one as your site font does not make your content accessible to dyslexic readers, and it can make it worse for others.
What actually helps: a practical typography specification
These settings are grounded in the research above and in WCAG. Treat them as defaults, not a straitjacket.
Font choice
- Use a clear, well-hinted sans serif with distinct letterforms. Check that capital I, lowercase l and the digit 1 are distinguishable, and that b/d and p/q are not simple mirror images.
- Avoid italics for anything longer than a few words. Use bold for emphasis instead.
- Avoid ALL CAPS for body text and long headings; word shapes disappear.
- Avoid condensed or very light weights for body copy.
Size and spacing
- Body text of at least 16px on the web, larger for long-form reading.
- Line height around 1.5 times the font size.
- Paragraph spacing clearly larger than line spacing.
- Do not tighten letter spacing for style. Default or slightly open tracking is safer.
Line length and alignment
- Aim for roughly 60 to 75 characters per line for body text. WCAG 1.4.8 (AAA) sets an upper limit of 80.
- Left-align text (in left-to-right languages). Avoid full justification: it creates uneven "rivers" of space that make tracking harder.
Colour and contrast
- Meet at least 4.5:1 contrast for body text (WCAG 1.4.3). See our colour contrast guide for the maths.
- Some dyslexic readers prefer an off-white or cream background to pure white. Offer it as an option or theme rather than forcing it on everyone.
Content and layout
- Short paragraphs, meaningful headings, and bulleted lists for sequences.
- Plain language. Typography cannot rescue a 45-word sentence. Our post on cognitive accessibility covers this in depth.
- Keep text as real text, not baked into images, so it can be resized, restyled and read aloud.
The part that is legally required: user control
Most of the above is good practice. The part that is a hard requirement under WCAG 2.1 AA - the level the EAA requires through EN 301 549 - is that your interface must survive users applying their own settings.
- 1.4.4 Resize Text (AA). Text must be resizable to 200% without loss of content or function.
- 1.4.10 Reflow (AA). Content must work at 320 CSS pixels wide without two-dimensional scrolling.
- 1.4.12 Text Spacing (AA). No loss of content or function 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.
- 1.4.8 Visual Presentation (AAA). Not mandatory for the EAA, but an excellent checklist: user-selectable colours, width no more than 80 characters, no justification, 1.5 line spacing, and resizing to 200% without horizontal scrolling.
This is where the fonts debate resolves itself. A reader who genuinely finds OpenDyslexic helpful can apply it with a browser extension, reader mode, or operating system setting. Your job is to make sure your layout does not break when they do: no fixed-height containers that clip text, no buttons whose labels overflow, no text set in images.
How to test it
- Apply a WCAG 1.4.12 text-spacing bookmarklet and walk through your key journeys - navigation, forms, checkout, error messages.
- Zoom to 200% and 400% in the browser.
- Override the font with a browser extension (OpenDyslexic is a good stress test because it is wide).
- Turn on reader mode and check that headings and structure survive.
- Ask dyslexic users. Preference data from real readers beats any font list.
A short checklist
- Body font is a clear sans serif with distinguishable I / l / 1
- Body text at least 16px; line height around 1.5
- Lines around 60-75 characters; left-aligned, not justified
- No italics or all caps for long text
- Contrast at least 4.5:1 for body text
- Layout passes 1.4.12 text spacing with no clipping or overlap
- Works at 200% zoom and 320px width
- No text in images
- Optional reading theme (background colour, font) offered as a choice, not imposed
- Tested with dyslexic users
The bottom line
Dyslexia-friendly fonts are a comforting idea that the evidence has not supported. The typography choices that do help are ordinary ones - size, spacing, line length, contrast, plain language - and the one that matters most is legally required already: build interfaces that bend when people set text the way they need it. Do that, and readers who prefer a specialist font can have it without you having to impose it on everyone else.
Related reading
WCAG 2.5.8 Target Size (Minimum): The 24px Rule, Its Five Exceptions, and the Dragging Fix Most Teams Skip
WCAG 2.2 added a 24 by 24 CSS pixel minimum for pointer targets and a single-pointer alternative for dragging. What 2.5.8 and 2.5.7 require, how the exceptions work, CSS patterns that pass, and how to apply the thresholds on iOS and Android.
Chatbot and AI Assistant Accessibility Under the EAA: Streaming Replies, Focus Management and the Widget Nobody Tested
Chat widgets and AI assistants sit inside checkout, banking and support flows the EAA covers, yet streaming responses, focus handling and launcher buttons routinely fail screen reader and keyboard users. What WCAG AA requires, how EU AI Act transparency duties interact, and a build-and-test checklist.
WCAG 1.4.10 Reflow: How to Pass the 400% Zoom Test Without Breaking Your Layout
WCAG 1.4.10 Reflow asks one thing: at 320 CSS pixels wide (400% zoom on a 1280px screen), can people read and use your page without scrolling in two directions? What the criterion actually requires, the exceptions teams misread, the layout patterns that fail, the CSS that fixes them, and a test method you can run in five minutes.