Skip to content
On this page Definition

Atlas · DS131 · Layout: Scanning

F-Pattern Layout

Structures text content for horizontal and vertical scanning.

  • Status in 2026: Descriptive label. An informal label for a look, not a defined system.
  • Trend 2027 to 2030: Steady (an editorial projection, not a forecast).
  • The term: Known technical term or standard.

Definition

Structures text content for horizontal and vertical scanning.

Traits

  • aligned headlines
  • lists

Typical settings: Articles, Results.

When to use it, and when not

Consider it when the task and motivation match: readers of long pages. Typical settings: articles, results.

Be careful when the risk below would hurt the main task: treating the pattern as a universal law.

UX risk and how to reduce it

Risk: Treating the pattern as a universal law.

Mitigation and accessibility: Use headings and test real reading.

How to check: Test a prototype against a plain baseline on a real task: completion, time, errors, comprehension, accessibility and preference, segmented by context rather than by stereotype.

Evidence

Indirect: the sources support underlying principles, not a preference for this style.

The sources below support the principles that apply to this term. None of them shows that this style works better or is preferred.

Heuristic scales

Relative editorial judgements from 1 to 5. They are not results of a study and not a measure of quality.

Visual complexity heuristic
2 / 5 (1 is few visual elements, 5 is many layered elements)
Expressiveness heuristic
1 / 5 (1 is restrained, neutral, 5 is highly expressive)
Information density heuristic
4 / 5 (1 is sparse, 5 is dense)

In our library

No design-style recipe in @codeatlasdev/ui implements this term yet. You can still build it from the --ca-* tokens: see Theming.

Prompt for your AI

Paste this into a coding agent. It carries the trade-offs, and asks for a baseline to compare against.

Design this interface in the "F-Pattern Layout" direction (layout, scanning): Structures text content for horizontal and vertical scanning.
Visual and interaction traits to use: aligned headlines, lists.
Main UX risk: Treating the pattern as a universal law. Mitigate it: Use headings and test real reading.
Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion.
Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.

References

  1. W3C Web Accessibility Initiative (2021). WCAG 2 supplemental guidance. W3C WAI.Standard or guideline

    Supports: W3C WAI lists supplemental guidance for improving accessibility beyond what WCAG 2 requires, including a cognitive accessibility guidance set.

    Does not support: Normative requirements: supplemental guidance is advisory, not required for conformance. This page is an index; a specific recommendation needs the linked document.

    Checked 2026-10-25.

  2. Lindgaard, Fernandes, Dudek, Brown (2006). Attention web designers: You have 50 milliseconds to make a good first impression!. Behaviour & Information Technology.Supported

    Supports: In three studies, ratings of the visual appeal of web homepages were highly correlated between exposures of 50 ms and 500 ms.

    Does not support: That people decide whether to stay, trust or buy in 50 ms. The measure is a rating of visual appeal for a set of homepages in a lab, not behavior on a live site.

    Checked 2026-10-25.