When a browser screen reports a changing result without taking focus away from the current control, treat that message as information about the page state. It is not automatically a question, approval request, or command to answer.
How to read a status message
Hypothetical example: In a public catalogue, a user types maps into the search field. A message then announces “12 matching titles,” while focus remains in the search input. The useful observation is that the catalogue has reported a count for the current update. The outcome is a readable status change: the user can decide what to inspect next, but no response to the announcement itself is required.
This interpretation concerns an explicitly implemented ARIA status pattern. The status role supplies advisory information, normally announced politely, and does not move focus when its content changes. See the MDN status role reference for the defined role behaviour.
Why it differs from a dialog
A dialog is a separate interaction pattern. Hypothetical contrast: a page presents a dialog titled “Delete saved list” with explicit response controls. That presentation asks the user to choose how to proceed; it is not equivalent to the catalogue’s “12 matching titles” announcement. The count describes an update, whereas the deletion dialog requests a decision. Reading that question is not consent. In this comparison, nobody chooses a response and no deletion occurs. The point is to distinguish a reported result from a pending decision.
Practical limit when checking the screen
Do not infer that a status announcement proves the result is accurate, complete, or suitable for a particular purpose. It only identifies information exposed through that status mechanism. Also, announcement timing can vary between browsers, assistive technologies, and updates, so an intermediate message may not be heard every time. Check the visible page state and the focused control when the distinction matters. The key test is whether the message reports a change while leaving focus in place, or presents a separate interaction that expects an explicit response.