Text reads well on a phone when it fits the screen width and starts at a comfortable size. It also helps when paragraphs are short and buttons are big enough for a thumb. Readers should never have to drag the page sideways to finish a line, and pinch zoom should always work.

Small screens expose every weak habit in a page. This page lists the settings that matter, gives rules of thumb where no standard exists, and ends with a test you can run on a real phone.

Start with the viewport and pinch zoom

Many layout problems begin before a single word is styled. MDN explains that some mobile browsers draw a page in a virtual window that is wider than the screen, then shrink the result to fit. Users then have to zoom and pan to read. This is one way a page ends up with tiny text.

The viewport setting tells the browser to use the real screen width. MDN says width=device-width sets the viewport to the screen's width in CSS pixels. With that in place, the page can adapt to a narrow screen instead of being shrunk.

MDN warns against setting user-scalable to no. It says this prevents readers from zooming to read and understand the page. It adds that WCAG requires at least 2 times scaling, and that the best practice is to allow 5 times. MDN also says some browsers ignore the setting, and iOS 10 and later ignores it by default. So blocking zoom hurts readers on some devices and does nothing on others.

The settings at a glance

SettingWorking ruleWhere it comes from
Body text sizeStart at 16 CSS pixels or largerRule of thumb
ParagraphsTwo to four sentencesRule of thumb
Page widthNo sideways scrolling at 320 CSS pixelsWCAG 1.4.10 Reflow
Tap targetsAt least 24 by 24 CSS pixels, with 44 by 44 as the stricter aimWCAG 2.5.8 and 2.5.5
Pinch zoomLeave it onMDN

The first two rows are habits, not standards. Nothing official says exactly how big a phone paragraph may be. These numbers are a sensible place to begin, so adjust them after testing.

Size and paragraphs

Do not shrink body text to fit more on the screen. Start at 16 CSS pixels or larger and give the lines some room. The font size guide and the line spacing guide go deeper.

Keep paragraphs short. A phone line holds only a handful of words, so a four-sentence paragraph can fill most of the screen. Lead each paragraph with its point. If a paragraph needs a list, make it a list.

Short sentences matter more here than on a large screen. See writing shorter sentences.

Line length and sideways scrolling

On a phone, the column is naturally narrow, so the old worry about lines that are too long mostly disappears. The column width guide covers desktops, where the problem is real. On a phone, the danger is the opposite: padding that squeezes the text into a thin strip.

WCAG's Reflow criterion asks that content works without scrolling in two directions at a width of 320 CSS pixels. Its intent is simple. When a line runs past the edge, readers must scroll back and forth, and WCAG says this can make them lose their place. A single column is a common way to meet it.

Some content is exempt. WCAG lists maps, diagrams, video, games, presentations and data tables as needing a two-dimensional layout. If a table is wide, let the table scroll inside its own box, so the rest of the page stays still.

Long web addresses are a classic cause of a page that drifts sideways. Use short, descriptive link text instead. See link text that makes sense on its own.

Tap targets

WCAG 2.5.8 asks that a pointer target is at least 24 by 24 CSS pixels, with exceptions. One exception is spacing: small targets pass if a 24 pixel circle centered on each does not overlap another target or another small target's circle. Links inside a sentence are exempt, because line height limits their size.

WCAG explains the purpose. The rule helps people activate a target without hitting its neighbor. It adds that authors who can should aim for the stricter 2.5.5, which asks for 44 by 44 CSS pixels. That page notes that touch is a coarse input, since a finger is larger than a mouse pointer and hides what it is about to press.

In practice, give buttons and menu items real padding. Put space between a list of links so thumbs do not collide.

Test it on a real phone

An emulator on a desktop is a start. A real phone shows more.

  • Open the page in portrait mode at the default settings.
  • Read the first screen without pinching. Is the text comfortable?
  • Scroll the whole page. Does anything push it sideways?
  • Tap every button and link with your thumb. Do you hit the wrong one?
  • Turn the phone on its side. Does the text still wrap?
  • Pinch to zoom in. Does it work?
  • Hand the phone to someone else and watch where they hesitate.

Desktop zoom works differently, and the browser zoom guide covers it. If you write the text yourself, the Easy-Read Editor can help you break long paragraphs before you test.

Common mistakes

  • Shrinking text to avoid scrolling. Scrolling is normal on a phone. Tiny text is not.
  • Fixing the width in pixels. The page then cannot follow the screen.
  • Blocking pinch zoom. It removes the reader's own fix.
  • Packing links close together. Thumbs are larger than cursors.
  • Using wide tables without a scroll box. One table can push the whole page sideways.
  • Testing only in an emulator. Real thumbs and real sunlight show other problems.

FAQ

What font size should I use on a phone?

Start at 16 CSS pixels or larger for body text. This is a rule of thumb, not a standard. Test it on your own page.

What is a CSS pixel?

It is the unit a web page uses for sizes. It is not the same as one physical dot on the screen.

Do I need a separate mobile site?

No. One page that adapts to a narrow width can do the job. WCAG's Reflow page notes that responsive design is a common approach.

Is two-column text acceptable on a phone?

Rarely. A single column keeps the reading order simple and avoids sideways scrolling.

Sources

Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.

This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.