You spend three months building a website. The content is solid, the layout is clean, and someone on the team suggests making the body text fully justified because it “looks more professional.” Everyone agrees. It ships. Six weeks later, your accessibility audit comes back flagged — and the consultant’s notes specifically call out your text alignment. You argue with her. It’s text alignment. How is that an accessibility issue?
I’m Rohan Ratnayake, and I’ve spent the last five years working as a web accessibility consultant specializing in cognitive and reading disabilities. I’ve sat in more post-audit meetings than I can count where the justified text flag gets challenged, dismissed, or just quietly ignored because nobody on the team understands the why behind it. That’s the problem I want to fix here. Not with a list of rules, but with the actual mechanics of what happens inside a reader’s brain — specifically a dyslexic reader’s brain — when they hit a block of fully justified text. Once you see it, you can’t unsee it.
The hard lesson I learned early came from a healthcare nonprofit whose patient portal I helped audit. Their entire knowledge base — hundreds of articles about medications, procedures, side effects — was set in full justification. Their patient satisfaction scores were mediocre, and drop-off on long articles was around 71%. We changed the text alignment to left-aligned as part of a broader fix, and re-ran user testing with participants who had disclosed dyslexia. Reading comprehension scores on those same articles went up measurably. Nobody had touched the words. Just the spacing.
The “Rivers of White Space” Problem Isn’t a Visual Quirk — It’s a Navigation Trap
Full justification works by stretching or compressing the spaces between words so that every line of text ends flush with the right margin. Typographers have known since the printing press era that this creates uneven word spacing. On a printed page, it’s manageable because the physical resolution is high and the human eye is forgiving at close range. On a screen, it gets worse. Variable pixel rendering, different font rendering engines across browsers, and responsive layouts that constantly reflow text at different viewport widths — all of it amplifies the spacing inconsistency.
The result is what typographers call “rivers” — vertical channels of white space that thread down through a paragraph because multiple consecutive lines happen to have large word gaps that accidentally line up. Your eye, which is constantly scanning for visual patterns, sees those rivers as structural signals. It thinks they mean something. For most readers, this is a mild distraction that the brain quickly suppresses. For dyslexic readers, it’s not mild and it doesn’t get suppressed.
Here’s the specific reason: dyslexia is not a problem with intelligence or with seeing letters backwards — that’s a myth that persists despite decades of research. Dyslexia is primarily a phonological processing issue, but it often comes paired with visual tracking difficulties. The brain has a harder time keeping its place on a line and moving correctly to the next one. Consistent, predictable spacing between words is a stabilizing cue. When that spacing is uneven — when some gaps are noticeably wider than others — the visual tracking system has to recalibrate constantly. That recalibration has a cognitive cost. It’s small per instance, but across a 600-word article, it accumulates into genuine fatigue and comprehension loss.
Why This Registers as “Cognitive Load” and Not Just “Difficulty Reading”
Cognitive load theory, originally developed by educational psychologist John Sweller, describes the total amount of mental effort a working memory system is using at any given moment. There are three types:
| Load Type | What It Means | Example in Reading |
|---|---|---|
| Intrinsic | Complexity of the content itself | Understanding a medical diagnosis |
| Germane | Mental effort building understanding | Making connections between paragraphs |
| Extraneous | Effort caused by how content is presented | Tracking words through uneven spacing |
Extraneous load is the one designers control. It doesn’t help the reader learn anything — it’s pure overhead. For a neurotypical reader with strong tracking skills, the extraneous load from justified text is low enough to be nearly zero. For a reader with dyslexia, that same formatting can push total cognitive load past the threshold where comprehension starts to degrade. They’re not failing to understand your content because your content is bad. They’re failing because part of their working memory is occupied with the mechanical act of following the text.
This is the part that gets missed in most accessibility conversations. People treat WCAG guidelines as a checklist of disabilities to accommodate rather than as a framework for understanding how cognitive effort scales differently across users. The Web Content Accessibility Guidelines (WCAG) don’t explicitly ban justified text, but Success Criterion 1.4.12 on text spacing and the general principle of reducing “cognitive friction” give auditors solid grounds to flag it — and most serious auditors do.
The Specific Numbers Nobody Talks About
Here’s what makes the rivers-of-white-space problem concrete rather than theoretical. In a standard paragraph set at a common body text width — roughly 600 to 700 pixels, which covers most desktop reading columns — a fully justified paragraph at a 16px font size can produce word spacing that varies between 4px and 22px within the same line, depending on the words present. That’s a 5x variance in the visual gap your eye is using as a separator.
Left-aligned text doesn’t do this. Word spacing stays locked to whatever the font’s default is — typically a consistent 4px to 6px range. The right edge of the text becomes ragged, yes, but that raggedness is irrelevant to reading. Nobody’s eye starts from the right side and works backward. The left edge and the consistent word spacing are the rails that guide reading, and left-alignment keeps those rails steady.
For dyslexic readers specifically:
- Uneven word spacing increases the likelihood of losing place mid-line
- Large gaps between words can cause the eye to skip words entirely, not read them slowly
- Rivers create false vertical structure that the eye interprets as a column break or list separator
- The brain spends time suppressing visual noise that provides zero informational value
A 2016 study published by the British Dyslexia Association found that typeface and spacing choices had significant effects on reading speed and accuracy for dyslexic readers — and spacing consistency was specifically noted as a factor. You can read their full style guide for dyslexia-friendly formatting directly — it’s one of the clearest practitioner-level documents on this topic that exists.
Why Designers Keep Getting This Wrong
The “professional look” argument for justified text usually comes from print design experience or from seeing justified text in books and newspapers. There’s a reason it works in those contexts that doesn’t transfer to web.
| Medium | Why Justification Works (or Doesn’t) |
|---|---|
| Print books | Fixed column widths, high-res output, professional hyphenation algorithms |
| Newspapers | Narrow columns where variance is minimal, designed for fast scanning not deep reading |
| Web (desktop) | Variable viewport widths cause constant reflow and unpredictable gap variance |
| Web (mobile) | Narrow columns at small font sizes make gap variance extreme and rivers very pronounced |
Books use sophisticated hyphenation to break words across lines, which dramatically reduces the gap variance that causes rivers. Most web implementations of justified text don’t enable CSS hyphenation, or enable it inconsistently across browsers. The result is text that’s trying to look like a book but is operating without the tools that make book justification work.
The other piece: print books are designed to be read by people who chose to read them and are sitting still in good lighting. A web article gets read on a phone on a bus, by someone who found it through a search at 11pm, often not by choice in the same way. The reading conditions are worse and the audience is broader. Your formatting needs to be more robust, not less.
What Your Accessibility Audit Is Actually Telling You
When a tool like Axe or WAVE flags justified text — or when a human auditor calls it out — the note isn’t about aesthetics. It’s about the extraneous cognitive load your formatting is adding to users who already have less working memory bandwidth available for the mechanical act of tracking text. The audit is telling you that you’ve made a formatting choice that prioritizes visual symmetry over reading function.
The fix is not complicated, but that’s not what this article is about. The point is understanding why it’s wrong so you stop having the argument every time a designer pushes back. Justified text on the web:
- Introduces unpredictable word spacing that no CSS value can fully control without hyphenation support
- Creates river patterns that function as false visual structure for readers with tracking difficulties
- Adds extraneous cognitive load on top of intrinsic content complexity
- Scales worse on smaller viewports where column widths compress and gap variance increases
- Gets flagged by accessibility auditors not as a stylistic preference but as a documented barrier for cognitively diverse users
Three Questions I Get Asked Every Time
Does this only affect people with diagnosed dyslexia?
No. Dyslexic readers are the most affected, but anyone reading in a second language, anyone reading under fatigue or distraction, and anyone with certain attention-related differences will experience elevated extraneous load from uneven spacing. Dyslexia is the clearest case, not the only case.
What about CSS text-align: justify with hyphens: auto?
Hyphenation does reduce river formation, but browser support for hyphens: auto is inconsistent across languages and rendering engines. It also requires the correct lang attribute on your HTML to function properly. Most implementations in production are missing one of those dependencies, which means you’re getting justification without effective hyphenation — the worst of both configurations.
My CMS forces justified text and I can’t change it. What do I tell stakeholders?
Document it as a known accessibility risk, cite WCAG 1.4.12 and cognitive load research, and include it in your audit findings. A platform limitation doesn’t remove the liability; it just changes who owns it. Stakeholders who understand that justified text increases bounce rate on long-form content tend to find the motivation to address platform constraints faster.
The Actual Problem Here
Most of the web is still treating text alignment as a visual preference when it’s a functional decision that affects how many of your readers can actually process what you wrote. Dyslexic users make up roughly 10% of the population — and they’re not a niche audience you can ignore because your content is too sophisticated for accessible formatting. Cognitive load doesn’t care how smart your readers are. It responds to the quality of your presentation.
Go back to any long-form piece on your site that’s currently justified. Paste it into a plain text preview with left alignment and read it again. You probably won’t notice a difference — because your visual tracking is working fine. Then consider that 10% of your readers are doing that same reading task with a system that’s already working harder just to stay on the line. The question isn’t whether justified text looks good. It’s whether the way it looks is worth what it costs the people reading it.
