Design Principle
Confirmation should protect irreversible or high-impact actions and explain object plus consequence.
Principle
Confirmation should protect irreversible or high-impact actions and explain object plus consequence.
Design action
Name the object, impact scope, and recovery path; use a specific destructive verb for the primary button and keep cancel safe.
Examples
Positive example: Account deletion, rollback, bulk delete, permission change, and payment cancellation are high risk. Counterexample: 'Are you sure?' is the only explanation.
Apply when
Account deletion, rollback, bulk delete, permission change, and payment cancellation are high risk. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from Apple HIG, Material Design, GOV.UK/Polaris/Atlassian component practices, and interaction accessibility principles. Apple HIG Motion: https://developer.apple.com/design/human-interface-guidelines/motion Material Design Motion: https://m3.material.io/styles/motion/overview/how-it-works GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Shopify Polaris Patterns: https://polaris-react.shopify.com/patterns Atlassian Empty State: https://atlassian.design/components/empty-state
Agent Directive
Name the object, impact scope, and recovery path; use a specific destructive verb for the primary button and keep cancel safe.