VERIFICATION-0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF
- Understand the domain and its constraints.
- Identify recurring symptom patterns.
- Trace the causal mechanism.
- Deliver treatment and prevention.
<forma-steps>
Numbered method or process using CSS counters on a native ordered list.
<forma-steps>patterns/steps.htmlSteps 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.
The smallest correct markup: the canonical pattern from patterns/steps.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
<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.
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
example-quality to the repository's tool manifest.example-quality collect --baseline
<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.
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.
<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.
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.
A four-step engagement method at phone width with longer step text.
<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.
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 |
|---|---|---|---|---|
role | ol.forma-steps | list | — | Restores list semantics that some browsers drop when list-style is removed. |
aria-label | ol.forma-steps | string | — | Names the procedure when no visible heading introduces it directly. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-steps | Block 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. |
| Keys | Result |
|---|---|
| — | Not interactive. Links placed inside a step follow native link behavior. |
| State | How it is expressed | Presentation |
|---|---|---|
| Default | no attributes | Static numbered list; there is no current or completed step. |
| Toned | data-forma-tone on an ancestor | Text and rules follow the surrounding surface tone. |
role="list" on the ol.aria-label.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.