How Users Actually Read Your Interface
Decades of eye-tracking research show people don't read interfaces — they scan them in predictable shapes. Here are the six patterns and where each one shows up.
Users read the top of a page across, drop down a bit and scan part of the next line, then trail their eyes down the left edge — describing the shape of an F. Dominant on text-heavy pages with weak visual hierarchy.
Eyes travel across the top, diagonally down to the lower-left, then across the bottom — tracing a Z. Common on sparse pages with a few focal elements and a clear call-to-action.
A reader's gaze sticks to one vertical band while scrolling — typically the center column. Common on mobile and during continuous-scroll reading where the cursor or thumb leads the eye.
Users skip large sections of content and land on visually distinct spots — buttons, prices, numbers, or boldface — like finding islands of meaning across a sea of text.
Eyes glide from heading to heading down the page, skipping body text entirely — only diving in when a heading promises something relevant. Hierarchy carries the entire experience.
When lines share repeated openings — "Step 1:", "Note:", or the identical leading word in every row of a table — readers skip the prefix entirely and jump straight to the unique content. It's the dominant pattern for scanning tables and lists of structured information, where the eye bypasses the redundant text down each column.
When an AI answer sits at the top of the page, the classic scan patterns give way to reading the response — and verifying its sources.
When a generated answer sits above the page, users read it instead of scanning what’s beneath. The F- and Z-patterns collapse into "read the answer, maybe glance below."
In an AI answer the new fixation target is the citation. Users skim past the prose to find — and click — the source that proves the claim before they trust it.