Attention and verification

Attention path

<forma-attention-path>

Declares an intended first-glance priority path while preserving semantic source order and explicit text when visual emphasis channels are removed.

Authoring tag
<forma-attention-path>
Behavior owner
Application content
Canonical source
patterns/attention-path.html

Purpose

An attention path structures a consequential screen so the thing that needs attention first is recognized first, and the rest is read in a declared order. It has one heavily framed primary region and a grid of supporting regions. Each region can declare its place with data-attention-step, and Forma prints that as a visible "Priority N" label, so the intended order survives grayscale, removed borders and forced colors. The path follows source order; Forma never reorders content visually. Which issue is primary, and what the steps are, is decided by the application from its own state.

Use when

  • A review or decision screen has several regions competing for attention, and one issue must be recognized before anything else.
  • The intended reading order should be explicit and testable rather than implied by size or color.
  • The screen must remain intelligible under grayscale, forced colors or removed visual emphasis.

Avoid when

  • Several independent regions each need to be limited to one primary claimant: use Emphasis budget.
  • The task is an explicit recognize, verify, act sequence before a transition: use Verification frame.
  • The content is an ordinary page section with no competing emphasis: use Section or Stack.
  • The primary region would be a transient message: use Alert or Callout.

Behavior to know

  • The primary region has a 2px functional border, surface background and padding; supporting regions have only a thin top rule.
  • data-attention-step produces a visible mono uppercase "Priority N" label before the region.
  • Supporting regions sit in an auto-fit grid of columns at least 15rem wide and collapse to one column on narrow screens.
  • Order is always source order: the path is declared, not rearranged.

Basic example

The smallest correct markup: the canonical pattern from patterns/attention-path.html inside its public tag. Copy this first, then adapt labels, names and state. This component owns a page's main landmark, so it renders in its own document below.

Canonical

Minimal attention path

Rendered from the canonical pattern file.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

HTML · Minimal attention path Raw HTML for HTML · Minimal attention path
<forma-attention-path class="forma-component-tag">
<main class="forma-attention-path" aria-labelledby="attention-title">
  <header>
    <p class="forma-component-kicker">Release verification</p>
    <h2 id="attention-title">Human review required</h2>
  </header>
  <section class="forma-attention-path__primary" data-attention-step="1" aria-labelledby="attention-primary">
    <span class="forma-status-lozenge" data-state="unknown">Unknown consumer outcome</span>
    <h3 id="attention-primary">Reconcile the consumer smoke test before publishing</h3>
    <p>The package build passed, but the consuming application has not reported a current verification result.</p>
    <div class="forma-cluster">
      <button type="button">Reconcile consumer</button>
      <button type="button">Inspect evidence</button>
    </div>
  </section>
  <div class="forma-attention-path__support">
    <section data-attention-step="2" aria-labelledby="attention-evidence">
      <h3 id="attention-evidence">Evidence</h3>
      <p>CI run 1042 passed 148 checks. Package contents were generated successfully.</p>
    </section>
    <section data-attention-step="3" aria-labelledby="attention-context">
      <h3 id="attention-context">Context</h3>
      <p>Release 1.4.0 changes comparison and verification presentation contracts.</p>
    </section>
    <section data-attention-step="4" aria-labelledby="attention-history">
      <h3 id="attention-history">Recent history</h3>
      <p>Two previous releases completed without reconciliation work.</p>
    </section>
  </div>
</main>
</forma-attention-path>

Click or tap the code once to select all of it, then copy.

Examples

Scenario

Blocked payment release

A treasury screen where the primary step is a blocked payment that needs a second approver. Evidence and context are supporting steps. Status is text, and the critical amount uses .forma-critical-value for deliberate reading.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

Treasury · payment run 118

One payment needs a second approver

Blocked: second approval required

Approve payment to Hanseatische Maschinenbau GmbH

Amount €148,200.00 exceeds the single-approver limit of €100,000.00.

Evidence

Invoice matched to purchase order PO-7782 and goods receipt GR-5521.

Rest of the run

41 other payments are approved and scheduled for 14:00.

