Interface Core B · Official guidance Platform: Web

Alert

An alert is a short, important message that is announced without moving keyboard focus. It does not ask the user to answer at once.

Try an example
You might call it Alert

Try an example

A real example

A background save fails while the user keeps typing in an editor. An alert says the changes were not saved and shows how to recover. If the user must stop and choose an answer, use an alert dialog instead.

Main parts

  1. 01important message
  2. 02live announcement
  3. 03recovery path

Use it when

Use this term for important, time-sensitive status that should be announced without taking focus away.

Do not use it when

Do not use alerts for normal updates, old messages, or content already on the page when it loads.

Name used in code

role=alert / aria-live=assertive

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Alert to solve this user need without losing the current context. User context: A background save fails while the user keeps typing in an editor. An alert says the changes were not saved and shows how to recover. If the user must stop and choose an answer, use an alert dialog instead. Recommended pattern: Alert. Why it fits: Use this term for important, time-sensitive status that should be announced without taking focus away. Do not use it when: Do not use alerts for normal updates, old messages, or content already on the page when it loads. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Alert. Definition: An alert is a short, important message that is announced without moving keyboard focus. It does not ask the user to answer at once. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

B
How official is this term?

Official guidance

The named platform, framework, project, or expert group has an official guide for this term.

It is official for that source. Other platforms or teams may use the term in another way.

Scope
Non-normative WAI-ARIA Authoring Practices pattern
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · W3C WAI · stable Alert Pattern Scope: Non-normative accessible alert guidance Role here: Direct term reference Source covers: canonical name, definition, interaction, keyboard behavior, accessibility

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.