Rôles status, alert et log

Some ARIA roles turn an element into a live region for you, setting a sensible politeness level automatically so you write less markup.

The status role marks a region that updates politely. It is perfect for low-key confirmations like a saved or copied message. 📋

Using role status is shorthand for aria-live set to polite. You get the same behavior with clearer, more semantic intent.

The alert role announces assertively the instant its content appears. Reach for it when something needs attention right now. ⚠️

An alert behaves like aria-live assertive plus aria-atomic true. It interrupts and reads its whole text as one message.

The log role suits content where new entries get added in order, like a chat thread or an activity feed. It reads politely.

A log signals that older messages matter and sequence is meaningful, so assistive tech reads additions in the order they arrive.

Pick status for a gentle confirmation and alert for a problem. A saved badge is status; a form-blocking error is alert.

Overusing the alert role makes everything interrupt and feel noisy. Reserve it for genuine errors and time-sensitive warnings.

Like raw live regions, an element with role status should exist before you inject text, so the screen reader is already watching it.

Beyond politeness, these roles describe what the region is. That semantic clarity helps both screen readers and the next developer.

You need to announce a form submission error that blocks the user immediately. Which role fits?

You now know status is polite, alert is assertive, and log keeps ordered streams. Choose the role that matches the update's weight. ✅