Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Write and announce interface status messages

    A status message explains what happened without necessarily changing pages: a search completed, submission is pending or saving failed. It should describe a real state and help someone decide whether to wait, correct, retry or continue.

    Go to the method

    Screen presenting confirmation on a desk
    AI-generated illustration

    Name a confirmed state

    Write from the service state, not the click. “Request received” needs confirmed receipt; “Sending” means waiting. A stopped animation does not prove acceptance. Avoid always showing success when the network or server can still reject the request.

    No result is different from failure. Distinguish “No products match” from “Unable to load the catalogue”. One invites changed criteria; the other may offer retry. Provide a workable action without discarding fields already completed.

    Announce without needless interruption

    The W3C criterion on status messages concerns changes that should be perceived without receiving focus. An appropriate region can communicate a result. Reserve urgent announcements for situations that truly justify interruption.

    Do not announce an entire result list on every typed character. Communicate a useful summary after updating and keep results available for reading. Check for repeated messages and outdated counts overtaken by newer input.

    Prepare the role="status" region before the message arrives, then update its content. The role implies aria-live="polite" and aria-atomic="true"; technique ARIA22 advises explicitly setting aria-atomic when the entire message needs announcing because environments do not all handle the default alike. Keep useful context in this small region rather than including the full results list.

    Choose the mechanism according to importance and context change. role="alert" is for important, usually time-sensitive information; it should not become the default for every message. Opening a dialog that moves focus uses a different mechanism from a status update without a context change. During acceptance testing, record the browser, assistive technology and observed message: attributes alone prove neither the announcement heard nor its timing.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Dynamic messages: choose a proportionate announcement
    SituationMechanism to considerUseful check
    Waiting for searchA short message in a prepared status region.Focus stays on the control; animations do not cause repeated announcements.
    Results summary availablestatus with a count and its context.The summary matches the current search without reading the whole list.
    Important error needing immediate attentionalert when urgency warrants it.The information is perceivable without forcing focus to move.
    Decision requested in a new windowA named dialog with focus management.Do not count opening it as a status announcement without a context change.

    Preserve useful evidence of the task

    A temporary message may suit a reversible action, but important confirmation should remain findable. An enquiry may need a summary or result page. References and next steps must match what the service actually accepted.

    Explain failure without unnecessary technical detail. Preserve recoverable input and indicate whether retrying could create a duplicate. When the outcome is uncertain, state that uncertainty rather than claiming success or failure without evidence.

    Example: filter a document library

    Educational example: filtering announces “8 documents” while focus stays on the filter. No matches prompts removal of a criterion. A service failure explains that data could not load. Testing distinguishes all three outcomes and verifies that the message belongs to the latest search.

    Measure the time between an action and its genuinely usable result.

    Synthetic case: pressing ‘filter’ immediately shows an indicator but results arrive later. Mark the trigger and the moment results become usable. Separate success, failure and cancellation. Marker names should describe the step without copying a private query; clear entries when keeping them no longer serves a purpose.

    • The duration measures the stated step; an indicator does not count as available results.
    • MDN User Timing

      API for named markers and measured intervals corresponding to application-specific steps.

    Reference documents

    Content updated on

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    Waiting then successWording follows confirmed stateSynthetic request identifier, received response and timeline of pending, success or failure messages.
    Empty resultCriteria can be adjustedOffered action and new results
    Announcement without movingFocus stays usefulActive element and verified announcement
    Uncertain outcomeRecovery avoids blind repetitionInstructions and service behaviour

    Frequently asked questions

    Should every message be an alert?

    No. Urgency, consequence and update frequency determine the announcement. Routine information should not constantly interrupt reading.

    Does a green message prove success?

    Text should express the result without relying on colour and correspond to actual service confirmation.

    Can confirmation disappear automatically?

    Check that consequential outcomes remain available. A brief message may not replace a durable summary.