Announce useful updates without repeating the whole page

What to change

Ask the supplier to limit automatic announcements to useful status information and choose a frequency appropriate to the task.

A worked example

Illustrative example

After a filter change, a short result-count update is announced. The entire list of card descriptions is left for the visitor to explore deliberately.

How to check the result

Accept when meaningful changes are discoverable without repeated interruptions, stale messages or unsolicited reading of large content regions.

A mistake to avoid

Silencing every update avoids noise but can leave users unaware that an action completed or produced no results.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordTrigger a search, filter change or draft save and listen with a screen reader. Record the exact scope and repetition of automatic announcements.Perform several changes quickly. Check whether obsolete updates are announced after a newer state has already appeared on screen.Ask the supplier to demonstrate a concise status approach that keeps focus on the user's current control while making the completed outcome available.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.