VERIFICATION-0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF
Ready to close September · Extended localized content for verification and layout resilience
- All invoices posted
- Payments allocated
- Bank reconciliation
- CPA adjustment reviewBlocking
<forma-readiness-checklist>
Explicit complete, incomplete and blocking prerequisites shown before a consequential transition.
<forma-readiness-checklist>patterns/readiness-checklist.htmlA readiness checklist shows the prerequisites for a consequential step, such as closing a period, publishing a release or submitting an application, and the state of each. Forma renders a bordered section with a header (a Status lozenge summary and a heading) and a list of items, each with a glyph, a label and an optional trailing action or state word. The application or Ordo decides what the prerequisites are, whether each is met, and whether the transition is allowed; Forma does not calculate readiness.
The smallest correct markup: the canonical pattern from patterns/readiness-checklist.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.
<forma-readiness-checklist class="forma-component-tag">
<section class="forma-readiness-checklist" aria-labelledby="readiness-title">
<header>
<span class="forma-status-lozenge" data-state="attention">5 of 7 complete</span>
<h3 id="readiness-title">Ready to close September</h3>
</header>
<ul class="forma-readiness-checklist__items">
<li data-state="complete"><span aria-hidden="true">✓</span><span>All invoices posted</span></li>
<li data-state="complete"><span aria-hidden="true">✓</span><span>Payments allocated</span></li>
<li data-state="incomplete"><span aria-hidden="true">○</span><span>Bank reconciliation</span><button type="button">Review</button></li>
<li data-state="blocked"><span aria-hidden="true">!</span><span>CPA adjustment review</span><span>Blocking</span></li>
</ul>
</section>
</forma-readiness-checklist>
Click or tap the code once to select all of it, then copy.
Every item is complete. The header lozenge switches to the ok glyph and the transition button is available below the list, supplied by the application.
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-readiness-checklist class="forma-component-tag">
<section class="forma-readiness-checklist" aria-labelledby="readiness-checklist-ready-to-publish-title">
<header>
<span class="forma-status-lozenge" data-state="ok">3 of 3 complete</span>
<h3 id="readiness-checklist-ready-to-publish-title">Ready to publish release 4.2</h3>
</header>
<ul class="forma-readiness-checklist__items">
<li data-state="complete"><span aria-hidden="true">✓</span><span>Release notes approved</span><span class="forma-visually-hidden">Complete</span></li>
<li data-state="complete"><span aria-hidden="true">✓</span><span>Migration tested on staging</span><span class="forma-visually-hidden">Complete</span></li>
<li data-state="complete"><span aria-hidden="true">✓</span><span>Rollback plan recorded</span><span class="forma-visually-hidden">Complete</span></li>
</ul>
</section>
<button type="button">Publish release</button>
</forma-readiness-checklist>
Click or tap the code once to select all of it, then copy.
A grant application with two blocking prerequisites and one incomplete item. Blocking items say "Blocking" in text and link to where they are resolved; the header counts what is complete.
Live demo. 1 native action works here and is verified by an outcome test.
<forma-readiness-checklist class="forma-component-tag">
<section class="forma-readiness-checklist" aria-labelledby="readiness-checklist-blocked-submission-title">
<header>
<span class="forma-status-lozenge" data-state="blocked">1 of 4 complete, 2 blocking</span>
<h3 id="readiness-checklist-blocked-submission-title">Before you submit the grant application</h3>
</header>
<ul class="forma-readiness-checklist__items">
<li data-state="complete"><span aria-hidden="true">✓</span><span>Budget totals match the narrative</span><span class="forma-visually-hidden">Complete</span></li>
<li data-state="blocked"><span aria-hidden="true">!</span><span>Signed letter of support from the partner institution</span><span>Blocking</span></li>
<li data-state="blocked"><span aria-hidden="true">!</span><span>Principal investigator's conflict-of-interest form</span><span>Blocking</span></li>
<li data-state="incomplete"><span aria-hidden="true">○</span><span>Optional data-sharing plan</span><a href="#readiness-checklist-blocked-submission-title">Add</a></li>
</ul>
</section>
</forma-readiness-checklist>
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.
The canonical close checklist at phone width with an action on an incomplete item.
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-readiness-checklist class="forma-component-tag">
<section class="forma-readiness-checklist" aria-labelledby="readiness-checklist-mobile-month-close-title">
<header>
<span class="forma-status-lozenge" data-state="attention">2 of 4 complete</span>
<h3 id="readiness-checklist-mobile-month-close-title">Close September books</h3>
</header>
<ul class="forma-readiness-checklist__items">
<li data-state="complete"><span aria-hidden="true">✓</span><span>All invoices posted</span><span class="forma-visually-hidden">Complete</span></li>
<li data-state="complete"><span aria-hidden="true">✓</span><span>Payments allocated</span><span class="forma-visually-hidden">Complete</span></li>
<li data-state="incomplete"><span aria-hidden="true">○</span><span>Reconcile the operating account at First National</span><button type="button">Review</button></li>
<li data-state="blocked"><span aria-hidden="true">!</span><span>External accountant adjustment review</span><span>Blocking</span></li>
</ul>
</section>
</forma-readiness-checklist>
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-readiness-checklist | id of the header heading | — | Names the checklist from its heading. |
data-state | li | complete | incomplete | blocked | — | Item state supplied by the application. complete bolds the glyph; blocked adds a thick inline-start border. incomplete has no special styling. |
aria-hidden | glyph span | true | — | Hides the ✓ / ○ / ! glyph; state must also be available as text. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-readiness-checklist | Block class | — | Root section with a functional border. Its direct header child is padded and separated by a rule. |
.forma-readiness-checklist__items | Element class | — | Unstyled list. Each li is a grid of a 2rem glyph column, a flexible label column and an auto column for an action or state word. |
[data-state] | Attribute hook | — | On each li: complete makes the first child (glyph) bold; blocked adds a 0.35rem accent inline-start border. |
| Keys | Result |
|---|---|
| Tab / Shift+Tab | Moves through item actions (buttons or links). Items themselves are not focusable. |
| Enter / Space | Activates the focused action (native behavior; Space applies to buttons only). |
| Event | Description |
|---|---|
click | Native click on item actions. The application navigates or performs the work. |
Not a form control; the checklist does not submit anything. The transition itself is a separate application button.
| State | How it is expressed | Presentation |
|---|---|---|
| Complete | li data-state="complete" | ✓ glyph in bold. Provide a text equivalent such as visually hidden "Complete". |
| Incomplete | li data-state="incomplete" | ○ glyph and usually an action to resolve it. |
| Blocking | li data-state="blocked" | ! glyph, a visible "Blocking" word and a thick inline-start border. |
2rem minmax(0, 1fr) auto grid at every width; the label column wraps.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.