VERIFICATION-0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF
- Version 0.3.0 · Extended localized content for verification and layout resilience
- Pinned in the site's forma.lock
- Zero runtime
- HTML and CSS only
- WCAG 2.2 AA
- Target for stable patterns
<forma-facts>
Short claims with supporting detail as a description list in a ruled, auto-fitting grid.
<forma-facts>patterns/facts.htmlFacts present a few short, verifiable claims (a version, a result, a standard) each with one line of supporting detail. The markup is a native description list: each .forma-facts__item wraps one dt claim and one dd detail, so assistive technology hears the pairing. The list lays out as a ruled grid whose columns fit by content using --forma-layout-fact-min (11rem).
dl semantics: each claim (dt) is paired with its detail (dd) inside a div wrapper, which HTML permits.The smallest correct markup: the canonical pattern from patterns/facts.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
<forma-facts class="forma-component-tag">
<div class="forma-site">
<dl class="forma-facts">
<div class="forma-facts__item"><dt>Version 0.3.0</dt><dd>Pinned in the site's forma.lock</dd></div>
<div class="forma-facts__item"><dt>Zero runtime</dt><dd>HTML and CSS only</dd></div>
<div class="forma-facts__item"><dt>WCAG 2.2 AA</dt><dd>Target for stable patterns</dd></div>
</dl>
</div>
</forma-facts>
Click or tap the code once to select all of it, then copy.
Four measured outcomes under a heading. On wide containers all four share a row; as the width shrinks the grid drops to two columns, then one.
<forma-facts class="forma-component-tag">
<div class="forma-site">
<section aria-labelledby="facts-engagement-outcomes-title">
<h3 id="facts-engagement-outcomes-title">Recent engagements</h3>
<dl class="forma-facts">
<div class="forma-facts__item"><dt>40%+ throughput</dt><dd>Delivery flow realigned</dd></div>
<div class="forma-facts__item"><dt>Hours to minutes</dt><dd>Reconciliation stabilized</dd></div>
<div class="forma-facts__item"><dt>Zero regressions</dt><dd>Across three release trains</dd></div>
<div class="forma-facts__item"><dt>6 weeks</dt><dd>From diagnosis to treatment</dd></div>
</dl>
</section>
</div>
</forma-facts>
Click or tap the code once to select all of it, then copy.
Facts inside a section with data-forma-tone="inverse". Claims, details and rules switch to the inverse tone colors without any per-component override.
<forma-facts class="forma-component-tag">
<div class="forma-site">
<section class="forma-section" data-forma-tone="inverse" aria-labelledby="facts-inverse-surface-title">
<h3 id="facts-inverse-surface-title">Release 0.3.0</h3>
<dl class="forma-facts">
<div class="forma-facts__item"><dt>Zero runtime</dt><dd>HTML and CSS only</dd></div>
<div class="forma-facts__item"><dt>WCAG 2.2 AA</dt><dd>Target for stable patterns</dd></div>
<div class="forma-facts__item"><dt>Pinned</dt><dd>sha256 per asset in forma.lock</dd></div>
</dl>
</section>
</div>
</forma-facts>
Click or tap the code once to select all of it, then copy.
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.
Three facts, one with a long claim, at phone width. Items stack into a single ruled column.
min-inline-size: 0, so nothing scrolls horizontally.<forma-facts class="forma-component-tag">
<div class="forma-site">
<dl class="forma-facts">
<div class="forma-facts__item"><dt>Version 0.3.0</dt><dd>Pinned in the site's forma.lock</dd></div>
<div class="forma-facts__item"><dt>Deterministic distribution builds</dt><dd>Two builds of the same source produce identical files</dd></div>
<div class="forma-facts__item"><dt>Zero runtime</dt><dd>HTML and CSS only</dd></div>
</dl>
</div>
</forma-facts>
Click or tap the code once to select all of it, then copy.
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
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.
| Attribute | On | Values | Default | Description |
|---|---|---|---|---|
aria-labelledby | section | id of a heading | — | Names the region that contains the facts when the facts are introduced by a heading. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-facts | Block class | — | The dl. An auto-fit grid with an 11rem minimum column, top and inline-start rules, and a block-space top margin. |
.forma-facts__item | Element class | — | The div that wraps one dt and one dd. Draws its end and bottom rules; dt is strong text, dd is small muted text. |
| Keys | Result |
|---|---|
| — | Not interactive. Facts are read in source order. |
| State | How it is expressed | Presentation |
|---|---|---|
| Default | no attributes | Ruled grid on the surrounding tone. |
| Toned | data-forma-tone on an ancestor | Claim, detail and rule colors follow the surrounding surface tone. |
dt and one dd.minmax(min(100%, --forma-layout-fact-min), 1fr); columns drop by content, no breakpoints.Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.