Error State
An error state stays visible when an action or page fails. It explains the specific problem and gives a safe way to recover.
Your local edits are safe. Check the connection and try the sync again.
A real example
A form has a wrong account number and the service also times out. The field says how to fix the number, while the service error keeps all input and offers Try again. Blaming the user or deleting their work is not recovery.
Main parts
- 01specific failure
- 02affected context
- 03recovery action
Use it when
Use this term when a failure blocks the task. The user needs a clear reason or a way to recover.
Do not use it when
Do not use one vague error for input, permission, network, and server problems that need different fixes.
Name used in code
failure type → preserved context + recovery 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 Error State to solve this user need without losing the current context. User context: A form has a wrong account number and the service also times out. The field says how to fix the number, while the service error keeps all input and offers Try again. Blaming the user or deleting their work is not recovery. Recommended pattern: Error State. Why it fits: Use this term when a failure blocks the task. The user needs a clear reason or a way to recover. Do not use it when: Do not use one vague error for input, permission, network, and server problems that need different fixes. 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 Error State. Definition: An error state stays visible when an action or page fails. It explains the specific problem and gives a safe way to recover. 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.