Text
| Sign | Why it hurts | What to use instead |
|---|---|---|
| a wall of text: a 10+ line paragraph | when scanning, the eye takes the first line and moves on | a paragraph is one thought, 3–5 lines (Chunking text) |
| a line across the whole monitor, 120–150 characters | the eye loses the start of the next line and rereads | a 45–80 character column (Line length) |
| justified text | without hyphenation the browser stretches the spaces, and white “rivers” run through the text | left-aligned (Left-aligned) |
| long centered text | every line has its own start — the eye looks for it again each time | center 1–2 lines: a heading, a caption |
| paragraphs IN CAPS | the letters share one height and lose ascenders and descenders, so words lose their shape; all caps reads slower than lowercase — Tinker and Paterson measured it back in 1928 | caps for short labels of 1–2 words, with letter spacing |
a thin weight (font-weight: 300 and below) in body text |
on an ordinary non-Retina screen the strokes turn gray and contrast drops | 400 for text, thin only for a large heading |
| three or more typefaces | each typeface is its own voice; the page sounds like an anthology | one for text and headings, a second monospace one for code |
| long passages in italic | italic is for a word or two; in many fonts italic in other scripts switches to handwritten forms — Cyrillic “т” looks like “m”, “и” like “u” — and long passages get harder to read | italic for a word or two; longer emphasis another way |
Emphasis
| Sign | Why it hurts | What to use instead |
|---|---|---|
| half a paragraph in bold | emphasis works only against ordinary text | one or two spots per screen (Bold: one or two spots) |
| underlining that isn’t a link | on screen, underlined means a link; people click it | bold; keep underlining for links |
| bold, color, caps and an exclamation mark at once | four signals where one is enough | one method |
| “Important!”, “Note!” every other paragraph | warnings lose weight and start getting skipped | one warning per page |
| emoji as list bullets | a screen reader reads each one aloud (“green check mark”), and the item starts with a picture instead of a word | an ordinary bullet; an icon only if it means something |
Color and contrast
| Sign | Why it hurts | What to use instead |
|---|---|---|
gray text lighter than #767676 on white |
below 4.5:1 it fails WCAG and vanishes in sunlight | secondary text at 4.5:1 or more (Text contrast) |
| color as the only signal: “red ones are errors” | about 8% of men distinguish red and green less well; printed in black and white the meaning is lost | color plus a second signal: an icon, a word, a shape |
| five or more accent colors | color stops meaning anything: every block has its own | one accent plus neutrals; colors for meaningful labels (formats, statuses) |
| white text on a light button | on green #22c55e it’s 2.28:1 |
a darker background or dark text |
| a dark theme that inverts the light one | shadows, grays and images are designed for a light background; inverted, everything is flat and garish | dark theme colors of its own, with contrast checked separately |
a pure #000 background and pure #fff text |
21:1 is 4.7 times the threshold; bright white on black glares in the dark | near-black and near-white: #131210 and #f2eee8 — 16.2:1 |
Spacing and alignment
| Sign | Why it hurts | What to use instead |
|---|---|---|
| the same spacing everywhere | you can’t see what belongs with what: a heading hangs between paragraphs | smaller inside a group, larger between groups (White space in CSS) |
| identical blocks with different spacing | the eye sees the difference and looks for meaning in it | a spacing scale: 4, 8, 12, 16, 24, 32 px |
| elements on different vertical lines | the edge “jitters” — the page looks sloppy even if you can’t say why | a shared grid: everything side by side starts from one line |
| a border around every block | borders draw a grid, and attention goes to it | group with spacing or a background; a border only where nothing else works |
| no margins at the screen edge on a phone | text sticks to the edge, and the first letter disappears under the rounded corner | a margin of 16 px or more |
Tables and lists
| Sign | Why it hurts | What to use instead |
|---|---|---|
| a grid of lines around every cell | the lines are louder than the data | thin horizontal rules, or alternating row backgrounds |
| left-aligned numbers | the digits don’t line up by place, so comparing is hard | numbers right-aligned, with tabular figures: font-variant-numeric: tabular-nums |
| a one-column table | that’s a list | a bulleted list |
| 6+ columns on a phone | horizontal scrolling, and the header scrolls away | 2–3 columns, or cards on a narrow screen |
| a list nested 4 levels deep | the links between levels get lost | 2 levels; deeper — a subheading and a new list |
Images, icons, screenshots
| Sign | Why it hurts | What to use instead |
|---|---|---|
| a screenshot of code or a terminal | can’t be copied, searched or read on a phone | a code block as text (Code as text) |
| a screenshot of the whole screen | the button you need is a dot somewhere in the corner | crop to the right spot and mark where to look |
| icons without labels | only the most familiar icons are understood unambiguously: search, close, home | an icon with a label next to it |
| decorative images in every section | meaningful images can’t be told from decoration, so both get skipped | an image where it explains; one decorative image for the whole page |
| a stock photo of “a team at a laptop” | it carries no information but takes up the first screen | a diagram, a screenshot, a relevant illustration — or nothing |
The page and the interface
| Sign | Why it hurts | What to use instead |
|---|---|---|
| the first screen holds a banner, cookies, a chat and a newsletter signup | the answer is pushed to the second screen, while 57% of the time is spent on the first | the first screen holds the heading, the lead and one action (One screen, one idea) |
| a slide carousel | the text moves on before it’s read; Erik Runyon’s measurements (2013) on the University of Notre Dame site found about 1% of visitors click a carousel, and 84% of clicks go to the first slide | one main message, static; the rest as a list below |
| a placeholder instead of a field label | it vanishes on input: you can no longer see what was asked | a label above the field, and the placeholder as an example value |
| links reading “here”, “more”, “read more” | a list of links doesn’t say where they lead | link text says where it leads (Link text) |
| buttons smaller than 24×24 px | fingers miss them, especially at the screen edge | 24×24 px or more (WCAG 2.5.8), 44×44 for frequent ones (2.5.5) |
If it doesn’t work
The page looks “cheap”, and it’s unclear what exactly is wrong
- Cause
- Most often small things that add up: three typefaces, five shades of gray, different spacing on identical blocks, alignment to different lines.
- Fix
- Squint at the page or blur it (Checking presentation): the eye itself shows where blobs and lines don’t match.
Everything follows the rules, and the page is boring
- Cause
- The rules remove what’s in the way but give no accent: everything is even, and the eye has nothing to catch on first.
- Fix
- One strong accent per screen: a large heading, an illustration, a number — whatever is primary (Three levels of importance).