Data display

Path summary

<forma-path-summary>

Provides an ordered textual representation of a selected relationship or evidence path.

Authoring tag
<forma-path-summary>
Category
Data display
Behavior owner
Application content
Canonical source
patterns/path-summary.html

Purpose

A path summary spells out one selected route through a set of related entities as a numbered list: each step is an entity (usually a link) followed by the relationship that leads to the next one. It is the text form of a highlighted path in a Diagram, dependency graph or evidence chain, so the route can be read, linked and announced without seeing the drawing. Forma provides the numbered layout; the path, its wording and its current step are application data.

Use when

  • A user has selected or been shown a route between two entities, such as how data flows from source to report.
  • An evidence path must be read in order, from claim to source or source to claim.
  • A spatial highlight needs an accessible, ordered equivalent.

Avoid when

Behavior to know

  • Section grid with a header (title and a count) and an ordered list with visible numbers.
  • Each step shows the entity on one line and the relationship phrase on the next (span is block).
  • Steps are spaced 0.5rem apart with a 1.5rem numbering gutter.
  • aria-current="step" can mark the selected or final step; Forma adds no visual styling for it.

Basic example

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

Canonical

Minimal path summary

Rendered from the canonical pattern file.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

Selected path

3 relationships

  1. Chronaprovides time entries to
  2. Billingcreates billable charges for
  3. Summarecords the invoice
HTML · Minimal path summary Raw HTML for HTML · Minimal path summary
<forma-path-summary class="forma-component-tag">
<section class="forma-path-summary" aria-labelledby="path-title">
  <header><h2 id="path-title">Selected path</h2><p>3 relationships</p></header>
  <ol class="forma-path-summary__steps">
    <li><a href="#chrona">Chrona</a><span>provides time entries to</span></li>
    <li><a href="#billing">Billing</a><span>creates billable charges for</span></li>
    <li aria-current="step"><a href="#summa">Summa</a><span>records the invoice</span></li>
  </ol>
</section>
</forma-path-summary>

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

Examples

Scenario

Evidence path from claim to source

How a readiness claim traces back to raw test output. Each relationship phrase is written to read naturally into the next step, and the final step is the source.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

Evidence path for “Release is ready”

4 steps, claim to source

  1. Release readiness claimis supported by
  2. Quality gate QG-17which evaluated
  3. CI run 1187which produced
  4. Test report artifactthe original source
HTML · Evidence path from claim to source Raw HTML for HTML · Evidence path from claim to source
<forma-path-summary class="forma-component-tag">
  <section class="forma-path-summary" aria-labelledby="path-summary-evidence-path-title">
    <header><h2 id="path-summary-evidence-path-title">Evidence path for “Release is ready”</h2><p>4 steps, claim to source</p></header>
    <ol class="forma-path-summary__steps">
      <li><a href="#path-summary-evidence-path-claim">Release readiness claim</a><span>is supported by</span></li>
      <li><a href="#path-summary-evidence-path-gate">Quality gate QG-17</a><span>which evaluated</span></li>
      <li><a href="#path-summary-evidence-path-run">CI run 1187</a><span>which produced</span></li>
      <li aria-current="step"><a href="#path-summary-evidence-path-log">Test report artifact</a><span>the original source</span></li>
    </ol>
  </section>
</forma-path-summary>

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

Scenario

Path with an unknown link

The route from an order to its shipment has a gap: the relationship between the warehouse pick and the carrier handoff was not recorded. The step still appears, stating Unknown, so the path does not look continuous when it is not.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

Order ORD-5521 to delivery

3 known relationships, 1 unknown

  1. Order ORD-5521was allocated to
  2. Pick list PL-880unknown relationship to the next step: handoff not recorded
  3. Carrier consignment NL-44102was delivered as
  4. Proof of deliverysigned 28 Sep 2026
