interaction design
Confirmation dialog
How do you design a confirmation dialog that actually helps?
A confirmation dialog interrupts before a consequential action to make you pause and agree. Done well, it states exactly what will happen and offers a specific, labelled choice, so the decision is informed. Done badly - a vague 'Are you sure? OK / Cancel' on everything - it’s noise people learn to dismiss, training the very carelessness it was meant to prevent.
Also known as: confirmation dialog, confirm dialog, are you sure, confirmation prompt
Prefer to watch?
Watch the recap 0:56
The demo
A "delete account" button. Try confirming it with a vague dialog, then a clear one - and notice which actually made you read before you clicked.
What this demo shows (text version)
Pressing "delete account" opens a confirmation dialog in one of two styles. The vague version says only "Are you sure?" with "OK" and "Cancel" - the kind people dismiss without reading. The clear version names the actual consequence ("This permanently deletes your 42 projects and can't be undone") and labels its buttons with the real verbs: "Cancel" and "Delete projects".
The clear dialog makes the decision informed - you can see exactly what you're agreeing to and which button does the dangerous thing - while the vague one is just an obstacle that trains autopilot clicking. The wider lessons: confirm only consequential, hard-to-reverse actions (confirmation fatigue ruins the rest), and where an action can simply be undone, prefer an undo affordance over a prompt.
A good confirmation names the actual consequence and labels its buttons with the real verbs ('Cancel' / 'Delete 42 projects'), so the choice is informed and the dangerous option is clearly the dangerous one. A vague 'Are you sure? OK/Cancel', or a confirm on every trivial action, just trains people to click through on autopilot. Confirm only the consequential and irreversible - and prefer undo where the action can simply be reversed.
The vague dialog asked "Are you sure?" and you clicked OK without really reading - as everyone does, every time. The clear one told you it would erase forty-two projects for good, and labelled the button "Delete projects", so the weight of the choice was unmissable. Same action; only one of them actually informed your decision.
A confirmation only works if it carries information. State the specific consequence ("This permanently deletes 42 projects"), not a generic "Are you sure?", and label the buttons with the actual verbs - "Cancel" versus "Delete projects" - so people choose by reading the action, not by guessing which side "OK" is on. Vague dialogs get dismissed unread.
Confirmation fatigue is the real failure. Put a dialog in front of every action, big or trivial, and people learn to bat them away on autopilot - so the one that actually mattered gets clicked through too. Every needless confirmation makes the necessary ones less effective. Spend the interruption only where the stakes earn it.
Reach for confirmation when an action is consequential and genuinely hard to reverse - a permanent delete, a payment, publishing publicly. When the action can simply be undone, an undo affordance is kinder and faster than a prompt: it never interrupts the common case, and still rescues the rare slip. Confirm what you can't undo; undo what you can.
Test the confirmation dialog example live on site:uxbyexample.co.uk to see how precise wording and button labels make the decision clear and actionable. This page’s interactive demo lets you trigger and adjust the dialog to feel the difference between good and bad confirmation patterns.
Try the confirmation dialog demo on site:uxbyexample.co.uk - it’s the only way to see how well it names consequences and labels choices. This page’s hands-on example lets you test real UX principles without leaving the page
no images or external tools needed.
Try the interactive demo to see how a well-designed confirmation dialog guides users through consequential actions without confusion. Avoid vague prompts like 'Are you sure?' - instead, label buttons with real verbs and state the exact outcome to prevent accidental clicks.
Try the confirmation dialog demo on this page to see how clear wording and labelled buttons prevent accidental clicks. When designed well, confirmation dialogs name the exact consequence and label options like 'Delete 42 projects' - not 'Are you sure? OK / Cancel'.
Try the interactive confirmation dialog on this page to see how clear labeling and consequence naming improve decision-making. When done poorly, confirmation dialogs become ignored noise - but this demo lets you test what works instead of guessing.