№ 008 / Opening sequence
Keep the work. Recover clearly.
Recovery is part of the experience.
Example connection interrupted. Your work is safe.
IN EVERYDAY WORDS
When something fails, the interface keeps your work and helps you take the next useful step.
The look
The person's work stays visible, with a specific error and a nearby recovery button.
Say this to a designer
Design a calm error-recovery state for this form. Keep everything the person entered. Explain what failed in everyday words, place a useful retry or correction action beside the explanation, and acknowledge that action immediately. Confirm recovery only after it succeeds. Keep the page steady throughout.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- An operation fails, followed by the visitor choosing to retry or correct it.
- entrance
- Show a concise error near the affected action. Do not shake the whole form or erase its fields.
- path
- Change the message and control in place. Keep the person's input visually anchored.
- timing
- A 120–180 millisecond fade can soften a message change. Recovery follows the real operation's timing, not a decorative delay.
- easing
- Ease out for a short fade, or use an immediate change when that is clearer.
- hold
- Keep the error visible until it is resolved; keep the success confirmation visible after recovery.
- exit
- Let the person continue from their existing work rather than restarting the form.
The vocabulary
- Error recovery
- Helping someone continue after something goes wrong.
- Inline validation
- Showing a field's problem close to that field so it can be corrected.
- Focus management
- Keeping keyboard users oriented by deliberately preserving or moving the active control.
- State transition
- A control changing from one condition to another, such as failed to waiting to successful.
Make it fit your project
Good places to use it: form submission, upload, save operation, network failure.
An operation can fail after someone has invested effort.
Watch for: Do not erase input, display unexplained error codes, or loop retries without consent.
When motion is off: Use direct status changes with the same explanation and recovery controls.
Implementation and accessibility
- Preserve the entered data and clearly identify the failed operation.
- Explain what can be retried and what needs correction.
- Keep the recovery control near the error.
- Acknowledge the retry and prevent duplicate work.
- Show success only after the operation completes; keep focus predictable.
- Associate field errors with their fields.
- Use an appropriate live region without repeated announcements.
- Make recovery available by keyboard.
- Clean up timers and requests.
- Bound retry behavior and avoid indefinite loading.
Give it to your AI
Download the working source and example assets. Match this reference number in the included catalog to its renderer.
Replace [ELEMENT] with the part of your project you want to change. The prompt includes the design brief, motion direction, definitions, and implementation steps.
Read the full prompt
Use AI Acceleration Design Ref #008 (Keep the work. Recover clearly., version 2) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/008. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Recovery is part of the experience. DESIGN REF #008 · Keep the work. Recover clearly. In everyday words: When something fails, the interface keeps your work and helps you take the next useful step. The look: The person's work stays visible, with a specific error and a nearby recovery button. Say this to a designer: Design a calm error-recovery state for this form. Keep everything the person entered. Explain what failed in everyday words, place a useful retry or correction action beside the explanation, and acknowledge that action immediately. Confirm recovery only after it succeeds. Keep the page steady throughout. Motion direction (starting points to adapt): Trigger: An operation fails, followed by the visitor choosing to retry or correct it. Entrance: Show a concise error near the affected action. Do not shake the whole form or erase its fields. Path: Change the message and control in place. Keep the person's input visually anchored. Timing: A 120–180 millisecond fade can soften a message change. Recovery follows the real operation's timing, not a decorative delay. Easing: Ease out for a short fade, or use an immediate change when that is clearer. Hold: Keep the error visible until it is resolved; keep the success confirmation visible after recovery. Exit: Let the person continue from their existing work rather than restarting the form. Design vocabulary: Error recovery: Helping someone continue after something goes wrong. Inline validation: Showing a field's problem close to that field so it can be corrected. Focus management: Keeping keyboard users oriented by deliberately preserving or moving the active control. State transition: A control changing from one condition to another, such as failed to waiting to successful. Reduced motion: Use direct status changes with the same explanation and recovery controls. Implement: 1. Preserve the entered data and clearly identify the failed operation. 2. Explain what can be retried and what needs correction. 3. Keep the recovery control near the error. 4. Acknowledge the retry and prevent duplicate work. 5. Show success only after the operation completes; keep focus predictable. Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML. Reduced motion: Use direct status changes with the same explanation and recovery controls. Accessibility: Associate field errors with their fields. Use an appropriate live region without repeated announcements. Make recovery available by keyboard. Performance: Clean up timers and requests. Bound retry behavior and avoid indefinite loading. Avoid: Do not erase input, display unexplained error codes, or loop retries without consent. Show me the working result, verify keyboard, mobile, loading/error and reduced-motion behavior, and explain any tradeoff. Do not publish or change unrelated elements.
Permanent reference #008 · version 2. Pairs with #003, #005.