Blog · Typography
Numbers and dyslexia - fonts that make digits clearer
Almost everything written about dyslexia-friendly reading is about letters - the shapes of b and d, the rhythm of a paragraph, the typeface you set for body text. Numbers get left out, which is strange, because digits are where a misread does the most damage. Get a letter wrong and context usually rescues you; the sentence still makes sense. Get a digit wrong and you dial the wrong number, pay the wrong amount, or copy a verification code that simply fails. For a lot of dyslexic readers, numbers are a separate and quieter struggle - and the typeface doing the work matters more here than almost anywhere else.
The short answer
Numbers are not just small letters - the errors are different. Two things go wrong: confusing similar-looking digits (a 0 for an O, a 1 for a lowercase l) and transposing the order of a sequence (typing 96 when it should be 69). A typeface built to keep digits distinct fixes the first; figures that line up in neat columns help with the second.
The safe picks are Atkinson Hyperlegible and Lexend for everyday reading, and a tabular monospace like JetBrains Mono for codes, tables and reference numbers. You do not need a separate diagnosis to benefit - clearer digits help anyone who has to read a number correctly the first time.
Why numbers are their own problem
First, the myth, because it gets in the way of every honest conversation about this. Dyslexic readers do not see numbers - or letters - flipped or mirrored on the page. When someone reads 69 as 96, their eyes are not reversing the image. The slip happens further along, in how the brain sequences and holds a string of symbols that carry no meaning of their own. The "reading backwards" picture is vivid and wrong, and believing it sends you looking for the wrong fixes.
What is real is that transpositions and digit reversals - 13 read as 31, 17 typed as 71 - show up more often for some dyslexic readers. They are best understood as a byproduct of the underlying processing differences rather than a defining sign of dyslexia. They also overlap with two neighbours: dyscalculia, a distinct difficulty with number sense and arithmetic, and plain working-memory load, which trips up plenty of people who have neither. The point is not to self-diagnose from a misread phone number, but to recognise that digits lean on exactly the systems dyslexia tends to tax.
There are two reasons a number is harder than a word of the same length. The first is that there is no safety net: language is redundant, so a half-recognised word is usually pinned down by the words around it, but the difference between account 4071 and account 4017 is invisible to context - both are equally plausible. The second is working memory. Holding a six-digit code or an IBAN in your head while you type it is precisely the kind of long, meaningless, sequential string that working memory handles badly, and dyslexia often comes with less room in that buffer. We unpack that load in detail in dyslexia and working memory, and it is the hidden reason long numbers feel so much heavier than they look.
The two failure points a font can fix
Break the problem into its two moments and it becomes clear what a typeface can and cannot do. The first moment is recognising a single digit: is that a 0 or an O, a 1 or an l, a 5 or an S? The second is holding and ordering the string: did the 4 come before the 7? A good font helps with both. Crisp, distinct glyphs reduce the first kind of error directly. Figures that sit in even, predictable columns give your eye stable landmarks for the second, so you are less likely to lose your place midway through a number. Neither is a cure, but both shave off real friction, and with numbers a small reduction in error rate is worth a lot.
The homoglyph problem
A homoglyph is a character that looks almost identical to another but means something different. Numbers are full of them: 0 against capital O, 1 against lowercase l and capital I, 5 against S, 6 against G, 2 against Z, 8 against B, and a 9 that can drift toward a lowercase g. In running prose these collisions rarely matter. In a password, a serial number or a one-time code, where letters and digits sit side by side and nothing is predictable, they matter constantly.
This is the exact problem Atkinson Hyperlegible was built to solve. The Braille Institute team went through the whole character set hunting down confusable pairs and forcing them apart: a slashed zero so it cannot be an O, an exaggerated 8 so it cannot be a B, a 1 that will not be mistaken for an l or an I. It was designed for low vision, but the same disambiguation is exactly what helps when a dyslexic reader has to be sure of a digit. Here are the worst offenders shown in a font that keeps them distinct, next to a smoother geometric face where they blur together:
0O o0 1 l I 5 S 6 G 8 B 2 ZAtkinson Hyperlegible - built to keep these pairs apart
0O o0 1 l I 5 S 6 G 8 B 2 ZGeometric sans - the same pairs start to merge
If your device does not have both faces installed the contrast will be softer, but on most screens the difference is plain: the disambiguated font lets you name each character without a second look, while the geometric one makes you pause on the zero and the one.
Lining, old-style and tabular figures
Two more distinctions are worth knowing, because they change how a number behaves even within a single font. The first is lining versus old-style figures. Lining figures all sit at the same height, like capital letters, so a row of them reads as a steady band. Old-style figures have ascenders and descenders - the 3, 4, 7 and 9 dip below the baseline - which looks elegant in flowing text but adds a bobbing motion that is extra work when you are trying to verify a number. For dyslexic readers, lining figures are the safer default.
The second is proportional versus tabular figures. Proportional figures each take their natural width, so a 1 is narrow and an 8 is wide. Tabular figures all take the same width, so they stack into tidy columns. When you are comparing prices, scanning a spreadsheet or checking a total, tabular figures hand your eye a grid to track along - the ones column sits under the ones column, the decimal points align - and that structure is exactly what a tired sequencing system needs.
In the tabular column the decimal points line up into a single vertical edge; in the proportional column the narrow 1s pull the digits out of alignment. This is why monospaced fonts feel so reassuring for codes and data - every digit is the same width by definition, so the grid is automatic. If you spend time in editors or terminals, the same logic carries over to reading code with dyslexia, where fonts like JetBrains Mono and IBM Plex Mono pair tabular digits with a slashed zero.
Fonts that get digits right
You do not need to memorise figure styles. A handful of typefaces have already done the work, and the right one depends on where the numbers live.
| Font | What it does with digits | Best for |
|---|---|---|
| Atkinson Hyperlegible | Slashed zero, distinct 1, 6 and 8, homoglyphs forced apart. | Codes, forms, anything where one wrong digit hurts. |
| Lexend | Open, even, generous figures with a large x-height. | General reading with numbers running through the text. |
| JetBrains Mono / IBM Plex Mono | Tabular by default, slashed zero, fixed width. | Spreadsheets, code, IBANs, reference numbers. |
| Verdana | Sturdy, wide, clearly lining digits. | A reliable fallback that is installed almost everywhere. |
| Georgia / elegant serifs | Old-style figures that dip below the baseline. | Looks lovely in prose; avoid when accuracy matters. |
If you are weighing the first two against each other for everyday reading, the trade-offs are the same ones we cover in Lexend vs Atkinson Hyperlegible - one optimises reading rhythm, the other raw character distinction - and both sit comfortably on the shortlist in our research-first guide to the best fonts for dyslexia.
Where numbers actually bite
It helps to know the moments worth defending, because they are not evenly spread. One-time codes are the highest-stakes thirty seconds in most people's day: a string of digits with a timer attached and no context to lean on. Where you can, paste rather than retype; where you must read, a clear font is the whole battle. Prices and totals reward tabular figures - lined-up decimals make a column of numbers comparable at a glance instead of one at a time. Phone numbers, card numbers and IBANs are easier when they arrive already chunked into groups of three or four, so keep them grouped and read them aloud as you go. Spreadsheets are worth setting up properly once: a tabular monospace turns a wall of figures into a grid, an approach that fits naturally with a dyslexia-friendly Google Docs and Sheets setup.
How to apply all this everywhere
The catch is the same one that undermines every font recommendation: most websites pick their own typeface and never ask. Your banking dashboard, the checkout page, the developer tool showing your API keys - they all ship whatever digits they like, slashed zero or not. You can choose a beautiful disambiguated font and still be stuck reading important numbers in something ambiguous, because the site chose for you.
LexiFont closes that gap. It is a Chrome extension that overrides the font on any page in one click, so you can read every site's numbers in Atkinson Hyperlegible or Lexend instead of whatever shipped - the same move we describe in how to change the font on any website in Chrome. It is the most direct way to act on everything above: pick a font whose digits you trust, and apply it to the pages where a wrong number actually costs you.
Get LexiFont Pro - Atkinson Hyperlegible, Lexend, OpenDyslexic and Comic Neue for $14.99 one-time
A two-minute test
Open a page that is mostly numbers - a bank statement, an order history, a spreadsheet. Read a column in the site's default font and notice how often you double-check a figure. Then swap to Atkinson Hyperlegible or a tabular monospace and read the next column. You are not timing yourself; you are counting the re-checks. If the second version makes you glance back less, that is the font quietly removing a source of error you had stopped noticing - and with numbers, fewer errors is the only score that counts.