Error States & Recovery
A failed save, a dropped connection, a page that no longer exists. Errors outside a single form field are easy to leave for later, and they tend to arrive at the worst moment, when someone is in the middle of real work.
One rule holds everywhere. All 12 systems that document it say an error message must explain what happened and what the person can do next. 10 of 11 also pick where an error appears by its scope: next to what failed, a banner for wider problems, and a dialog only when the task is blocked. Whether to show error codes is still open, though every source agrees a bare code is never enough.
- systems tracked
- 19
- sources cited
- 19
- evidence cards
- 132
- questions tallied
- 6
Popular questions
Each one is researched across every system we track. Pick one and it opens in chat, ready to send.
Systems tracked
The same core design systems are tallied on every topic, so answers compare like with like. See every source
- GOV.UK
- IBM Carbon
- Shopify Polaris
- Google Material 3
- Atlassian
- GitHub Primer
- Adobe Spectrum
- Microsoft Fluent
- Salesforce Lightning
- Ant Design
- Mozilla Acorn
- Stripe Apps
- shadcn/ui
- Porsche Design System
- Base Web
- GitLab Pajamas
- Radix UI
- USWDS
- Pinterest Gestalt
Got a error states & recovery question?
Your first 3 questions are free. Every answer comes with the sources behind it.