Site and editorial

Facts

<forma-facts>

Short claims with supporting detail as a description list in a ruled, auto-fitting grid.

Authoring tag
<forma-facts>
Behavior owner
Site content
Canonical source
patterns/facts.html

Purpose

Facts 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).

Use when

  • Summarizing two to six headline claims in a hero aside or product section.
  • Showing release facts such as version, runtime and conformance target.
  • Each claim is a few words and its detail is one short line.

Avoid when

Behavior to know

  • Native dl semantics: each claim (dt) is paired with its detail (dd) inside a div wrapper, which HTML permits.
  • Claims are strong primary text; details are small muted text that stays AA on every tone.
  • Hairline rules separate items without doubling at shared edges.

Basic example

The smallest correct markup: the canonical pattern from patterns/facts.html inside its public tag. Copy this first, then adapt labels, names and state.

Canonical

Minimal facts

Rendered from the canonical pattern file.

Version 0.3.0
Pinned in the site's forma.lock
Zero runtime
HTML and CSS only
WCAG 2.2 AA
Target for stable patterns
HTML · Minimal facts Raw HTML for HTML · Minimal facts
<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.

Examples

Scenario

Engagement outcomes

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.

Recent engagements

40%+ throughput
Delivery flow realigned
Hours to minutes
Reconciliation stabilized
Zero regressions
Across three release trains
6 weeks
From diagnosis to treatment
HTML · Engagement outcomes Raw HTML for HTML · Engagement outcomes
<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.

Scenario

Facts on an inverse section

Facts inside a section with data-forma-tone="inverse". Claims, details and rules switch to the inverse tone colors without any per-component override.

Release 0.3.0

Zero runtime
HTML and CSS only
WCAG 2.2 AA
Target for stable patterns
Pinned
sha256 per asset in forma.lock
HTML · Facts on an inverse section Raw HTML for HTML · Facts on an inverse section
<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.

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

Phone stacked facts

Three facts, one with a long claim, at phone width. Items stack into a single ruled column.

Viewport width

Frames narrower than the selected width show the component at the width available.

What changes at narrow widths

  • Items fit by content with an 11rem minimum: two columns fit around 390px, and one column at 320px or with larger text.
  • Long claims and details wrap inside their item; items have min-inline-size: 0, so nothing scrolls horizontally.
  • Rules stay single-width at shared edges in every column count.
  • Facts are not interactive, so there are no touch targets to size.
HTML · Phone stacked facts Raw HTML for HTML · Phone stacked facts
<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.

Baseline

Mobile · 320px

The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.

Viewport width

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
AttributeOnValuesDefaultDescription
aria-labelledbysectionid of a heading—Names the region that contains the facts when the facts are introduced by a heading.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-factsBlock 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__itemElement 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.
Keyboard interaction
KeysResult
—Not interactive. Facts are read in source order.

States

Facts states
StateHow it is expressedPresentation
Defaultno attributesRuled grid on the surrounding tone.
Toneddata-forma-tone on an ancestorClaim, detail and rule colors follow the surrounding surface tone.

Accessibility

Forma provides

  • Keeps native description-list semantics so each claim and its detail are announced together.
  • Uses tone text pairs that stay AA for both claims and muted details on every tone.

Your application supplies

  • Introduce the facts with a heading, or keep them next to content that explains them.
  • Write claims that stand on their own; do not rely on position or layout to relate a claim to its detail.
  • Keep each item to one dt and one dd.

Responsive behavior

  • Auto-fit grid with minmax(min(100%, --forma-layout-fact-min), 1fr); columns drop by content, no breakpoints.
  • Items and text wrap; there is no fixed height, so text-spacing overrides and 200% text do not clip.

Motion

  • No animation: facts are static and have no hover or focus states.

Usage guidance

Do

  • Keep claims short and specific, with numbers or names where possible.
  • Keep sources for claims available on the page or linked nearby.

Avoid

  • Using facts for navigation or links.
  • Packing more than about six items into one list.

Verification specimens

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.