VERIFICATION-0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF
Review details · Extended localized content for verification and layout resilience
- 1Details
- 2Review
- 3Validate
- 4Publish
Confirm the supplied information before continuing.
<forma-wizard>
Step-by-step workflow shell with current-step state, progress, validation hooks, resume, and mobile reduction.
<forma-wizard>patterns/wizard.htmlThe wizard is a bordered shell for a task split into ordered steps: a header with the step position, title and a native progress bar; a step rail marking complete and current steps; a body for the current step's fields; and a footer of actions. Forma renders whatever state it is given. Limen and Ordo own the workflow: which steps exist (including branching), whether the user may advance, validation before advance, save and exit, resume, and whether earlier steps can be revisited. On phones the rail reduces to the current step only.
data-state="complete" and data-state="current" plus aria-current="step" on the current item.The smallest correct markup: the canonical pattern from patterns/wizard.html inside its public tag. Copy this first, then adapt labels, names and state.
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.
Confirm the supplied information before continuing.
<forma-wizard class="forma-component-tag">
<section class="forma-wizard" aria-labelledby="wizard-title">
<header class="forma-wizard__header">
<div><span class="forma-wizard__position">Step 2 of 4</span><h3 id="wizard-title">Review details</h3></div>
<progress value="2" max="4" aria-label="Workflow progress">2 of 4</progress>
</header>
<ol class="forma-wizard__steps" aria-label="Workflow steps">
<li data-state="complete"><span>1</span>Details</li>
<li data-state="current" aria-current="step"><span>2</span>Review</li>
<li><span>3</span>Validate</li>
<li><span>4</span>Publish</li>
</ol>
<div class="forma-wizard__body">
<p>Confirm the supplied information before continuing.</p>
</div>
<footer class="forma-wizard__actions">
<button type="button">Back</button>
<button type="button">Continue</button>
</footer>
</section>
</forma-wizard>
Click or tap the code once to select all of it, then copy.
The user pressed Continue on step 1 with a missing field. Ordo refused the transition; the application rendered a focusable validation summary in the body and marked the field invalid. The rail and position are unchanged.
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.
<forma-wizard class="forma-component-tag">
<section class="forma-wizard" aria-labelledby="wizard-blocked-title">
<header class="forma-wizard__header">
<div><span class="forma-wizard__position">Step 1 of 4</span><h3 id="wizard-blocked-title">Service details</h3></div>
<progress value="1" max="4" aria-label="Workflow progress">1 of 4</progress>
</header>
<ol class="forma-wizard__steps" aria-label="Workflow steps">
<li data-state="current" aria-current="step"><span>1</span>Details</li>
<li><span>2</span>Review</li>
<li><span>3</span>Validate</li>
<li><span>4</span>Publish</li>
</ol>
<div class="forma-wizard__body">
<div class="forma-validation-summary" role="alert" tabindex="-1" aria-labelledby="wizard-blocked-summary-title">
<div class="forma-validation-summary__icon" aria-hidden="true">!</div>
<div>
<h4 class="forma-validation-summary__title" id="wizard-blocked-summary-title">Fix 1 problem to continue</h4>
<ul class="forma-validation-summary__list"><li><a href="#wizard-blocked-owner">Enter an owning team.</a></li></ul>
</div>
</div>
<div class="forma-field">
<label class="forma-field__label" for="wizard-blocked-owner">Owning team</label>
<input id="wizard-blocked-owner" name="wizard-blocked-owner" type="text" required aria-invalid="true">
</div>
</div>
<footer class="forma-wizard__actions">
<button type="button">Save and exit</button>
<button type="button">Continue</button>
</footer>
</section>
</forma-wizard>
Click or tap the code once to select all of it, then copy.
A draft resumed from a saved session. Three steps are complete and Publish is current; the footer offers Back, Save and exit, and the final action.
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.
Resumed from your draft saved yesterday at 17:42. All checks passed. Publishing makes release 2.8 available to every customer.
<forma-wizard class="forma-component-tag">
<section class="forma-wizard" aria-labelledby="wizard-resume-title">
<header class="forma-wizard__header">
<div><span class="forma-wizard__position">Step 4 of 4</span><h3 id="wizard-resume-title">Publish release 2.8</h3></div>
<progress value="4" max="4" aria-label="Workflow progress">4 of 4</progress>
</header>
<ol class="forma-wizard__steps" aria-label="Workflow steps">
<li data-state="complete"><span>1</span>Details</li>
<li data-state="complete"><span>2</span>Review</li>
<li data-state="complete"><span>3</span>Validate</li>
<li data-state="current" aria-current="step"><span>4</span>Publish</li>
</ol>
<div class="forma-wizard__body">
<p>Resumed from your draft saved yesterday at 17:42. All checks passed. Publishing makes release 2.8 available to every customer.</p>
</div>
<footer class="forma-wizard__actions">
<button type="button">Back</button>
<button type="button">Save and exit</button>
<button type="button">Publish release</button>
</footer>
</section>
</forma-wizard>
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.
Below 40rem the header stacks, the rail shows only the current step with a Current step note, and actions wrap if they do not fit.
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.
<forma-wizard class="forma-component-tag">
<section class="forma-wizard" aria-labelledby="wizard-mobile-title">
<header class="forma-wizard__header">
<div><span class="forma-wizard__position">Step 3 of 4</span><h3 id="wizard-mobile-title">Validate configuration</h3></div>
<progress value="3" max="4" aria-label="Workflow progress">3 of 4</progress>
</header>
<ol class="forma-wizard__steps" aria-label="Workflow steps">
<li data-state="complete"><span>1</span>Details</li>
<li data-state="complete"><span>2</span>Review</li>
<li data-state="current" aria-current="step"><span>3</span>Validate</li>
<li><span>4</span>Publish</li>
</ol>
<div class="forma-wizard__body">
<p>Checking 14 settings against the production policy.</p>
</div>
<footer class="forma-wizard__actions">
<button type="button">Back</button>
<button type="button">Continue</button>
</footer>
</section>
</forma-wizard>
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.
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.
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 |
|---|---|---|---|---|
aria-labelledby | section.forma-wizard | id of the step heading | — | Names the wizard region by the current step title. |
value | progress | number | — | Current step number, supplied by the application. |
max | progress | number | — | Total number of steps; update it when branching changes the total. |
aria-label | progress and ol.forma-wizard__steps | string | — | Names the progress bar (Workflow progress) and the step list (Workflow steps). |
data-state | step li | complete | current | absent (upcoming) | Visual step state written by the application. current also bolds the step and inverts its marker; complete adds a check glyph. |
aria-current | current step li | step | absent | Programmatic current step. Always pair it with data-state="current". |
type | action buttons | button (or submit) | — | Use type="button" when the application handles the transition; type="submit" when the step is a native form submission. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-wizard | Block class | — | Bordered root section. |
.forma-wizard__actions | Element class | — | Footer flex row with actions at opposite ends; wraps when needed. |
.forma-wizard__body | Element class | — | Padded region for the current step's content. |
.forma-wizard__header | Element class | — | Grid of position/title and a progress column (at least 10rem); stacks below 40rem. |
.forma-wizard__position | Element class | — | Small monospace "Step n of m" text. |
.forma-wizard__steps | Element class | — | Four-column step rail with a bottom rule. Each item has a circular number marker. Below 40rem only the current item is shown. |
[data-state] | Attribute hook | — | On step items: current or complete. Presentation only; the workflow state lives in Limen/Ordo. |
| Keys | Result |
|---|---|
| Tab / Shift+Tab | Moves through the step body's fields and then the footer actions. The step rail is not interactive. |
| Enter / Space | Activates the focused action button (native). |
| Event | Description |
|---|---|
click / submit | Native events from the action buttons. Limen asks Ordo whether the transition is legal, then renders the next state. |
The wizard is not a form itself. Wrap the body and actions in a form when steps submit natively; each step's fields validate as ordinary form controls.
| State | How it is expressed | Presentation |
|---|---|---|
| Upcoming step | li without data-state | Secondary text and an outlined marker. |
| Current step | data-state="current" + aria-current="step" | Primary bold text and an inverse marker; the only step shown below 40rem, with a Current step note. |
| Complete step | data-state="complete" | A check glyph is generated on the marker. |
| Blocked | application renders a validation summary and aria-invalid fields | Position and rail stay on the current step; Forma adds no rail error state. |
| Resumed | application renders saved state | Identical to any other state; resume messaging is body content. |
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.