# Error Recovery

Error recovery helps people understand what failed, preserve their work, correct the problem, and confidently continue from a known state.

- Type: practice
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/error-recovery/>)

## What it means

Error recovery is the interface and system behavior following a failed action. It identifies the problem in plain language, connects the message to the affected place, preserves recoverable data, offers a specific next step, and confirms resolution. It covers input errors, conflicts, permissions, outages, and partial success.

## Why it matters

Failure is unavoidable in networked products. Recovery determines whether a temporary problem becomes lost work, abandonment, duplicate action, or a support ticket. Accessible recovery makes failures perceivable to keyboard and screen-reader users without forcing them to hunt for what changed.

## When to use it

Use recovery patterns for forms, uploads, payments, saves, authentication, synchronization, and multi-step processes. Design them alongside the happy path, especially where requests may time out, partially succeed, or be retried with financial or data consequences.

## How it works

1. State what happened in human terms; do not lead with implementation codes.
2. Keep valid input and explain how to correct each affected field or condition.
3. Place field guidance nearby and provide a linked summary for long forms; manage focus deliberately.
4. Offer safe actions such as retry, edit, undo, save draft, support, or status.
5. Prevent duplicates with idempotent operations, then confirm the state after recovery.

## A practical example

An address form returns two invalid fields. The page keeps every value, shows a summary linked to each field, moves focus to the summary, and associates each message with its input. After correction, messages clear and the order proceeds without re-entering payment details.

## Where it breaks

A message cannot repair a broken workflow, unavailable permission, or destructive backend. Automatic retries can duplicate payments or edits unless operations are safe. Moving focus or announcing every small validation change can overwhelm assistive-technology users, so urgency must match impact.

## Common mistakes

- Showing “Something went wrong” without a cause or next step
- Clearing the form after failed submission
- Retrying a non-idempotent action without checking whether it succeeded

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/error-recovery/#visualization-error-recovery>)

## Sources

1. [Understanding SC 3.3.1: Error Identification](<https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html>) — W3C Web Accessibility Initiative · Accessibility guidance
2. [Error message](<https://design-system.service.gov.uk/components/error-message/>) — GOV.UK Design System · Institutional design system
3. [Error summary](<https://design-system.service.gov.uk/components/error-summary/>) — GOV.UK Design System · Institutional design system

## Related topics

- [Error Prevention](<https://wiki.soroush.uk/topic/error-prevention/>)
- [Loading State](<https://wiki.soroush.uk/topic/loading-state/>)
- [Empty State](<https://wiki.soroush.uk/topic/empty-state/>)
