Where should an alert show up so the user actually notices?

Toasts for the result of an action, a persistent bell feed for what happened while they were away, and a higher tier for urgent alerts.

Toast now, feed for later

A transient toast confirms an action the user just took, then disappears. A persistent feed (the bell with an unread badge) collects what happened while they were away, so a toast fading does not lose anything.

For [event], should I surface it as a transient toast, a persistent entry in the notification feed, or both, given whether the user triggered it and whether they need to find it again later?

Not every alert is equal

A routine update can sit quietly in the feed. An urgent alert (a payment failed, a deadline is now) needs to interrupt: stronger styling, maybe sound, and an assertive screen reader announcement instead of a polite one.

Is [notification] routine or urgent for the user, and how should that change its placement, its visual weight, and its ARIA live region politeness (polite versus assertive)?

Toasts confirm what the user just did, the bell feed holds what they missed, and only genuinely urgent alerts get to interrupt.

Additional Resources

Explore these carefully curated resources to deepen your understanding and practice the concepts covered in this lesson.

MDN ARIA live regions

Documentation

How to announce dynamic updates to screen reader users without moving focus.

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions

PreviousNext