legibility

• SKILL.mdcore · 12,048 bytes
• references/lineage.mddoc · 8,165 bytes

# Legibility

> **Definition.** Legibility is the visual clarity of individual characters and short text — the ease with which a reader can identify each letter, number, or symbol at a glance. It's determined by typeface design, size, weight, color contrast, and the spacing within and between characters. Legibility is the *prerequisite* for reading; without it, the rest of typography (hierarchy, voice, readability) is pointless because the user can't reliably identify what they're looking at.

The classic test of legibility: can the reader distinguish similar characters quickly under the actual viewing conditions? "I" and "1" and "l" — three different characters that in many typefaces look nearly identical. "O" and "0." "rn" and "m." "5" and "S." "8" and "B." A typeface that makes these distinctions clear is legible; one that doesn't, isn't. The cost of poor legibility is paid every time the user has to look twice.

Legibility is distinct from *readability*. Readability concerns the ease of reading sustained prose — line length, leading, paragraph rhythm. Legibility concerns the ease of identifying individual characters or short phrases. A poster billboard, a button label, a code listing, a phone number on a contact card — all are legibility problems. A long article is primarily a readability problem (though it requires legibility too).

## Why legibility matters

Most UI text is not prose. It's labels, button text, form-field values, error messages, navigation items, search results. These are read in glances, often in motion (scrolling), often in poor conditions (small screens, harsh sunlight, while doing something else). The user has fractions of a second to identify what each chunk of text says.

Poor legibility costs the user every glance. They look, can't immediately resolve what the text says, look again, sometimes lean closer or zoom in. The cost is small per instance and large in aggregate.