Editorial team ·
Does the page tell a screen reader that the save worked?
You click Save and a small “Preferences saved” message appears at the bottom. Your keyboard focus stays on the button. Now try the same action with a screen reader and pay attention to what it says. A quiet visual update can be easy to miss when you are listening to the page.
Choose a message that says what actually happened
- Make one change at a time
- Use a demo action with a predictable result.
- Keep track of where the keyboard focus stays.
- Record what is announced
- Compare spoken and visible text.
- Repeat to see whether the message is missing, late, or repeated.
Test the update while staying on the same control
In the fictional settings page, activate Save and wait. Write down what you see and what you hear. A status message can be exposed through a suitable role or property so it is announced while focus remains on Save.
Repeat with a search filter. A message such as “12 results” can confirm that the list has changed. Read on to make sure you can reach the updated results. If the message repeats after every irrelevant action, record what triggers it.
A progress message needs a little care. Test the start and completion of a longer operation. If the screen updates frequently, listen for whether the announcements help the task or keep interrupting the person while they read.
Capture the exact announcement and the focused control at the time. With those two facts, the person fixing the interface can distinguish between a missing announcement, an unexpected focus change, and clear text that was announced too often.
| Action | Example message | What to observe |
|---|---|---|
| Save settings | Preferences saved | Announcement while focus stays on Save |
| Apply a filter | 12 results | Count is available and updated results can be reached |
| Start an export | Export ready | Completion is announced without repeating the progress every second |
Questions and answers
- Do I move focus to a status message?
- An ordinary status message can be announced without moving focus. A decision prompt is a different kind of interaction.
- Do I need a screen reader for this check?
- The accessibility tree helps inspect the role. A screen-reader run shows what is actually announced for that setup.
- Is “Done” a useful message?
- If more than one task is in progress, name what finished. “Export ready” gives someone a clearer next step.