Someone filters orders on example.com/orders. The list updates in place: three shipped rows appear, and a heading now says "3 shipped orders." A screen reader user is still on the Status control and hears nothing, so they don't know the page changed. The results are visible. They were never announced.
Web HIG tip #18 (Quick #78): Dynamic content updates must be announced to screen readers ( aria-live or focus management).
Why it matters
An in-page update does not load a new document, so the screen reader does not announce a new page. Without a live-region update or a focus move:
People using a screen reader can miss a filter, save, or cart change that happened elsewhere on the page
Keyboard users can be left on the control they just used, with no cue that content below or beside it changed
A visual toast or a badge is easy to miss if it is not also announced, or if focus never moves to it
Announcing every keystroke while someone types a query can be just as unusable as announcing nothing
Quick #78 is…