HTML · Blocked payment release Raw HTML for HTML · Blocked payment release
<forma-attention-path class="forma-component-tag">
  <section class="forma-attention-path" aria-labelledby="attention-path-payment-release-title">
    <header>
      <p class="forma-component-kicker">Treasury · payment run 118</p>
      <h2 id="attention-path-payment-release-title">One payment needs a second approver</h2>
    </header>
    <section class="forma-attention-path__primary" data-attention-step="1" aria-labelledby="attention-path-payment-release-primary">
      <span class="forma-status-lozenge" data-state="blocked">Blocked: second approval required</span>
      <h3 id="attention-path-payment-release-primary">Approve payment to Hanseatische Maschinenbau GmbH</h3>
      <p>Amount <span class="forma-critical-value">€148,200.00</span> exceeds the single-approver limit of €100,000.00.</p>
      <div class="forma-cluster">
        <button type="button">Request second approval</button>
        <button type="button">View invoice</button>
      </div>
    </section>
    <div class="forma-attention-path__support">
      <section data-attention-step="2" aria-labelledby="attention-path-payment-release-evidence">
        <h3 id="attention-path-payment-release-evidence">Evidence</h3>
        <p>Invoice matched to purchase order PO-7782 and goods receipt GR-5521.</p>
      </section>
      <section data-attention-step="3" aria-labelledby="attention-path-payment-release-run">
        <h3 id="attention-path-payment-release-run">Rest of the run</h3>
        <p>41 other payments are approved and scheduled for 14:00.</p>
      </section>
    </div>
  </section>
</forma-attention-path>

Click or tap the code once to select all of it, then copy.

Scenario

Reconciling state with long localized text

The primary issue is an application-reported reconciling state, shown as its own state rather than collapsed into failure. Long German text wraps inside every region, and a supporting region without a declared step simply has no priority label.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

Lagerbestand

Bestandsabgleich läuft

Abgleich läuft – Ergebnis noch nicht bekannt

Keine Umbuchungen bis zum Abschluss der Inventurdifferenzprüfung

Das Lagerverwaltungssystem hat den Abgleich um 09:40 gestartet und noch kein Ergebnis gemeldet.

Umfang

Betroffen sind 3 Lagerorte und 1.284 Artikelpositionen.

Hilfe

Der Abgleich dauert üblicherweise weniger als 30 Minuten.

HTML · Reconciling state with long localized text Raw HTML for HTML · Reconciling state with long localized text
<forma-attention-path class="forma-component-tag">
  <section class="forma-attention-path" aria-labelledby="attention-path-reconciling-title" lang="de">
    <header>
      <p class="forma-component-kicker">Lagerbestand</p>
      <h2 id="attention-path-reconciling-title">Bestandsabgleich läuft</h2>
    </header>
    <section class="forma-attention-path__primary" data-attention-step="1" aria-labelledby="attention-path-reconciling-primary">
      <span class="forma-status-lozenge" data-state="unknown">Abgleich läuft – Ergebnis noch nicht bekannt</span>
      <h3 id="attention-path-reconciling-primary">Keine Umbuchungen bis zum Abschluss der Inventurdifferenzprüfung</h3>
      <p>Das Lagerverwaltungssystem hat den Abgleich um 09:40 gestartet und noch kein Ergebnis gemeldet.</p>
      <div class="forma-cluster"><button type="button">Status aktualisieren</button></div>
    </section>
    <div class="forma-attention-path__support">
      <section data-attention-step="2" aria-labelledby="attention-path-reconciling-scope">
        <h3 id="attention-path-reconciling-scope">Umfang</h3>
        <p>Betroffen sind 3 Lagerorte und 1.284 Artikelpositionen.</p>
      </section>
      <section aria-labelledby="attention-path-reconciling-help">
        <h3 id="attention-path-reconciling-help">Hilfe</h3>
        <p>Der Abgleich dauert üblicherweise weniger als 30 Minuten.</p>
      </section>
    </div>
  </section>
</forma-attention-path>

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

Mobile review path

At phone width the supporting steps stack under the primary region and the primary actions become full-width buttons.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

Viewport width

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

What changes at narrow widths

  • The supporting grid uses minmax(min(100%, 15rem), 1fr), so below about 31rem it is a single column in step order.
  • At 30rem and below the action cluster inside the primary region becomes a one-column grid of full-width buttons at least 2.75rem tall, and button text wraps instead of overflowing.
  • Status lozenges and headings wrap anywhere, so long identifiers or 200% text do not cause horizontal scrolling at 320px.
  • The Priority labels stay visible in portrait and landscape; the order never changes with orientation.
