How to set line lengths and spacing rules for pages that support both quick scans and sustained reading
Guidance on choosing line lengths and vertical spacing that keep routes workable for readers who scan reference sections as well as those who follow longer narrative passages.
Readers often move between short lookups and longer passages on the same page. Line length and spacing choices affect whether those shifts stay smooth or become interrupted. The aim is to keep text blocks comfortable for both patterns without forcing constant reorientation.
Fixed rules rarely suit every combination of tables, headings and paragraphs. Instead, designers need a short set of adjustable limits that can be checked against actual content growth. This article sets out practical limits and the checks that show when those limits need adjustment.
Choosing a base line length
A line length of roughly 65 to 75 characters remains the most workable average for sustained reading on desktop screens. Shorter lines increase the number of returns and can slow readers who stay with a narrative for several paragraphs. Longer lines make it harder for the eye to locate the start of the next line after a quick glance away to a table.
On smaller viewports the same character count produces lines that feel cramped once padding and side elements are added. A simple test is to measure the longest paragraph at each breakpoint and confirm that the count stays inside the range. If a table forces the text column narrower, the line length target can drop to 55 characters without harming readability, provided vertical spacing is increased slightly to compensate.
Setting vertical spacing between blocks
Vertical spacing between paragraphs, headings and tables should follow a consistent scale rather than arbitrary pixel values. A base unit of 0.75 times the body font size works for most text blocks. Headings then receive 1.5 times that unit above and below, while tables receive twice the unit above and once below to separate them from surrounding text.
The same scale should apply when content is added over time. If a new reference table is inserted, the spacing above and below it follows the rule rather than matching whatever gap existed before. This prevents gradual compression that makes routes harder to follow after several updates.
Adjusting for tables and lists
Tables and bulleted lists change the rhythm of reading. Lines inside table cells are usually shorter, so the surrounding paragraph text can stay at the standard length provided the table itself does not push the text column below 50 characters. When a table is wide, the text column narrows; in that case the line length target is relaxed only for the paragraphs immediately beside the table.
Lists benefit from slightly tighter spacing between items than between paragraphs. A 0.5 unit gap inside the list keeps the list visually grouped while the larger gap before and after the list restores separation from the main text flow. Over-tightening the list items makes quick scanning harder; over-widening them breaks the sense that the items belong together.
Testing at breakpoints
Breakpoints are checked by rendering the page at each defined width and counting characters on the longest text block. If the count exceeds 80 characters at any breakpoint, either the column width or the base font size is reduced. The same check is run after any content addition that changes column behaviour.
Keyboard navigation and screen reader order are reviewed at the same time. If a wide table causes the text to reflow below the table on narrow screens, the tab sequence must still follow the visual order. When it does not, a simple reorder of markup or an explicit aria-flowto attribute restores the route without altering spacing.
Reviewing after content growth
Pages that receive regular additions need a short quarterly check. The check records the current longest line length at each breakpoint and notes any new tables or lists. If the line length has drifted outside the 65–75 character band on more than one breakpoint, the column widths or base spacing unit is adjusted once rather than patched locally.
The same review notes whether vertical spacing still separates distinct blocks. When two tables sit closer than the agreed unit, one receives additional margin to restore the intended separation. This single adjustment prevents the slow accumulation of uneven gaps that make routes less predictable.
Limitations of rigid rules
These limits assume a standard body font size and a single text column beside reference material. Pages that place tables inside the text flow or that use multi-column reference sections require separate measurement. In those cases the character count is taken only on the primary narrative column, and the spacing scale is applied only to the gaps that readers cross when moving between narrative and reference.
Very narrow side panels used for quick reference can tolerate shorter line lengths without harming the main reading route, provided the panel is visually distinct. The test remains the same: measure the panel text at each breakpoint and confirm it does not force the main column below the minimum width chosen for sustained reading.
Consistent application of the line length range and the spacing scale keeps routes legible as pages grow. The checks are few and can be performed with ordinary browser tools, so they fit into ordinary maintenance without special equipment or external data.