Toast
A toast is a short status message. It doesn't block the page and usually leaves on its own.
A real example
After autosave, “Changes saved” appears quietly in a corner and is announced once.
Main parts
- 01State signal
- 02Human-readable message
- 03Timing or progress
- 04Recovery path
Use it when
Use it for a low-risk confirmation that doesn't need an answer.
Do not use it when
Never use it for an important error or instructions people must read or follow.
Name used in code
role="status" 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 Toast to solve this user need without losing the current context. User context: After autosave, “Changes saved” appears quietly in a corner and is announced once. Recommended pattern: Toast. Why it fits: Use it for a low-risk confirmation that doesn't need an answer. Do not use it when: Never use it for an important error or instructions people must read or follow. 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): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Toast. Definition: A toast is a short status message. It doesn't block the page and usually leaves on its own. 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.