HTML · Mobile review path Raw HTML for HTML · Mobile review path
<forma-attention-path class="forma-component-tag">
  <section class="forma-attention-path" aria-labelledby="attention-path-mobile-title">
    <header>
      <p class="forma-component-kicker">Access review</p>
      <h2 id="attention-path-mobile-title">Contractor access expires today</h2>
    </header>
    <section class="forma-attention-path__primary" data-attention-step="1" aria-labelledby="attention-path-mobile-primary">
      <span class="forma-status-lozenge" data-state="attention">Expires at 18:00</span>
      <h3 id="attention-path-mobile-primary">Extend or remove access for M. Chen</h3>
      <div class="forma-cluster"><button type="button">Extend 30 days</button><button type="button">Remove access</button></div>
    </section>
    <div class="forma-attention-path__support">
      <section data-attention-step="2" aria-labelledby="attention-path-mobile-usage">
        <h3 id="attention-path-mobile-usage">Recent use</h3>
        <p>Last sign-in 2 hours ago from the office network.</p>
      </section>
    </div>
  </section>
</forma-attention-path>

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.

Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.

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
data-attention-stepprimary and supporting regionspositive integerabsentDeclares the region's place in the intended attention path and renders a visible "Priority N" label. Must follow source order; descriptive only, never severity or authority.
aria-labelledbyroot and each regionid of the region heading—Names each region by its heading so the path is navigable by headings and regions.
data-state.forma-status-lozengeok | attention | blocked | unknownabsentAdds a status symbol to the text status in the primary region.
langroot or regionsBCP 47 taginheritedDeclare the language of localized content so wrapping and pronunciation are correct.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-attention-pathBlock class—Root grid of header, primary region and support grid. In an application page this is often main; nested, use a labelled section.
.forma-attention-path__primaryElement class—The single first-glance region: 2px border, surface background, padding. Its action cluster stacks full width at 30rem and below.
.forma-attention-path__supportElement class—Auto-fit grid of supporting regions (minimum 15rem each), each with a thin top rule.
[data-attention-step]Attribute hook—Presentation hook that prints "Priority N" before any region inside the path.
Keyboard interaction
KeysResult
Tab / Shift+TabMoves through actions in source order, which is also the declared attention order. No added keyboard behavior.

Form behavior

Not a form control.

States

Attention path states
StateHow it is expressedPresentation
Primary.forma-attention-path__primaryStrong frame and background; recognized first.
Declared stepdata-attention-step="N"Visible "Priority N" label before the region.
Supportingchildren of .forma-attention-path__supportThin top rule, auto-fit columns.
Forced colors@media (forced-colors: active)Primary border and supporting rules use CanvasText; the Priority labels and text remain.

Accessibility

Forma provides

  • Keeps the declared path in source order, so visual, reading and focus order agree.
  • Prints the step as visible text, so priority survives grayscale, removed borders and forced colors.
  • Wraps headings, paragraphs, buttons and status text anywhere and stacks actions at narrow widths to avoid overflow at 320px and 200% text.

Your application supplies

  • Choose the primary region from application state, not from what looks most urgent.
  • Keep headings meaningful: the "Priority N" label is CSS-generated content and is not reliably announced by every screen reader, so it cannot replace a heading or a text status.
  • Number steps in source order without gaps and use one primary region per path.
  • State unknown, stale or reconciling conditions as themselves; never strengthen them into failure or success.

Responsive behavior

  • Root and every region set min-inline-size: 0 and max-inline-size: 100%.
  • Support grid: repeat(auto-fit, minmax(min(100%, 15rem), 1fr)), which becomes one column when there is room for less than two 15rem regions.
  • At 30rem and below: the primary region's .forma-cluster becomes a single column of full-width, wrapping buttons.
  • Status lozenges inside the path wrap at 30rem and below instead of forcing width.

Motion

  • No animation: the path is static and nothing moves or pulses to attract attention. Attention comes from structure and text, which is why it survives reduced motion unchanged.

Usage guidance

Do

  • Make the primary region's heading state the required action or decision.
  • Keep supporting regions short and factual.

Avoid

  • Using the attention path to rank severity or authority; step numbers describe reading order only.
  • Declaring more than one primary region, or using CSS order to move the primary region.

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.