Parts that must work together
A pattern is not a screenshot. It is a reusable decision model that must preserve intent, state, recovery, and accessibility as layouts change.
Decision framework
Questions to answer before choosing UI
Can the action be reversed?
Prefer immediate action with undo when reversal is reliable. Confirmation becomes more important as consequence, scope, or irreversibility increases.
What exactly is affected?
Name the object, amount, collaborators, permissions, and downstream effects. Do not rely on a generic danger color.
What proof is proportionate?
A normal confirmation may need only a specific button label. High-impact actions may justify reauthentication, typed confirmation, or a delay.
End-to-end accessibility
- Move focus into confirmations and return it intentionally
- Use action-specific labels
- Do not make color the only danger cue
- Announce completion, failure, and undo availability
- Keep destructive and cancel actions distinguishable at zoom and high contrast
Failure patterns to test
Confirming every harmless action
Using Yes and No labels
Making the destructive action the safest-looking choice
Claiming an action is reversible when undo can fail
Hiding scope until after confirmation