Why live regions exist
When content changes after the page loads, a screen reader does not automatically read it. A toast saying Saved or a count of search results could pass by silently. A live region is a container marked so that updates inside it are announced when they change.
- Politeness controls timing so updates wait or interrupt.
- The region must exist before updates so the browser is watching it.
- Only the changed text is usually announced, not the whole page.
Polite and assertive
The two common levels decide how urgent an update is.
- A polite level waits until the user pauses, good for status messages.
- An assertive level interrupts immediately, reserved for urgent errors.
- Overusing assertive is jarring, so prefer polite for routine updates.
Making them reliable
Live regions are finicky, so a few habits keep them dependable.
- Render the empty region first, then insert text into it later.
- Keep messages short and specific so the announcement is clear.
- Avoid flooding the region with rapid changes that pile up.
A status role gives a polite region, and an alert role gives an assertive one, so you can choose the right tool for the message.
Key idea
A live region announces dynamic updates to screen reader users, with polite for routine status and assertive reserved for urgent messages.