# Announce the result without stealing the user’s place

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Announce the result without stealing the user’s place

ID: MHC-D-RESEARCH-1105 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/announce-the-result-without-stealing-the-user-s-place

Finished should not be a message only sight can hear.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### 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.

### Explanation

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.

### Steps

1. Identify the result or progress change the user needs to know.
2. Provide an appropriate status message rather than shifting focus to decorative feedback.
3. Check that it is announced once, at a useful time, without interrupting every small change.

### 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?

### Limits

- Not every update deserves an alert. Repeated progress announcements can overwhelm the information they were meant to reveal.

### Evidence and sources

- supports: WCAG 4.1.3 addresses status messages that assistive technology can present without receiving focus. — RS-DF1D065015C67030. Not every interface change is a status message; excessive or urgent announcements can be disruptive. (Success criterion and intent.)
- RS-DF1D065015C67030: Understanding Success Criterion 4.1.3: Status Messages — https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html

### Vedokrok editorial review

Choose the status message before the announcement

A changed screen is not always a status message. First identify the information and whether the user's context changes.

#### Separate feedback from a new place to work

A status message reports an outcome, waiting, progress or an error without changing the user's context. An export tool's completion notice beside the form can qualify while focus stays in place. An error dialog that takes focus and an options panel opening are different cases: check the dialog or control's own accessibility, rather than adding an alert by habit. WCAG 4.1.3 does not require new feedback for every change.

#### Make ordinary feedback available with its meaning

For non-urgent updates, WAI describes a role=status container that exists before the message arrives. Where this pattern fits, put the update and the context needed to understand it inside that container. If the whole phrase needs announcing, WAI advises explicit aria-atomic=true because some environments do not apply the role's atomic default. In an export tool, hearing 'Two files ready' is useful; hearing only 'Two' leaves the result unclear. This is one implementation pattern, not the only allowed technique.

#### Test the experience, not an announcement count

Record the browser, assistive technology and settings; trigger the change while doing another part of the task. Check access to the meaningful update and unnecessary interruptions. Useful progress feedback may be intermittent, and assistive technology may delay or suppress it according to user preferences. 'Spoken exactly once' is not the criterion. This check complements actionable error wording in 1104; it does not certify the whole interface.

**Editorial takeaway:** Leave a test record: what changed, why it is a status message, how its meaning is exposed, and what happened in the tested setup.

#### Editorial evidence

- supports: SC 4.1.3 concerns programmatically determinable status information that can be presented without taking focus. — wcag22-20241212. Normative scope, not a mandate for one spoken announcement or a complete conformance test. (SC 4.1.3; glossary: status message)
- limits: Ordinary expansion and focus-taking dialogs fall outside this status-message criterion; timing can reflect user preferences. — RS-DF1D065015C67030. Selected guidance qualifies the earlier once-only instruction. Other accessibility requirements remain applicable. (Intent; Benefits; Status message examples; Examples of changes that are not status messages; Other uses of live regions or alerts)
- supports: The ARIA22 pattern establishes the status container before an update and retains meaningful context within it. — w3c-aria22-status. The role defines atomic updates by default; WAI recommends explicit aria-atomic=true where the whole message is needed because support differs. This optional technique still needs testing in the intended environment. (Description; Tests, Procedure 1–3)
- RS-DF1D065015C67030: Understanding Success Criterion 4.1.3: Status Messages — https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html
- wcag22-20241212: Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation, 12 December 2024 — https://www.w3.org/TR/2024/REC-WCAG22-20241212/
- w3c-aria22-status: ARIA22: Using role=status to present status messages — https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA22

Editorial version: 1.0.0 · evidence checked 2026-10-06 · Agent editorial review; not human or expert certification.

No review details supplied.
