Blog · How-to
Dyslexia-friendly Google Docs setup
For most adults who write for a living, Google Docs is the single longest piece of text they look at all week. It is also a surface tuned for the average reader - 11 point Arial on a hard-white page, single line height, default tracking - and the average reader is not dyslexic. The good news is that Docs lets you change almost every variable that matters; the better news is that you can save the result as a default and never set it up again. Here is the practical setup, in the order to apply it.
What makes Google Docs hard to read
Three default choices stack against a dyslexic reader. The page is pure white, which produces low-grade glare on most LCD panels and pushes the eye to over-correct. The body font is 11 point Arial, set at single line spacing - that is dense by any standard, and well below the size and leading values that show up in legibility research as helpful for adults with dyslexia. And the page is sized to look like A4 on screen, which means a long line on a wide laptop with the document zoomed to 100%, often well above the 60-75 character per line range the eye tracks comfortably.
None of these are bugs. They are the right defaults for someone who needs the document to print like a Word doc from 2008. They are the wrong defaults for reading. The trick is to swap them, save the result, and let every new document inherit it.
Step 1: change the body font
Open any document. Place the cursor in a paragraph of body text and click the font name in the toolbar - by default it shows Arial. At the bottom of the dropdown, click More fonts. This is the moment where the choice of font does most of the heavy lifting.
Google Fonts ships several typefaces that are useful here, and Docs makes them all one click away. The shortlist for dyslexic readers:
Lexend
Built around reading-speed research. The wider letter spacing and tall x-height make it visibly faster to read in long passages, which is where Docs spends most of its time. Of all the Google Fonts available in Docs, Lexend is the one that ports the most cleanly into a writing surface - it does not feel "novelty," and reviewers will not flag it. We covered the research it is built on in our Lexend in Chrome piece.
Atkinson Hyperlegible
The Braille Institute font designed to disambiguate look-alike characters - 0/O, l/1/I, a/o. If your dyslexia is the letter-confusion kind rather than the tracking kind, Atkinson Hyperlegible is the better starting point. It is also the most versatile font on this list for documents that mix prose, code blocks, dates, and references, because it never lets a glyph blur into the one beside it. Background and trade-offs are in Lexend vs Atkinson Hyperlegible.
Comic Neue
The grown-up cousin of Comic Sans. The reason Comic Sans is the dyslexia community's perennial favourite is that its letterforms are irregular enough to never look like each other - and Comic Neue keeps that property without the visual baggage. If you are writing notes and drafts that nobody else will see, this is often the calmest reading surface on the list. We unpack the trade-off in Comic Sans and dyslexia.
OpenDyslexic is not in the Google Fonts library that Docs surfaces, so it cannot be set as the document font from inside Docs itself. There is a workaround using the Chrome layer further down this article, and it is worth knowing about - but for the in-document choice, pick one of the three above.
Step 2: lift the size and the line spacing
Once the font is right, two other dials do most of the remaining work. Both live in the toolbar.
Bump the body text from 11 point to 13 or 14 point. The rule of thumb from our font-size guide is that the eye is most comfortable when an average lowercase letter sits at roughly 4-5 mm tall on screen, which on most laptops puts you at 13-14 point in Docs at 100% zoom. Going higher does not necessarily help; it shortens the line, which can backfire by introducing more line breaks per paragraph.
Then change line spacing. Click Format > Line & paragraph spacing, or use the line-spacing icon in the toolbar. Move from "Single" to 1.5. This is the single biggest readability lever in Docs and the one most readers leave on the default. The peer-reviewed effect of generous leading on dyslexic reading speed is genuinely large - we go through the numbers in line spacing and letter spacing for dyslexia. Inside Docs, 1.5 hits the sweet spot for most adults; some readers prefer "Custom spacing" set to 1.4 if 1.5 starts to feel airy.
While you are in that menu, set Add space after paragraph to 8 or 12 points. It separates paragraphs visually so your eye does not have to count line breaks.
Step 3: change the page colour
Pure white pages are not kind to dyslexic eyes, especially under fluorescent or cool LED light. Google Docs lets you change page colour and saves it inside the document.
Go to File > Page setup. In the dialog, click the Page colour swatch and pick Custom. Three values are worth trying first:
A warm cream around #FAF3E3 takes the glare off without making the text look dim. A pale grey around #EEECEA is the middle path - barely off-white, but enough to soften the contrast. A very pale blue around #EEF3F8 is the option some readers report as the calmest, particularly readers who also struggle with visual stress. We work through the evidence in background colours for dyslexia; the short version is that the right value depends on your eyes and your lighting, and the only way to find it is to try.
Print preview note. A custom page colour shows up in the on-screen view but, in most cases, will not actually print on paper unless you turn on background printing in the print dialog. That is usually what you want - cream backgrounds save eye strain on screen but waste ink at the printer.
Step 4: save it as the default
This is the step most guides skip and the one that actually compounds. Once your document looks right - font, size, line spacing, paragraph spacing, page colour - turn the changes into the new default for every document you create.
Place the cursor in a body paragraph that is set the way you want it. Open Format > Paragraph styles > Normal text > Update "Normal text" to match. Then go back to the same submenu and click Options > Save as my default styles. From now on, every new Doc you open inherits your dyslexia-friendly setup.
This is also the step where it pays to update the heading styles, not just body. While you are in Paragraph styles, set Heading 1, Heading 2, and Heading 3 to use the same font as your body, just at larger sizes and (optionally) bolder weight. Mixing two fonts in a document is the kind of small visual switching cost that adds up. Your headings should look distinct from body text but they should not require your eye to recalibrate.
Step 5: turn on the Chrome layer for everything else
Steps 1 to 4 fix the document body. They do not fix the comments sidebar, the suggesting-mode banners, the toolbars, or the document title bar - all of which still render in Google's UI font (currently Roboto/Arial) at small sizes. They also do not let you use OpenDyslexic, which is not in the Google Fonts library Docs surfaces.
That is where a Chrome-side font override comes in. The principle is the same one we cover in how to change the font on any website in Chrome: you tell the browser to ignore the page's font declarations and substitute one of your own. For Google Docs specifically, the trick is to scope the override carefully - you usually want the override to apply to docs.google.com for the chrome and toolbars, but you may want to leave the in-document text alone if you have already set it to Lexend or Atkinson via Step 1. Most font-override extensions, including LexiFont, let you exclude the iframe that contains the editing surface so the two layers do not fight each other.
If you want OpenDyslexic on the body text, the trick is the inverse: leave the Doc's font set to Arial inside Docs, and use the Chrome override to substitute OpenDyslexic everywhere on docs.google.com. The trade-off is that any reviewer opening the same document will see Arial - your override is local to your machine.
A demo: same paragraph, three setups
The text is identical. What changes is how much effort the eye spends to get through it. For one paragraph the difference looks small. Across a 4,000-word document, it compounds.
What about Dark mode?
Google Docs supports a dark theme: View > Appearance > Dark (or "Use device theme" to inherit your OS setting). For some dyslexic readers, dark mode in Docs is a clear win - the surrounding chrome stops glowing, and the page itself becomes a softer dark grey rather than the inverse-video harshness of pure black. For others, particularly readers with co-occurring visual stress, dark mode actually makes letters feel like they are floating; the eye loses its anchor.
The right call depends on your eyes and your room lighting. We dig into the trade-offs in dyslexia-friendly dark mode. As a rough rule: try dark mode in Docs for a full afternoon's writing session before deciding. If your eyes feel less tired at the end, keep it. If the screen feels harder to track, go back to a cream or pale-grey page.
Suggesting mode and the comments sidebar
The two parts of Docs that defeat most accessibility setups are Suggesting mode (the orange/green underlined edits) and the comments sidebar. Suggesting mode is unavoidable if you collaborate, but two settings make it survivable. From View, turn off Show suggested edits inline when you are reading, then turn it back on when you are reviewing. And from the three-dot menu on any suggestion, you can resolve in batch rather than one-by-one - which is essential when a long doc comes back with 50 tracked changes.
For the comments sidebar, the big lever is the panel width. Drag the sidebar narrower if it is competing with your line length on the document side. The narrower the comments column, the wider your reading column - and a wider reading column at the right line height beats a wider sidebar most of the time.
Mobile Google Docs
The iOS and Android Docs apps respect your saved default styles, including the font (if it is a Google Font that ships in the app) and the line spacing. They do not respect a custom page colour, and they do not let you load Chrome extensions. On mobile, the decisive lever is the system-wide text size: turn on Dynamic Type at "Larger" or "Largest" and the Docs app respects it for body text. The trade-offs there are the same ones we cover in best font size for dyslexic adults.
A 10-minute setup checklist
If you want the whole thing in one pass, do this in order, in a fresh blank document:
Pick your font from More fonts - Lexend, Atkinson Hyperlegible, or Comic Neue. Set body to 13 point. Set line spacing to 1.5 from the toolbar. Add 8 or 12 points after paragraph from Format > Line & paragraph spacing. Open File > Page setup and set page colour to a custom warm cream, pale blue, or soft grey. Update Normal text to match the cursor's paragraph, then save as your default. Last, install or open LexiFont and scope it to docs.google.com for the toolbars and chrome. Read a real document. Tweak one variable at a time until it feels right.
Most readers land on a setup within 10-15 minutes and leave it there for years.
The bigger picture
Google Docs is the second test case after Gmail; the same logic extends to every long-form web app you spend hours in - your CMS, your knowledge base, your project tracker. The reason a dyslexia-friendly extension matters more than per-app settings is that you only configure it once. Docs gets its own setup; so does Gmail; everything else gets the override. The cumulative effect across a writing day is the part that adds up - and it is the kind of thing we built LexiFont Pro to handle in one place, with all four dyslexia-friendly fonts available and per-site rules so each app gets the treatment it needs.