# Progressive Disclosure

Progressive disclosure presents essential information and actions first, revealing secondary or advanced detail when users request or need it.

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

## What it means

Progressive disclosure is an interaction principle that manages complexity by staging information. The initial view emphasizes what most users need for the current decision; optional details, advanced settings, or later steps remain available through clear controls or context. It can be sequential, where later information appears after an action, or contextual, where extra detail is expanded in place.

## Why it matters

By postponing secondary material, progressive disclosure can improve scanning, reduce intimidating first impressions, and protect novices from irrelevant choices while preserving expert capability. It also helps small screens and complex forms focus attention on the next meaningful decision rather than presenting every possibility at once.

## When to use it

Use progressive disclosure when a screen contains genuinely secondary options, advanced configuration, lengthy explanations, or steps that depend on earlier choices. It works best when users can recognize how to reveal more and when hidden information is not required to make the visible decision safely.

## How it works

1. Separate information needed for the immediate decision from optional, advanced, or conditional detail.
2. Choose a reveal pattern—such as an accordion, details control, advanced section, or subsequent step—that matches the task.
3. Write a specific trigger label that predicts what will appear and indicate state when content is expanded.
4. Preserve entered data and context across reveals, and ensure keyboard, focus, and assistive-technology behavior is correct.
5. Test whether users notice the trigger and whether anything hidden is actually needed earlier.

## A practical example

An analytics tool initially asks for a report name, date range, and metric. An “Advanced scheduling” section reveals timezone, delivery format, recipients, and retry rules for teams that need automation. A short summary reflects hidden settings after they are configured, so users can review them without reopening the section.

## Where it breaks

Hiding information always reduces its discoverability. Progressive disclosure is harmful when concealed details affect consent, price, risk, eligibility, or the meaning of an action. It can also make comparison difficult when users must repeatedly open sections. Do not use it merely to make a cluttered design look clean; fix unnecessary complexity first.

## Common mistakes

- Hiding required or consequential information under a vague “More” link.
- Using accordions for short content that would be easier to scan when visible.
- Failing to preserve state, focus, or a summary after advanced options are closed.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/progressive-disclosure/#visualization-progressive-disclosure>)

## Sources

1. [Progressive Disclosure](<https://www.nngroup.com/articles/progressive-disclosure/>) — Nielsen Norman Group · Interaction-design guidance
2. [Accordions on Desktop: When and How to Use](<https://www.nngroup.com/articles/accordions-on-desktop/>) — Nielsen Norman Group · Usability guidance
3. [Understanding Success Criterion 3.2.2: On Input](<https://www.w3.org/WAI/WCAG22/Understanding/on-input.html>) — World Wide Web Consortium · Accessibility guidance

## Related topics

- [Content Hierarchy](<https://wiki.soroush.uk/topic/content-hierarchy/>)
- [Faceted Navigation](<https://wiki.soroush.uk/topic/faceted-navigation/>)
- [Navigation Design](<https://wiki.soroush.uk/topic/navigation-design/>)
