Definition: A live region is an area of a page whose changes a screen reader announces on its own, even when focus is somewhere else. It is marked with aria-live or a role such as status or alert. This is how status messages meet WCAG success criterion 4.1.3 [1][2].
German: Live-Region · Also: aria-live · Last reviewed: 27 September 2026
Why you need one
Sighted people notice when something changes on the page: "Added to basket", "12 results found", "Saved". A screen reader only reads where focus is. Without a live region, a blind person misses the message – and cannot tell whether their click did anything.
The alternative would be to move focus to the message, but that pulls people away from what they were doing. WCAG 4.1.3 therefore requires status messages to be announced without moving focus [1].
The main variants
| Markup | Effect | Example |
|---|---|---|
role="status" (same as aria-live="polite") | announced when the screen reader has finished speaking | "3 items in your basket" |
role="alert" (same as aria-live="assertive") | interrupts immediately | "Your session ends in 1 minute" |
aria-live="off" | not announced | default |
alert is for urgent things. Mark every detail as an alert and you interrupt people constantly.
Common mistakes
- Inserting the region together with the message. Many screen readers only notice changes in a region that was already in the DOM. Create the empty container on load and fill it later.
- Too much in one region: make a whole results list live and all of it gets read out.
- Error messages shown only in colour, with nothing announced.
- Messages that vanish after two seconds, before anyone can read them.
In code
<!-- Present on load, empty at first -->
<p role="status" id="cart-status"></p>// After adding the item, set the text only
const status =
document.getElementById('cart-status')
status.textContent = '3 items in your basket'How to test it
Turn on a screen reader such as NVDA or VoiceOver. Trigger every status message: apply a filter, add to basket, submit a form. Is the message announced without you moving focus?
How Reviseberg handles it
Whether a message is announced can only be checked with a screen reader running. WCAG 4.1.3 is therefore one of the criteria Reviseberg does not test automatically: it stays "untested" until a person records a result and the method they used. A guided test sets out the procedure step by step. A screen reader agent is not part of Reviseberg today.
Related terms
Screen reader · ARIA · Accessibility tree · Form label · Manual accessibility testing