Component 32 · Feedback
Alert banner
Communicate a persistent page- or system-level condition.
Overview
Communicate a persistent page- or system-level condition. It converts domain state into an understandable, traceable and accessible interface contract.
When to use
Use HE/Alert banner when you need to communicate a persistent page- or system-level condition. Keep its role distinct from transport freshness, animal-health severity and model confidence.
Example
<div class="he-alert-banner" role="status"><span>i</span><div><b>Archive queued</b><p>Daily telemetry will synchronize when the connection returns.</p></div><button class="he-button he-button--sm he-button--secondary">Review</button></div>Anatomy
1Identity
2Primary value
3State
4Evidence or action
Anatomy stays identical in Pasture and Atlantic. A responsive layout may wrap or stack parts, but reading order and focus order remain equivalent.
Variants and states
Variants
States
Accessibility
Use status for passive updates and alert only for urgent, time-sensitive conditions.
- Maintain a visible keyboard focus indicator and a logical focus sequence.
- Never rely on colour alone for operational, freshness or severity state.
- Keep touch targets at least 44 × 44 px unless the target is an inline text link.
Cross-platform contract
| Surface | Canonical name | Status |
|---|---|---|
| Figma | HE/Alert banner | stable |
| Web | .he-alert-banner | implemented |
| Flutter | HeAlertBanner | implemented |
| Token root | component.alertbanner | generated |