Disclosure / details
One short supporting explanation belongs in place beside the content it clarifies.
- Type
- UI-UX
- Sources
- 3
- Trail checked
Progressive disclosure, overlays, warnings, focus, and interruption management.
Browse all problem familiesAttention is part of the task. Disclosure reveals supporting detail when it becomes useful; interruption earns prominence when the person must decide or act before continuing.
Strong: A booking page shows the price and cancellation rule beside Reserve, while a labeled disclosure holds the full venue policy.
Weak: A booking page hides the cancellation charge in a tooltip and opens a modal for routine help while the visitor chooses a room.
Try it: Mark each item on a page as essential now, useful on request, or requiring an interruption, and explain the task consequence.
Begin with the core behavior, apply it in different contexts, then review cases that reveal the quality boundary. Open each entry for its decision rule, states, example, and source trail.
0 of 21 studies complete
Start this family →Learn the shared task and the core interaction choices.
One short supporting explanation belongs in place beside the content it clarifies.
Section headings provide a useful overview and users can choose which details to inspect.
The default task has a safe recommended path for most users.
Users repeatedly inspect selected records, tickets, alerts, files, assets, tasks, comments, or locations while staying in a work surface.
A compact control needs a brief supplemental explanation.
A short task must interrupt normal page interaction but should return users to the same context afterward.
Choose a specialized form for the context and follow its complete behavior.
A local control needs brief explanatory content or light editing while page context remains visible.
Users need to inspect object metadata before choosing whether to open a link, mention, file, row, issue, or reference.
Users repeatedly inspect files, messages, PDFs, images, videos, audio, invoices, contracts, designs, or attachments from a list or grid.
A local object or toolbar has three to eight secondary commands.
Objects or selections have secondary commands that experienced users expect near the target.
An urgent current-workflow condition requires acknowledgement, cancellation, retry, sign-out, review, or another explicit response before continuation.
The surface needs adaptive size, edge attachment, drag or detent behavior, or a clear temporary child-task mode.
Mobile users need extra contextual detail or controls while staying oriented to a map, feed, route, media item, or selected object.
Users need to inspect object detail, metadata, comments, history, or light actions while staying on the current page.
A temporary task needs the whole viewport for capture, immersive preview, focused setup, scanning, or dense editing.
Study failure cases and identify the better recovery route.
Use this anti-pattern entry to audit toolbars, row actions, cards, command bars, mobile action sheets, and generated UIs with symbol-only controls.
Use it when a generated UI wraps ordinary messages in dialog components because the design intent was underspecified.
Use it when a design review needs concrete evidence that motion is interrupting reading, form entry, recommendation feedback, or assistive-technology output.
Use this anti-pattern entry to review forms, checkout, applications, settings, data tables, eligibility flows, upload flows, and disabled actions where required information is hidden in a tooltip.
Use this anti-pattern to review temporary drawers, inspectors, side sheets, and mobile drawer layouts for missing close and return behavior.
Try fewer words, clear the filter, or search across all pattern families.
Search all patterns