This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung →
Accessibility
How do blind visitors learn about a website's status messages?
Blind visitors only learn about status messages if the website technically marks them as such — then the screen reader announces them automatically, without the visitor leaving their current position. If the message "Item added to cart" only appears visually at the edge of the screen, it stays silent for screen readers. WCAG criterion 4.1.3 requires that status messages be programmatically recognisable as such.
A silent message is like a nod on the phone
Status messages accompany almost every action on the web: "Item added to cart", "3 results found", "Your message has been sent", "Form loading". Sighted visitors notice them in passing. A blind visitor, though, has their focus elsewhere — still on the button they just pressed, say. If the confirmation only appears visually, they never learn whether their action worked. They press again, add the item to the cart twice, or give up, unsure what happened. The solution: the message area is marked up in the source code as a status region. Screen readers watch such regions and announce new content on their own — the visitor stays at their current position and still hears the confirmation.
How the audit service checks status messages
The automated measurement with axe-core checks the technical side of existing message regions: are the markers valid and correctly applied, so that assistive tools can read them. The decisive question goes further: is every message that arises during actual use really announced. That can only be judged by someone operating the website and listening. Our report therefore openly marks this part as a manual check point. At the Gold Standard level, a human triggers typical actions — adding something to the cart, submitting a form, starting a search — and checks with a screen reader whether the confirmation comes through audibly. An empty check counts as a failure with us, never as a free pass.
- Collect all the status messages on your website: cart confirmations, search result counters, submission confirmations, loading notices.
- Ask your agency to mark up the message areas as status regions in the source code, so screen readers announce them.
- Test with the screen reader built into your operating system whether the message is announced audibly after the action.
- Keep status messages short and clear — the text is announced word for word, and long messages get tiring to listen to.
FAQ
What is a status message under WCAG?
A status message informs about the outcome or progress of an action, without changing the page and without moving focus: "Item in cart", "3 results found", "Message sent". Criterion 4.1.3 requires that such messages be marked up as a status region in the source code, so screen readers announce them automatically.
Why doesn't the screen reader read out my success message?
Screen readers read at the spot where the visitor's focus currently sits. A message that only appears visually somewhere else lies outside that field of view and stays silent. Only the technical marker as a status region tells the program to watch that area and announce new content on its own — without the visitor leaving their position.
How does the audit service check status messages?
The measurement engine automatically checks with axe-core whether existing message regions are technically marked up correctly. Whether every message is announced audibly during actual use is judged by a human at the Gold Standard level: they trigger typical actions and listen along with a screen reader. The report states both parts separately — measured and humanly judged.