A Live Region Audit Checks What Your App Says Out Loud

What We Keep Finding

Modern interfaces talk with their hands. A toast here, a counter there, three results filtered in, one item added to the cart. Sighted users see the flutter. Screen reader users hear exactly what the code announces, which by default is nothing. "Added to cart" that was never spoken did not happen.

Most teams know about politeness and stop there, and politeness is only half of it. Politeness decides when a message gets read, so whether it interrupts or waits its turn. Atomicity decides what gets read, meaning the whole region or only the bit that changed. Get that second one wrong and your cart counter announces "3" into the silence, with no word attached to say three of what. The status role carries both settings sensibly by default. A plain live region does not, and a plain live region is what most people reach for.

The second thing that goes wrong is a false negative, and it is why teams tell us the announcement is there when it is not. A live region generally has to exist in the page before the message lands in it, so a component that creates its own region and fills it in the same breath announces nothing at all. The one role that is handled differently is the alert role, which is announced even when injected. That is the difference between a toast that works and a toast that is silently perfect in the code review.

Then there is announcing twice, which is the commonest defect in the whole category and the one that looks most like diligence. Moving focus is already a change of context, which means the message was never a status message and never needed a live region on top. A form that jumps focus to the error summary and also fires a polite announcement says the same thing twice, and the second interrupts the first. It is not belt and braces. It is a bug.

One boundary worth knowing before you inventory anything, because it decides what belongs in a finding. A list of search results is not a status message. The little line saying "18 results" or "no results" is, and only if the update does not move focus or reload the page. So a filter that repaints a grid needs a count announced, not the grid.