Perspective
Something changed, but I wasn't told
The interface updates visually, but the change is not communicated through every relevant interaction mode.
A product can respond correctly and still leave someone unaware that anything happened.
What happens
Content, validation, loading state, search results, a cart total or another status changes without moving focus. A person who can see the update may notice it immediately; someone relying on non-visual output may receive no equivalent information.
Why it matters
If a person does not know an action succeeded, failed or changed the interface, they may repeat it, wait unnecessarily, navigate away or make a decision using stale information.
How to test it
Perform real tasks while paying attention to changes that occur without a page load or focus move. With a screen reader, confirm that important status information is announced at an appropriate time without unnecessarily stealing focus. Also check whether visual-only cues such as colour or animation are carrying the message.
Can automation detect it?
Only partially. Automation can inspect some status-message patterns and semantics. It cannot reliably decide whether every meaningful dynamic change is communicated at the right time or with useful wording.
Relevant WCAG
Depending on the implementation, this commonly relates to 4.1.3 Status Messages. Other criteria can apply when the missing information concerns errors, state or sensory characteristics.
What a pass does not prove
A status being announced does not prove the wording is understandable, the timing is useful, or the resulting workflow is easy to continue.
Follow the evidence trail
- Standard: WCAG 2.2 — 4.1.3 Status Messages
- Test it: Testing changes that happen without moving focus
- Try it: Something changed. Were you told?
- Evidence limit: a successful announcement does not establish that every dynamic state is covered or that the wording is understandable.