Site and editorial

Steps

<forma-steps>

Numbered method or process using CSS counters on a native ordered list.

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

Purpose

Steps present a short method or procedure as a native ol. Forma removes the default markers and draws a two-digit counter (01, 02, …) in the mono face before each item, with rules between items. Because list styling is removed, the pattern adds role="list" so browsers that drop list semantics for unstyled lists still announce it as a list with its count. Steps are static content: there is no current step or completion state.

Use when

  • Describing how an engagement, method or installation proceeds, in order.
  • Each step is one sentence or a short paragraph.
  • Pairing an install procedure with a Code sample on a product page.

Avoid when

  • Users are moving through a multi-step form and need to see progress: use Wizard or Survey progress.
  • Showing events with dates: use Timeline.
  • The items are ordered destinations with links: use Entry index.

Behavior to know

  • Numbers come from a CSS counter, so they always match item order; they are decorative and assistive technology announces the list position instead.
  • The number column keeps its width while the text wraps beside it.
  • Item text uses the tone's primary text color.

Basic example

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

Canonical

Minimal steps

Rendered from the canonical pattern file.

  1. Understand the domain and its constraints.
  2. Identify recurring symptom patterns.
  3. Trace the causal mechanism.
  4. Deliver treatment and prevention.
HTML · Minimal steps Raw HTML for HTML · Minimal steps
<forma-steps class="forma-component-tag">
<div class="forma-site">
  <ol class="forma-steps" role="list" aria-label="Method">
    <li>Understand the domain and its constraints.</li>
    <li>Identify recurring symptom patterns.</li>
    <li>Trace the causal mechanism.</li>
    <li>Deliver treatment and prevention.</li>
  </ol>
</div>
</forma-steps>

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

Examples

Scenario

Installation procedure with a code sample

A product install section: the steps sit in the primary column of a split and the matching command in the supporting column. Inline code stays legible inside a step.

Install

Three steps to a first report

  1. Add example-quality to the repository's tool manifest.
  2. Run the baseline collection on the main branch.
  3. Publish the report from CI on every pull request.
Collect a baseline
example-quality collect --baseline
HTML · Installation procedure with a code sample Raw HTML for HTML · Installation procedure with a code sample
<forma-steps class="forma-component-tag">
  <div class="forma-site">
    <section class="forma-section" aria-labelledby="steps-install-procedure-title">
      <div class="forma-split">
        <div>
          <p class="forma-eyebrow">Install</p>
          <h3 id="steps-install-procedure-title">Three steps to a first report</h3>
          <ol class="forma-steps" role="list" aria-label="Installation">
            <li>Add <code>example-quality</code> to the repository's tool manifest.</li>
            <li>Run the baseline collection on the main branch.</li>
            <li>Publish the report from CI on every pull request.</li>
          </ol>
        </div>
        <figure class="forma-code-figure">
          <figcaption id="steps-install-procedure-code">Collect a baseline</figcaption>
          <pre class="forma-code" tabindex="0" aria-labelledby="steps-install-procedure-code"><code>example-quality collect --baseline</code></pre>
        </figure>
      </div>
    </section>
  </div>
</forma-steps>

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

Scenario

Ten-step method with long items

A longer method on the surface tone. Numbers keep two digits (01 to 10) so the text column stays aligned, and multi-line items wrap beside their number.

  1. Understand the domain, its constraints and the decisions people make inside it.
  2. Collect the reported symptoms without explaining them yet.
  3. Group symptoms that recur together across teams, releases and environments.
  4. Name candidate mechanisms for each group.
  5. Design observations that would distinguish between the candidates.
  6. Run the observations and record the results.
  7. Eliminate candidates the evidence contradicts.
  8. State the remaining cause and the evidence for it.
  9. Propose treatment and prevention, with the cost of each.
  10. Agree how the treatment will be verified after release.
HTML · Ten-step method with long items Raw HTML for HTML · Ten-step method with long items
<forma-steps class="forma-component-tag">
  <div class="forma-site">
    <div data-forma-tone="surface">
      <ol class="forma-steps" role="list" aria-label="Diagnostic method">
        <li>Understand the domain, its constraints and the decisions people make inside it.</li>
        <li>Collect the reported symptoms without explaining them yet.</li>
        <li>Group symptoms that recur together across teams, releases and environments.</li>
        <li>Name candidate mechanisms for each group.</li>
        <li>Design observations that would distinguish between the candidates.</li>
        <li>Run the observations and record the results.</li>
        <li>Eliminate candidates the evidence contradicts.</li>
        <li>State the remaining cause and the evidence for it.</li>
        <li>Propose treatment and prevention, with the cost of each.</li>
        <li>Agree how the treatment will be verified after release.</li>
      </ol>
    </div>
  </div>
</forma-steps>

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 method

A four-step engagement method at phone width with longer step text.

Viewport width

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

What changes at narrow widths

  • The counter column keeps its minimum width and each item's text wraps beside it, so numbers stay aligned at 320px.
  • Items have no fixed height; text-spacing overrides and 200% text grow the rows instead of clipping them.
  • There are no interactive targets; any links inside a step keep the shell's underline and focus ring.
  • Orientation changes only reflow line breaks.
HTML · Phone method Raw HTML for HTML · Phone method
<forma-steps class="forma-component-tag">
  <div class="forma-site">
    <ol class="forma-steps" role="list" aria-label="Engagement method">
      <li>Understand the domain and its constraints before proposing anything.</li>
      <li>Identify recurring symptom patterns across teams.</li>
      <li>Trace the causal mechanism with evidence.</li>
      <li>Deliver treatment and prevention, then verify both.</li>
    </ol>
  </div>
</forma-steps>

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
roleol.forma-stepslist—Restores list semantics that some browsers drop when list-style is removed.
aria-labelol.forma-stepsstring—Names the procedure when no visible heading introduces it directly.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-stepsBlock class—The ol. Resets the forma-step counter, removes default markers and padding, and draws a top rule; each direct li increments the counter, shows it as a two-digit mono number, and draws a bottom rule.
Keyboard interaction
KeysResult
—Not interactive. Links placed inside a step follow native link behavior.

States

Steps states
StateHow it is expressedPresentation
Defaultno attributesStatic numbered list; there is no current or completed step.
Toneddata-forma-tone on an ancestorText and rules follow the surrounding surface tone.

Accessibility

Forma provides

  • Uses a native ordered list, so position and count are announced.
  • Generates numbers with CSS counters that always match source order.
  • Keeps text at primary contrast on every tone.

Your application supplies

  • Keep role="list" on the ol.
  • Introduce the steps with a heading or aria-label.
  • Do not refer to steps only by their visual number in other text; name the step.

Responsive behavior

  • Each item is a flex row: a fixed-width counter and a wrapping text column. No breakpoints.
  • Items grow with their content; there are no fixed heights.

Motion

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

Usage guidance

Do

  • Start each step with a verb.
  • Keep steps to one action or idea each.

Avoid

  • Typing numbers into the step text; the counter already numbers it.
  • Using steps to show live progress; they have no state.

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.