HTML · Path with an unknown link Raw HTML for HTML · Path with an unknown link
<forma-path-summary class="forma-component-tag">
  <section class="forma-path-summary" aria-labelledby="path-summary-broken-path-title">
    <header><h2 id="path-summary-broken-path-title">Order ORD-5521 to delivery</h2><p>3 known relationships, 1 unknown</p></header>
    <ol class="forma-path-summary__steps">
      <li><a href="#path-summary-broken-path-order">Order ORD-5521</a><span>was allocated to</span></li>
      <li><a href="#path-summary-broken-path-pick">Pick list PL-880</a><span>unknown relationship to the next step: handoff not recorded</span></li>
      <li><a href="#path-summary-broken-path-carrier">Carrier consignment NL-44102</a><span>was delivered as</span></li>
      <li aria-current="step"><a href="#path-summary-broken-path-pod">Proof of delivery</a><span>signed 28 Sep 2026</span></li>
    </ol>
  </section>
</forma-path-summary>

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 data flow path

A three-step data flow at phone width. Entity and relationship text wrap within each numbered step.

Static specimen. Its links point to placeholder destinations that do not exist on this site. 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

  • No breakpoints: the numbered list keeps its 1.5rem gutter and every step wraps within the remaining width.
  • Entity links and relationship phrases are on separate lines, so long names do not run into the relationship text at 320px.
  • Links are ordinary inline links; keep entity names as link text so each is a clear tap target.
  • Orientation changes only affect line wrapping.
HTML · Mobile data flow path Raw HTML for HTML · Mobile data flow path
<forma-path-summary class="forma-component-tag">
  <section class="forma-path-summary" aria-labelledby="path-summary-mobile-path-title">
    <header><h2 id="path-summary-mobile-path-title">Selected path</h2><p>3 relationships</p></header>
    <ol class="forma-path-summary__steps">
      <li><a href="#path-summary-mobile-path-chrona">Chrona time tracking</a><span>provides time entries to</span></li>
      <li><a href="#path-summary-mobile-path-billing">Billing</a><span>creates billable charges for</span></li>
      <li aria-current="step"><a href="#path-summary-mobile-path-summa">Summa general ledger</a><span>records the invoice</span></li>
    </ol>
  </section>
</forma-path-summary>

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 links point to placeholder destinations that do not exist on this site. 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
aria-labelledbysection.forma-path-summaryid of the header heading—Names the path.
aria-currentlistepabsentOptionally marks the selected or final step for assistive technology. Not styled by Forma.
hrefaURL or fragment—Links each entity to its view or node.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-path-summaryBlock class—Root section; a grid with 0.75rem gaps. Removes the trailing margin of the header's last child.
.forma-path-summary__stepsElement class—The numbered ol: 0.5rem gaps, 1.5rem inline-start gutter; each li has a small inline-start padding and its span is displayed as a block below the entity.
Keyboard interaction
KeysResult
TabMoves through the entity links in path order.
EnterFollows the focused link (native).

Form behavior

Not a form control.

States

Path summary states
StateHow it is expressedPresentation
Stepli in .forma-path-summary__stepsEntity plus relationship to the next step.
Current or final steparia-current="step"Exposed to assistive technology; no visual change from Forma.
Unknown linkapplication text in the step's spanStated in words so gaps are visible.

Accessibility

Forma provides

  • Uses an ordered list with visible numbers, so sequence is conveyed both visually and programmatically.
  • Keeps entity and relationship text as real text in reading order.

Your application supplies

  • Write relationship phrases so the path reads as sentences from step to step.
  • State the direction of the path in the header (claim to source, source to report).
  • Include unknown or unverified links explicitly.
  • If aria-current should also be visible, add visible text such as "(selected)".

Responsive behavior

  • No breakpoints; steps wrap within the container from 320px up.
  • The numbering gutter is fixed at 1.5rem.

Motion

  • No animation: the summary is static and replaced by the application when the selected path changes.

Usage guidance

Do

  • Keep the path in the same order as the highlighted route in any accompanying diagram.
  • Show the number of steps or relationships in the header.

Avoid

  • Arrows or connector glyphs as the only statement of relationship.
  • Omitting steps to shorten the path.

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.