Status Message
A status message reports a result, progress, or wait without opening a dialog or taking focus away.
A real example
After a buyer uses code JULY15, focus stays where it is. A status says, “Discount applied; total NT$1,530.” A bad code shows an error linked to its field. A payment failure that needs a choice opens a dialog and moves focus instead.
Main parts
- 01Triggering operation
- 02Persistent message container
- 03Non-interrupting announcement
Use it when
Use it for an update that people should notice without stopping what they are doing or moving focus.
Do not use it when
Do not rely only on a toast that quickly disappears. If a message needs action now, move focus to the place where people can act.
Name used in code
role=status or an appropriate aria-live region without focus transfer Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use Status Message to solve this user need without losing the current context. User context: After a buyer uses code JULY15, focus stays where it is. A status says, “Discount applied; total NT$1,530.” A bad code shows an error linked to its field. A payment failure that needs a choice opens a dialog and moves focus instead. Recommended pattern: Status Message. Why it fits: Use it for an update that people should notice without stopping what they are doing or moving focus. Do not use it when: Do not rely only on a toast that quickly disappears. If a message needs action now, move focus to the place where people can act. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Status Message. Definition: A status message reports a result, progress, or wait without opening a dialog or taking focus away. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.