Overview disclosure splits a result into two parts: an always-visible overview that states what the user must know to act (the state, its scope, how certain it is, what is still unresolved, and whether more verification is needed), and one or more Disclosure sections below it for supporting evidence. It is a labelled section (forma-overview-disclosure) whose first child is forma-overview-disclosure__overview, marked with a thick inline-start rule, followed by native details class="forma-disclosure" elements. Forma provides the structure and spacing. Deciding what is consequential, and writing the state text, is the application's job; the pattern never infers state, freshness or legality.
Use when
A verification, reconciliation or review result has supporting evidence that most users do not need to read every time.
Hiding the wrong detail could lead someone to act on stale, partial or unknown information.
A screen follows the Visual Engineering rule that disclosure may hide secondary detail but never consequential state.
Avoid when
The hidden content is ordinary optional detail with no consequential summary: use Disclosure alone.
The whole task is recognize, verify, then act with a decision: use Verification frame.
You need to list distinct authoritative states side by side: use State survivability.
The overview is never collapsible; only the evidence below it is.
The overview is marked by a 0.25rem rule in the current text color, not by a status color.
The section is named by the overview heading through aria-labelledby.
Evidence sections are standard Disclosure elements with their own motion and states.
Basic example
The smallest correct markup: the canonical pattern from patterns/overview-disclosure.html inside its public tag. Copy this first, then adapt labels, names and state.
Canonical
Minimal overview disclosure
Rendered from the canonical pattern file.
Live demo. 1 native action works here and is verified by an outcome test.
Verification still required
State: Evidence is stale. One unresolved item remains before the application can confirm the transition.
Inspect secondary evidence
Last verified 3 hours ago. Source B has not responded to reconciliation.
<forma-overview-disclosure class="forma-component-tag">
<section class="forma-overview-disclosure" aria-labelledby="overview-title">
<div class="forma-overview-disclosure__overview">
<h3 id="overview-title">Verification still required</h3>
<p><strong>State:</strong> Evidence is stale. One unresolved item remains before the application can confirm the transition.</p>
</div>
<details class="forma-disclosure" data-forma-motion-weight="light">
<summary>Inspect secondary evidence</summary>
<div class="forma-disclosure__content">
<p>Last verified 3 hours ago. Source B has not responded to reconciliation.</p>
</div>
</details>
</section>
</forma-overview-disclosure>
Click or tap the code once to select all of it, then copy.
Examples
Scenario
Reconciliation with an unknown source
One source has not answered, so the result is explicitly Unknown, not Failed. The overview states the state as text with a Status lozenge, the scope (3 of 4 sources), and what remains. Two evidence sections hold the per-source detail and the raw timestamps.
Live demo. 2 native actions work here and are verified by an outcome test.
Ledger reconciliation incomplete
Unknown 3 of 4 sources reconciled. Source D (card processor) has not responded since 09:40.
Unresolved: 1 source. Do not close the period until it reconciles or is excluded by an approver.
Per-source results
Source A (bank): matched, 1,204 entries
Source B (payroll): matched, 86 entries
Source C (expenses): matched, 342 entries
Source D (card processor): no response
Request timestamps
Last request to Source D at 09:40 UTC; two retries at 09:45 and 09:55 without a response.
<forma-overview-disclosure class="forma-component-tag">
<section class="forma-overview-disclosure" aria-labelledby="overview-disclosure-reconciliation-unknown-title">
<div class="forma-overview-disclosure__overview">
<h3 id="overview-disclosure-reconciliation-unknown-title">Ledger reconciliation incomplete</h3>
<p><span class="forma-status-lozenge" data-state="unknown">Unknown</span> 3 of 4 sources reconciled. Source D (card processor) has not responded since 09:40.</p>
<p><strong>Unresolved:</strong> 1 source. Do not close the period until it reconciles or is excluded by an approver.</p>
</div>
<details class="forma-disclosure" data-forma-motion-weight="light">
<summary>Per-source results</summary>
<div class="forma-disclosure__content">
<ul>
<li>Source A (bank): matched, 1,204 entries</li>
<li>Source B (payroll): matched, 86 entries</li>
<li>Source C (expenses): matched, 342 entries</li>
<li>Source D (card processor): no response</li>
</ul>
</div>
</details>
<details class="forma-disclosure" data-forma-motion-weight="light">
<summary>Request timestamps</summary>
<div class="forma-disclosure__content">
<p>Last request to Source D at 09:40 UTC; two retries at 09:45 and 09:55 without a response.</p>
</div>
</details>
</section>
</forma-overview-disclosure>
Click or tap the code once to select all of it, then copy.
Scenario
Verified with nothing outstanding
A complete result still keeps its scope and freshness in the overview, including the explicit statement that nothing is unresolved, so the absence of work is stated rather than implied by missing content.
Live demo. 1 native action works here and is verified by an outcome test.
Access review complete
Confirmed All 58 accounts in the Finance group reviewed. Verified .
Unresolved: none.
Reviewer decisions
54 accounts kept, 4 removed. Decisions recorded by R. Osei and M. Laine.
<forma-overview-disclosure class="forma-component-tag">
<section class="forma-overview-disclosure" aria-labelledby="overview-disclosure-verified-nothing-outstanding-title">
<div class="forma-overview-disclosure__overview">
<h3 id="overview-disclosure-verified-nothing-outstanding-title">Access review complete</h3>
<p><span class="forma-status-lozenge" data-state="ok">Confirmed</span> All 58 accounts in the Finance group reviewed. Verified <time datetime="2026-09-30T08:15Z">today at 08:15 UTC</time>.</p>
<p><strong>Unresolved:</strong> none.</p>
</div>
<details class="forma-disclosure" data-forma-motion-weight="light">
<summary>Reviewer decisions</summary>
<div class="forma-disclosure__content">
<p>54 accounts kept, 4 removed. Decisions recorded by R. Osei and M. Laine.</p>
</div>
</details>
</section>
</forma-overview-disclosure>
Click or tap the code once to select all of it, then copy.
Mobile
Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.
Mobile example
Stale evidence on a phone
A stale certificate check at phone width. The overview wraps but stays first and visible; the evidence is one tap away.
Live demo. 1 native action works here and is verified by an outcome test.
Frames narrower than the selected width show the component at the width available.
What changes at narrow widths
The section is a single-column grid at every width, so the overview is always first in reading order and on screen.
Overview text wraps inside the 0.75rem padding beside the inline-start rule; no content is truncated or hidden at 320px.
Each evidence summary is a 44px-minimum tap target and its content opens in flow below it.
There are no breakpoints: recomposition never moves consequential state into a collapsed section.
<forma-overview-disclosure class="forma-component-tag">
<section class="forma-overview-disclosure" aria-labelledby="overview-disclosure-mobile-stale-evidence-title">
<div class="forma-overview-disclosure__overview">
<h3 id="overview-disclosure-mobile-stale-evidence-title">Certificate check is stale</h3>
<p><span class="forma-status-lozenge" data-state="attention">Needs attention</span> Last checked 26 hours ago; checks are expected every 6 hours. Current expiry status is not known.</p>
</div>
<details class="forma-disclosure" data-forma-motion-weight="light">
<summary>Last known result</summary>
<div class="forma-disclosure__content">
<p>api.example.net: valid until 14 January 2027, issued by the internal CA.</p>
</div>
</details>
</section>
</forma-overview-disclosure>
Click or tap the code once to select all of it, then copy.
Baseline
Mobile · 320px
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
Live demo. 1 native action works here and is verified by an outcome test.
Frames narrower than the selected width show the component at the width available.
API and configuration
Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.
Native and ARIA attributes
Attribute
On
Values
Default
Description
aria-labelledby
section.forma-overview-disclosure
id of the overview heading
—
Names the section from its overview heading so it is exposed as a named region.
data-forma-motion-weight
details.forma-disclosure
light | standard | heavy
light
Motion weight of each evidence disclosure; see Disclosure.
datetime
time
ISO 8601
—
Machine-readable freshness when the overview states when something was verified.
CSS hooks (derived from dist/all.css)
Hook
Kind
Values or default
Description
.forma-overview-disclosure
Block class
—
Section grid that stacks the overview above the evidence disclosures with a 0.75rem gap.
.forma-overview-disclosure__overview
Element class
—
Always-visible overview: padded grid with a 0.25rem inline-start rule in the current text color; first and last children lose their block margins.
Keyboard interaction
Keys
Result
Tab / Shift+Tab
Moves to each evidence summary (and any links in the overview).
Enter / Space on a summary
Opens or closes that evidence section (native details).
Events
Event
Description
toggle
Native event on each evidence disclosure when it opens or closes.
Form behavior
No form participation.
States
Overview disclosure states
State
How it is expressed
Presentation
Overview visible
always
State, scope, uncertainty and unresolved work are shown as text; there is no collapsed state for the overview.
Unknown, stale, partial, reconciling or confirmed are written by the application; the pattern itself has no state hooks.
Accessibility
Forma provides
Keeps the overview outside any disclosure, so it is always in the accessibility tree and on screen.
Marks the overview with a rule that follows the text color, including in forced-colors mode, rather than a semantic color.
Uses native details for evidence, with announced expanded state and 44px summaries.
Your application supplies
Write the state in words (Unknown, Stale, Reconciling), not only as a lozenge color.
State scope and unresolved work explicitly, including "none" when nothing is outstanding.
Choose a heading level that fits the page outline.
Keep the overview accurate to authoritative application state; never strengthen unknown into failure or success.
Responsive behavior
Single-column grid at every width; the overview is first in source and visual order.
Text wraps inside the overview; evidence opens in flow below.
No breakpoints and no horizontal overflow at 320px.
Motion
The overview does not animate. Evidence sections use Disclosure motion: the + / × indicator turns with light spring timing, content fades and settles on open, and block size settles where interpolate-size is supported.
Under prefers-reduced-motion: reduce the disclosure height transition is removed and the rest is effectively instant.
Usage guidance
Do
Answer "can I act on this?" in the overview's first sentence.
Keep evidence sections named by what they contain.
Avoid
Moving unresolved items or uncertainty into a collapsed section to shorten the page.
Using the rule color or lozenge color as the only indicator of state.
Collapsing the whole component into a single disclosure on phones.