Body size has a viewing-distance floor
Aliases: body size floor · reading-distance type size · body rung
What it is
A type scale is not decorated down from the title. It stands on the body rung. Body is the size people inhabit for the longest, over the largest area, and it has a floor that moves with viewing distance: about a foot for a phone in the hand, about two for a laptop, several metres for a living-room set. Copy a barely readable phone body onto a far-away screen and the ladder’s structure survives while reading does not.
What is at stake is how the scale picks its anchor, not another derivation of visual angle. Visual angle already folds size and distance into one quantity; that belongs with visual capability. Typography takes the consequence: for each device class, choose a body that can be read continuously at that distance, then grow titles and captions from it.
Why it happens
Every contrast on the ladder is relative to body. If body is already on the readable floor, two rungs of title are merely “slightly larger small type,” and captions drop below identification. The floor is not a luxury constraint on display sizes. It is the ladder’s ground: when it sinks, every rung sinks with it.
Change the distance and the same physical size subtends a different angle. The usual product mistake is to treat “we use 16 on the phone” as a cross-device truth and ship one pixel ladder everywhere. What can be shared is the role structure — body, title, caption — not the pixel values. Far-away UIs have to raise the body rung, and sometimes drop rungs, because large type already spends screen share that used to hold extra levels.
x-height moves the floor. A nominal 16px Latin face with a small x-height can read smaller than a 15px face with a taller one. CJK glyphs typically fill more of the em, so the same nominal size is closer to “already using the whole body”; the floor cannot be copied from Latin product habit.
Studying it
In the print-legibility tradition, Tinker treated size and viewing distance as joint conditions of the copy, measuring speed, comprehension, and rated effort; screen work keeps the logic and changes the distance to handheld or desk. There is no need to rerun acuity-threshold experiments. What is needed is continuous-prose reading at the typical distance of the target device, asking whether the body rung still carries efficiency.
Independent variables: body size, device class (hence distance), x-height of the face. Dependent variables: reading speed, comprehension items, rated effort, whether people lean in.
A method trap: previewing a television UI on a laptop tests the designer’s distance, not the user’s. Put the device at the intended distance, or scale to that subtended angle. Judging a mockup as “looks big enough” does not count.
Where it stops holding
Labels, buttons, and navigation meant for a glance may sit below the continuous-reading floor — they are not there to host paragraphs. Body in books, help, and terms must be set for continuous reading; a tight UI look is not a reason to shrink paragraphs to caption size.
When the user enlarges system type, product body should grow with it rather than stay nailed to the mockup’s pixel floor. The floor is a safety net for the default setting, not a ceiling against user choice. Low vision, older readers, and outdoor glare all push the effective floor up on the same device; calibrating on the designer’s own reading in a dim room systematically undershoots.
Applying it
- Pick the body rung per device class first: read a couple of paragraphs at the real distance, then derive the other rungs.
- Do not write phone body pixels into a television or conference-room scale. Role names can be shared; the numbers must be re-pinned.
- Recheck body after a typeface or language change. If x-height or CJK face height moved, the floor moved.
- How to check: sit at the intended distance for that device class and read a paragraph. Leaning in, slowing to a murmur, or skipping is a fail. “Looks large on the artboard” is not a pass.