A customer presses Add to cart. The item count changes visually, but their screen reader stays silent. Moving focus to the entire cart would interrupt shopping; announcing the whole page would be worse. A small status message can communicate the result where it happens.
W3C’s ARIA22 technique uses role="status" for this kind of update. The role has polite live-region behaviour, allowing an announcement without moving focus. Its guidance also recommends explicit aria-atomic="true" when the complete status message should be read.
Keep the announcement boundary small
Place the status role on a dedicated message container that exists before the update occurs. Do not apply it to the entire product grid or checkout page. A broad container can include far more content than the user needs to hear.
An illustrative message is “Notebook added. Cart: 2 items. Subtotal: £12.” Include only values the interface actually knows. If delivery charges have not been calculated, calling the subtotal the final total would introduce a separate usability problem.
Test the second click as well as the first
Using a keyboard and a screen reader, add one item and listen. Then change its quantity, remove it and add another. Check whether each relevant result is announced once, in a useful order, while focus stays where the interaction expects it.
Also test a failed addition. The interface should not announce success while the request is still pending or after the server has rejected it. Match the message to the confirmed outcome and provide a usable next step when something fails.
Keep the same information available visually; a spoken update should not become a separate, conflicting account of the cart. The goal is a short piece of feedback that helps someone continue shopping with confidence, rather than a stream of repeated totals that competes with every other action.

