Success State
A success state confirms that an action finished. It shows the lasting result and any useful next step.
Your guide is synced and ready for the team to use.
Continue to atlasA real example
A payment finishes with receipt ID R-4812. The page confirms it once, shows the receipt and where to go next, and still works after refresh. Before the server confirms, the status must say Pending, not Success.
Main parts
- 01confirmation
- 02result evidence
- 03next destination
Use it when
Use this term after an important action has a confirmed, lasting result worth showing.
Do not use it when
Do not celebrate normal toggles, announce success before confirmation, or leave the user with no next step.
Name used in code
confirmed result → receipt + next step 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 Success State to solve this user need without losing the current context. User context: A payment finishes with receipt ID R-4812. The page confirms it once, shows the receipt and where to go next, and still works after refresh. Before the server confirms, the status must say Pending, not Success. Recommended pattern: Success State. Why it fits: Use this term after an important action has a confirmed, lasting result worth showing. Do not use it when: Do not celebrate normal toggles, announce success before confirmation, or leave the user with no next step. 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 Success State. Definition: A success state confirms that an action finished. It shows the lasting result and any useful next step. 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.