- Job
- Slow down
- Requirement
- must specify if destroy exists
- States / rules
- Friction sentence; not dismissible by accident
- Specified means
- Q5 applied
- Hardest context
- Not separately stated in this row.
—
Accidental delete
Flow
Trigger: An action can delete, revoke, remove, or otherwise cause a costly-to-reverse loss.
- Identify the exact object or consequence before asking for confirmation.Identify the exact object or consequence before asking for confirmation.
- Explain what will happen and whether recovery is possible.Explain what will happen and whether recovery is possible.
- Use a confirm action whose verb names the destructive outcome.Use a confirm action whose verb names the destructive outcome.
- Keep cancellation visually and keyboard-accessibly available.Keep cancellation visually and keyboard-accessibly available.
- Prevent duplicate submission while the action is in flight.Prevent duplicate submission while the action is in flight.
- After completion, return the user to a stable context and state what changed.After completion, return the user to a stable context and state what changed.
Typical Building Blocks composition
Composition below is baseline guidance for the pattern; it does not rename or add source checklist rows.
Flow rules
- Do not use confirmation as theater for low-cost reversible actions.
- The destructive verb stays explicit in the final action.
- Focus enters the confirmation surface predictably and returns intentionally.
Responsive behavior
On small screens, the confirmation surface may become a sheet or full-width dialog, but consequence, cancel path, and destructive verb remain visible.
Accessibility is tested across the sequence.
Keyboard order, focus movement, state announcements, touch targets, cancellation, and recovery must be verified for the whole flow—not only for each participating component in isolation.
Recovery is part of the pattern.
A complete pattern defines what the user sees when the happy path breaks, what is preserved, where focus goes, and how the user safely resumes or exits.
Catalog connection
A product Catalog can show this pattern only when the product actually implements the flow. If it is absent, keep the section honestly Not yet rather than mounting a fictional working pattern.