A fault summary lists several unresolved Aegis faults in one programmatically focusable region: a count, a title, and one entry per already-grouped fault with its severity text, reference, occurrence count and, where relevant, a link to the affected region. Forma does not fingerprint, deduplicate or decide that two faults share a cause; Aegis lifecycle logic and the application supply the grouped entries and counts. After a failed submit or similar action the application can move focus to the summary so keyboard and screen-reader users land on one clear starting point.
Use when
A consequential action produced more than one unresolved fault and the user needs one place to start.
Repeated faults have been grouped upstream and should appear once with an occurrence count.
Each fault relates to a region on the page that the user can jump to.
Avoid when
There is only one fault and it belongs to a visible region: use Fault inline there.
The condition affects the whole application: use Fault banner.
You would need Forma to collapse duplicates or compute counts; that logic stays in Aegis or the application.
Behavior to know
tabindex="-1" makes the region focusable by script without adding a tab stop.
Each entry shows severity as text in its metadata line; Critical entries are also bold.
Entries are an ordered list, so the order the application supplies (for example by severity or page position) is announced.
No live region by default: announcements happen through focus, not repeated assertive updates.
Basic example
The smallest correct markup: the canonical pattern from patterns/fault-summary.html inside its public tag. Copy this first, then adapt labels, names and state.
Canonical
Minimal fault 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.
!
2 unresolved faults
Some work needs your attention
Repeated occurrences are grouped by the application before rendering.
<forma-fault-summary class="forma-component-tag">
<section class="forma-fault-summary" tabindex="-1" aria-labelledby="fault-summary-title">
<div class="forma-fault-summary__heading">
<div class="forma-fault-summary__marker" aria-hidden="true">!</div>
<div>
<p class="forma-fault__severity">2 unresolved faults</p>
<h2 id="fault-summary-title">Some work needs your attention</h2>
<p>Repeated occurrences are grouped by the application before rendering.</p>
</div>
</div>
<ol class="forma-fault-summary__list">
<li data-forma-severity="error">
<a href="#customer-name">Customer name could not be saved</a>
<span class="forma-fault-summary__meta">Error · AG-4F82C · occurred 3 times</span>
</li>
<li data-forma-severity="warning">
<a href="#sync-status">Synchronization is waiting for GitHub</a>
<span class="forma-fault-summary__meta">Warning · AG-91B7Q</span>
</li>
</ol>
</section>
</forma-fault-summary>
Click or tap the code once to select all of it, then copy.
Examples
Scenario
After a failed submit
A summary above a short form after submission failed. Each link targets the affected field in the same page; the critical entry is bold as well as labelled Critical. The application focuses the summary once after the failed submit.
Live demo. 3 native actions work here and are verified by an outcome test.
Click or tap the code once to select all of it, then copy.
Scenario
One grouped fault with many occurrences
Aegis grouped fourteen identical failures into one entry. The summary shows the count supplied upstream; Forma does not compute it. The entry has no affected region, so it is plain text instead of a link.
!
1 unresolved fault
Nightly export needs attention
Repeated occurrences are grouped by the application before rendering.
Export to the reporting warehouse timed outError · AG-2RT9M · occurred 14 times since 02:00 UTC
<forma-fault-summary class="forma-component-tag">
<section class="forma-fault-summary" tabindex="-1" aria-labelledby="fault-summary-grouped-repeats-title">
<div class="forma-fault-summary__heading">
<div class="forma-fault-summary__marker" aria-hidden="true">!</div>
<div>
<p class="forma-fault__severity">1 unresolved fault</p>
<h2 id="fault-summary-grouped-repeats-title">Nightly export needs attention</h2>
<p>Repeated occurrences are grouped by the application before rendering.</p>
</div>
</div>
<ol class="forma-fault-summary__list">
<li data-forma-severity="error">
<strong>Export to the reporting warehouse timed out</strong>
<span class="forma-fault-summary__meta">Error · AG-2RT9M · occurred 14 times since 02:00 UTC</span>
</li>
</ol>
</section>
</forma-fault-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
Fault summary on a phone
A summary with long entry titles and references at phone width.
Live demo. 2 native actions work here and are verified by an outcome test.
Frames narrower than the selected width show the component at the width available.
What changes at narrow widths
The summary is a single-column grid at every width; the marker and heading stay side by side and the heading text wraps.
Entry links wrap onto several lines and the monospace metadata line breaks anywhere, so long references never cause horizontal scrolling.
Links keep their full text as the touch target; leave vertical space between entries (the list uses a 0.65rem gap) rather than shrinking text.
Orientation changes only reflow text; list order and numbering stay the same.
<forma-fault-summary class="forma-component-tag">
<section class="forma-fault-summary" tabindex="-1" aria-labelledby="fault-summary-mobile-summary-title">
<div class="forma-fault-summary__heading">
<div class="forma-fault-summary__marker" aria-hidden="true">!</div>
<div>
<p class="forma-fault__severity">2 unresolved faults</p>
<h2 id="fault-summary-mobile-summary-title">Some changes were not saved</h2>
</div>
</div>
<ol class="forma-fault-summary__list">
<li data-forma-severity="error">
<a href="#fault-summary-mobile-summary-title">Delivery instructions for the north warehouse loading dock could not be saved</a>
<span class="forma-fault-summary__meta">Error · AG-4F82C-DELIVERY-NORTH · occurred 3 times</span>
</li>
<li data-forma-severity="warning">
<a href="#fault-summary-mobile-summary-title">Synchronization is waiting for the carrier service</a>
<span class="forma-fault-summary__meta">Warning · AG-91B7Q</span>
</li>
</ol>
</section>
</forma-fault-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.
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
Attribute
On
Values
Default
Description
tabindex
section.forma-fault-summary
-1
—
Required. Lets the application move focus to the summary after a failed operation without adding a tab stop.
aria-labelledby
section.forma-fault-summary
id of the heading
—
Names the region so focus lands on a named landmark.
data-forma-severity
li
diagnostic | warning | error | critical
—
Records each entry's Aegis severity. critical makes the entry bold; the severity must also be written in the metadata line.
href
a
#id of the affected region
—
Links an entry to the field or region it concerns. Omit the link when there is no affected region.
aria-hidden
.forma-fault-summary__marker
true
—
Hides the decorative marker glyph.
CSS hooks (derived from dist/all.css)
Hook
Kind
Values or default
Description
.forma-fault-summary
Block class
—
Root section: a bordered grid with a strong 3px focus-visible outline and ring so programmatic focus is visible.
.forma-fault-summary__heading
Element class
—
Two-column grid placing the marker beside the count, heading and optional note.
.forma-fault-summary__list
Element class
—
Ordered list of grouped entries with a 0.65rem gap and visible numbering.
.forma-fault-summary__marker
Element class
—
Decorative round marker glyph.
.forma-fault-summary__meta
Element class
—
Monospace metadata line for severity, reference and occurrence count; breaks anywhere.
Keyboard interaction
Keys
Result
Tab / Shift+Tab
Moves between entry links. The summary itself is not in the tab order (tabindex=-1).
Enter
Follows the focused link to the affected region (native link behavior). The target should be focusable or a form control so focus moves with it.
Events
Event
Description
—
No Forma events. The application calls focus() on the summary after a failed submit; links use native navigation.
Form behavior
Not a form control. It can sit above a form and link to its fields.
States
Fault summary states
State
How it is expressed
Presentation
Unfocused
default
A bordered region listing the grouped faults.
Focused
:focus-visible after application focus()
3px outline with an outer focus ring; the region is announced by its name.
Critical entry
li data-forma-severity="critical" plus text
Entry text is bold in addition to the Critical label.
Grouped entry
occurrence text supplied by the application
The meta line states how many times the grouped fault occurred.
Accessibility
Forma provides
Provides a strong visible focus indicator for the region when it receives focus.
Writes severity as text in every entry and uses bold weight for Critical as a non-color cue.
Keeps the marker decorative and the list semantic, so entries are counted and ordered for assistive technology.
Keeps borders, marker and metadata text visible in forced-colors mode.
Your application supplies
Supply already-grouped entries and occurrence counts from Aegis; never deduplicate in markup.
Focus the summary once after a failed consequential action; do not add an assertive live region that repeats on every render.
Make link targets focusable (form controls, or elements with tabindex="-1") so focus follows navigation.
Update or remove entries as Aegis reports faults resolved, reopened or superseded.
Responsive behavior
A single-column grid at every width; the heading row keeps the marker in an intrinsic-width column.
Entry links and headings wrap; metadata uses overflow-wrap: anywhere so long references fit at 320px.
There are no breakpoints; the list numbering uses a 1.4rem inline-start padding that remains readable on phones.
Motion
No animation: the summary appears with the application's render and focus moves to it immediately.
Only native link and focus styling change state; nothing slides, fades or pulses.
Usage guidance
Do
State the count in the first line so users know how much work there is.
Order entries meaningfully, for example by severity or by position on the page.
Keep the reference in each entry so support can match it.
Avoid
Listing the same fault several times instead of an occurrence count.
Using role="alert" and re-rendering, which repeats the announcement.
Linking to regions that no longer exist after the fault resolves.