Readable type is a system of choices

By Gyata Tabiri · Revised October 30, 2026

Readable type needs to be judged on the page where people will use it. I look at the text, the available space, and the surrounding hierarchy together, rather than treating one font-size value as the whole decision.

Choose units for their relationship

A rem value relates to the root font size, while em values depend on the relevant font-size context. Pixels can still be appropriate for some dimensions. The choice should explain what is meant to scale together, rather than express loyalty to a single unit.

Read the actual content

Review a normal paragraph, a long heading, a form label, and a dense table. Check the length of the line and the space between lines. Text that technically fits can still be tiring to read, particularly when the surrounding hierarchy is weak.

Test enlargement

Zoom the page and inspect whether content remains available and controls remain usable. Relative units help describe a scale, but do not by themselves make a layout accessible. Fixed heights, clipping, and constrained containers can still create problems.

Protect useful distinctions

Body copy, supporting notes, navigation, and captions have different jobs. Give each enough clarity without forcing everything to the same size. When making a site-wide adjustment, verify those roles separately so an improvement to article text does not accidentally change the footer or controls.

For a team, that means typography can be discussed through actual content and behavior: whether a label is readable, whether a heading wraps well, and whether the page still works when someone enlarges it.

Web design and UX examples · Discuss a role or project

Reference: CSS length units.