# Visual Hierarchy

Visual hierarchy uses position, scale, spacing, contrast, grouping, and sequence to reveal importance and guide attention through an interface.

- Type: principle
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/visual-hierarchy/>)

## What it means

Visual hierarchy is the ordered relationship that helps people see what matters first, what belongs together, and what can wait. Designers create it with layout, proximity, typography, color, imagery, and layering. Strong hierarchy reflects task priority and information structure rather than making everything compete.

## Why it matters

People scan interfaces before reading closely. Hierarchy lowers interpretation effort, makes primary actions easier to locate, and helps dense content feel navigable. It must also be supported by semantic headings, meaningful order, and labels so structure is not visual-only.

## When to use it

Use visual hierarchy on every screen, especially dashboards, forms, navigation, settings, and pages with competing actions. Revisit it when responsive layouts change, content grows, localization expands labels, or alerts and validation enter the page.

## How it works

1. Rank content and actions by user task, consequence, and frequency.
2. Create a reading path with placement and spacing before adding color or decoration.
3. Use a limited type scale and contrast system to distinguish levels consistently.
4. Group related items and separate unrelated regions without excessive boxes.
5. Check grayscale, zoom, keyboard order, heading semantics, and real-content extremes.

## A practical example

On an invoice page, amount due and date form the first group, followed by payment. Line items use a quieter but readable table, while account links sit in a secondary region. Semantic headings preserve structure for screen readers and a one-column layout.

## Where it breaks

Visual prominence is culturally and contextually influenced, and too many emphasis techniques create noise. Low-contrast secondary text becomes inaccessible. Hierarchy cannot fix poor information architecture, and visual order that differs from DOM or focus order confuses users.

## Common mistakes

- Making every card, badge, and action prominent
- Relying on color alone for priority or status
- Creating visual order that conflicts with reading and focus order

## Sources

1. [Human Interface Guidelines](<https://developer.apple.com/design/human-interface-guidelines>) — Apple · Institutional guideline
2. [Design tips](<https://developer.apple.com/design/tips/>) — Apple Developer · Institutional guidance
3. [Visual Representation](<https://assets.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/visual-representation>) — Interaction Design Foundation · Reference chapter

## Related topics

- [Typography in UI](<https://wiki.soroush.uk/topic/typography-in-ui/>)
- [Color in UI](<https://wiki.soroush.uk/topic/color-in-ui/>)
- [Grid System](<https://wiki.soroush.uk/topic/grid-system/>)
