F4.03.1measuredesignresearch

Overlong measure makes the next line hard to find

Aliases: line length · column width · overlong line

What it is

After reading a line to its end, the eye has to travel back and land on the start of the next line. When the line is too long, that return crosses too much of the field, and the landing undershoots onto the line above, the line below, or the middle of the same line. What the reader feels is not “this line has a lot of words.” It is rereading a sentence, skipping one, and going back to align the left edge with a finger.

Overlong measure is a geometric failure of that return path. It is not the same as leading too tight, where contours collide: even when the rows are visually separate, the start can still sit at the far edge of the field and be missed.

Why it happens

A fixation covers only a few characters; a long line is a chain of forward saccades. At the end, the next saccade must reverse, travel far, and hit the first character of the next line. Longer travel means larger landing variance; at the same time the left edge is a stack of nearly identical line starts, with no unique target to aim at. Missing the line is then almost geometry, not inattention.

Chinese packs more per character and has no word spaces, so the return has fewer word-shape landmarks than Latin, and a wrong landing costs more: discovery depends on meaning, not on seeing an unexpected word outline. The usual product form is body copy stretched to the viewport on a wide display — the mockup looks “open” on a laptop and turns the return into a half-screen aiming task.

Justified long lines add a further cue conflict: the left edge is flush, but word spacing is stretched and the visual weight of each right edge differs, so the end of the line is a poor predictor of where the start should be. A ragged right at least makes each line end a fingerprint of “which line I am on”; once the line is long, that rag is negligible against the whole.

Studying it

Tinker treated measure as a primary independent in print reading, typically with speed, comprehension, and rated ease of keeping the place. On screens Dyson asked the same question: speed can even rise as lines lengthen (fewer returns), while preference and next-line errors move the other way. Reporting speed alone therefore yields a false “longer is better”; skip rate and effort have to travel with it.

Independents: characters or words per line, column width, number of columns, presence of line numbers or a dropped initial. Dependents: whether the first fixation after the return lands on the correct line start (eye tracking), skip count, speed, preference.

A method trap: labs often use a single quiet column. Product pages have navigation, cards, ads on both sides. Effective measure is the text column, not the window, but the surrounding noise makes the return harder still, so “still readable in the lab” is not a product ceiling.

Where it stops holding

Titles, formulae, code, and URLs are not prose returns; a long single line is often the structure of the content and should not be force-wrapped for aiming. Wide table cells are scanned sideways, not read line by line. Two or three short lines on a poster or slide carry no “find the next line” load no matter how wide. If the user stretches the window and the body stretches with it, the failure appears; if the column is capped and the extra width becomes margin, window width is not measure. Chinese, being roughly monospaced and without word spaces, packs more characters into the same pixel column, so overlength arrives earlier than in Latin.

Applying it

  • Cap the body column and spend leftover width on margins, not on more characters.
  • Check with a real paragraph at the target size (not a title, not a button): at the end of the line, does the next start have to be hunted?
  • On wide screens, several columns beat one stretched column; the gutter has to be wide enough that the return cannot land in the neighbour.
  • How to check: have someone read a full paragraph aloud and mark sudden rereads and silences. Those spots are usually a missed return, not hard content.

Related

  • Same group: F4.03.2 Overshort measure chops reading with constant wraps · F4.03.3 Constrain measure in characters, not pixels
  • Nearby: F4.02 Leading · F4.05 Alignment
  • Search terms: measure · line length · return sweep · characters per line

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/F4.03.1