{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/announce-the-result-without-stealing-the-user-s-place",
  "id": "MHC-D-RESEARCH-1105",
  "version": "0.1.0",
  "title": "Announce the result without stealing the user’s place",
  "summary": "Finished should not be a message only sight can hear.",
  "kind": "protocol",
  "body": "Make relevant status information programmatically available without unnecessarily moving focus. Choose an announcement pattern appropriate to the urgency. Test with the actual assistive technology; adding a live region is an implementation choice, not proof of a good experience.",
  "limits": [
    "Not every update deserves an alert. Repeated progress announcements can overwhelm the information they were meant to reveal."
  ],
  "topics": [
    "accessible-workflows-50"
  ],
  "intents": [],
  "source_ids": [
    "RS-DF1D065015C67030"
  ],
  "evidence": [
    {
      "claim": "WCAG 4.1.3 addresses status messages that assistive technology can present without receiving focus.",
      "source_id": "RS-DF1D065015C67030",
      "role": "supports",
      "note": "Not every interface change is a status message; excessive or urgent announcements can be disruptive.",
      "locator": "Success criterion and intent."
    }
  ],
  "use_when": [
    "A background action changes status but assistive-technology users receive no useful signal."
  ],
  "avoid_when": [
    "Not every update deserves an alert. Repeated progress announcements can overwhelm the information they were meant to reveal."
  ],
  "example": "After an upload, the interface announces Processing complete while the user remains in the field they were editing.",
  "check": "Can the user tell what happened and continue the task without losing their place?",
  "steps": [
    "Identify the result or progress change the user needs to know.",
    "Provide an appropriate status message rather than shifting focus to decorative feedback.",
    "Check that it is announced once, at a useful time, without interrupting every small change."
  ],
  "sources": [
    {
      "id": "RS-DF1D065015C67030",
      "title": "Understanding Success Criterion 4.1.3: Status Messages",
      "url": "https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html"
    }
  ],
  "relations": [],
  "collections": [
    {
      "id": "RC-F151F4A278F577C4",
      "title": "Make the task usable across different ways of accessing it",
      "url": "/collections/make-the-task-usable-across-different-ways-of-accessing-it"
    }
  ]
}