Most blog readability problems come down to a handful of settings: text size, line length, line spacing, contrast, tap targets, and how much is competing with the article for space. Set those sensibly and almost any theme becomes comfortable to read.
The short version: body text at 16px or larger, lines of roughly 45β75 characters, a line height of 1.5, text contrast of at least 4.5:1, and nothing covering the article when someone arrives. The table gives the values. The sections after it explain where each number comes from, because some are published standards and some are only convention, and it helps to know which is which.
The settings, the values, and the reasons
| Setting | Recommended value | Why |
|---|---|---|
| Body text size | 16px minimum; 17β18px is common | Readable on a phone without zooming |
| Line length | About 45β75 characters, never over 80 | The eye finds the next line easily |
| Line height | 1.5 Γ font size | Lines stop blurring into each other |
| Text contrast | 4.5:1 or higher (3:1 for large text) | Readable with low vision or in sunlight |
| Tap targets | 24Γ24px at the very least; 44β48px is better | Fewer mis-taps |
| Images and ad slots | Space reserved before they load | The page doesn't jump while you read |
| Pop-ups | No full-screen overlay on arrival | Readers and Google can reach the content |
| Mobile ads | Well under 30% of the article's height | Past that, ads crowd out the article |
Text size, line length and line height
Text size. There's no official minimum. WCAG, the web accessibility standard published by the W3C, doesn't set one. The 16px figure is convention: it's the default size in every major browser, and it's the floor most designers work from. Plenty of blogs use 17 or 18px for body text, and I'd pick 18px for anything long. If your theme sets body text at 14px, that's the first thing to change.
Line length. This one does have a published number. WCAG's Visual Presentation criterion (1.4.8) says a line should be no more than 80 characters wide. It's a Level AAA criterion, the strictest of WCAG's three tiers, so treat it as a sensible ceiling more than a requirement. Typographers go further and commonly recommend about 45β75 characters. That range is long-standing convention, and no standard sets it.
On a phone the screen does this for you. The problem shows up on laptops and tablets, where a theme lets text run the full width of the window. The fix is a maximum width on the article column: around 65ch in CSS, or somewhere near 600β700px at an 18px font size depending on the typeface.
The same criterion says text shouldn't be justified, so leave body text left-aligned.
Line height. WCAG 1.4.8 asks for line spacing of at least "space-and-a-half", meaning 1.5. A second criterion, Text Spacing (1.4.12, Level AA), uses the same 1.5 figure in a different way: your page must not break when a reader overrides the spacing to that value. So 1.5 is both a good default and the value your layout has to survive. Anything from 1.5 to about 1.7 reads well for body text. Headings can be tighter.
Contrast: the one with a hard number
WCAG's Contrast (Minimum) criterion, which is Level AA, requires a contrast ratio of at least 4.5:1 between text and its background. Large text, defined as 18pt (about 24px) or 14pt bold (about 18.5px), only needs 3:1. The full wording is in the WCAG 2.2 specification on w3.org.
Black on white passes with a huge margin. The usual failures are elsewhere: light grey body text, pale link colours, grey dates and author lines, and white text on a brand-coloured button. Put each text and background pair into a free contrast checker (WebAIM has a well-known one) and fix whatever comes in under 4.5:1.
If your site has a dark mode, check those colours too. The ratio applies to every colour scheme you ship.
Tap targets on a phone
WCAG 2.2 added Target Size (Minimum), which asks for targets of at least 24 by 24 CSS pixels. That's a floor. Google's web.dev guidance recommends about 48px with roughly 8px between targets, and Apple tells app designers to make controls at least 44 by 44 points.
Links inside a sentence are exempt from the WCAG rule, so you don't need to restyle your paragraphs. Look at menu items, the search icon, share buttons, pagination, footer links stacked close together, and the close button on any banner, which is often the smallest target on the page.
Headings and paragraphs
Many readers scan the headings before deciding whether to read. A heading should say what its section covers. "Contrast: the one with a hard number" tells you something. "Things to consider" doesn't.
Keep the levels in order: the title, then H2 for sections, then H3 inside them. People using screen readers often jump from heading to heading, and skipped levels make that harder.
Short paragraphs help on a phone, where four sentences can fill the screen. Two to four sentences is a reasonable habit. Don't chop everything into single lines, though, because an explanation that needs five sentences reads worse as five fragments. The article structure I'd use for drafting covers this from the writing side.