# Banner and Alert

Banners present persistent page- or service-level messages, while alerts announce important time-sensitive information without requiring users to find it first.

- Type: framework
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-06
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/banner-and-alert/>)

## What it means

A banner is a prominent, usually persistent message region placed in relation to a page, section, or whole service. An alert is a semantic status message important enough to be announced when it appears. A visual banner is not automatically an alert, and routine information should not receive interruptive alert semantics.

## Why it matters

Persistent messaging can communicate outages, deadlines, policy changes, or outcomes that transient feedback cannot safely carry. Correct urgency and announcement behavior help people notice the message without creating repeated, disruptive output.

## When to use it

Use a banner for important information that should remain available while users continue their task, and alert semantics for dynamically appearing information that warrants immediate announcement. Use inline errors for field problems, a toast for low-risk confirmation, and a dialog for a required decision.

## How it works

1. Classify the message by scope, urgency, persistence, and required response.
2. Place it consistently near the affected content or at the start of the relevant page area.
3. State what happened, who or what is affected, and the next action when one exists.
4. Choose region, status, or alert semantics that match the urgency without moving focus unnecessarily.
5. Define dismissal and recurrence rules, then test repeated updates, screen-reader output, zoom, and color independence.

## A practical example

An invoicing service shows a persistent banner above the page heading when bank transfers are delayed. It names the affected payment method, expected review time, and status link. Because it is present on page load and does not require immediate action, it uses a labeled region rather than an assertive alert.

## Where it breaks

Users can develop banner blindness, especially when several messages compete. Alerts do not guarantee attention, persistent banners consume space, and dismissing a message may be unsafe when its underlying condition still applies.

## Common mistakes

- Giving every informational banner an assertive alert role.
- Using a banner instead of placing task-critical instructions in the main content.
- Showing several banners with unclear priority.
- Communicating severity only through color or an unexplained icon.

## Sources

1. [Notification banner](<https://design-system.service.gov.uk/components/notification-banner/>) — GOV.UK Design System · Institutional design system
2. [Alert Pattern](<https://www.w3.org/WAI/ARIA/apg/patterns/alert/>) — W3C Web Accessibility Initiative · Technical guidance

## Related topics

- [Toast and Snackbar](<https://wiki.soroush.uk/topic/toast-and-snackbar/>)
- [Form Validation](<https://wiki.soroush.uk/topic/form-validation/>)
- [Modal Dialog](<https://wiki.soroush.uk/topic/modal-dialog/>)
