Back to compare picker

Icon-only ambiguous action vs Confirmation dialog vs Undo

Use clear labels before users act, confirmation when a clearly chosen high-risk action needs review, and undo when a named reversible action has already completed.

Learn the decision

Match the interaction to the person's task

Use clear labels before users act, confirmation when a clearly chosen high-risk action needs review, and undo when a named reversible action has already completed.

Icon-only ambiguous action

Use it when: Use this anti-pattern entry to audit toolbars, row actions, cards, command bars, mobile action sheets, and generated UIs with symbol-only controls.

Make this state clear: Default state where the action name is visible or programmatically exposed before activation.

Observe the result: Users can identify the action before activation and receive confirmation, undo, or result status after consequential actions.

Study the full pattern →

Confirmation dialog

Use it when: The action is destructive, irreversible, costly, security-sensitive, privacy-affecting, or externally visible.

Make this state clear: Pre-action state with an explicit consequential trigger.

Observe the result: Cancel, Escape, and Keep archive leave the archive unchanged and return focus to Delete archive.

Study the full pattern →

Undo

Use it when: The action is common and mistakes are likely.

Make this state clear: Normal state before the user action.

Observe the result: Undo restores the deleted task to the list and reports Quarterly report restored.

Study the full pattern →

Practice the judgment: Imagine this situation: Users choose the wrong row action because several icons are unlabeled. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.

Review the underlying principle →

Decision dimensions

Dimension Icon-only ambiguous actionConfirmation dialogUndo
UI or UX UI + UX - Ambiguous action anti-patternUI + UX - Consequential alert decisionUX - Post-action recovery behavior
UI guidance Replace ambiguous symbol-only controls with visible text or icon-plus-text actions that name the verb and affected object.Render an alert-style modal decision with a specific title, consequence description, safe cancellation, and a destructive action label that names the object or scope.Show a named recovery affordance after the completed action, such as Undo delete for a specific task, near the result or in a consistent status region.
UX guidance Make users confident about what will happen before activation instead of forcing recognition, memorization, or trial-and-error.Help the person reach a clear task outcome.Let users move quickly through frequent reversible actions, then recover from mistakes after seeing the result.
Good UI A report row shows Archive report, Download report, and Share report as labeled controls with matching accessible names.Delete Research archive? explains that 14 notes and shared links will be permanently removed, offers Keep archive, and labels the danger action Delete archive.Deleting Quarterly report removes it from the list and shows a recovery panel saying Quarterly report deleted with an Undo task button.
Bad UI The same box icon archives reports in one table and deletes folders in another.The red destructive action is enabled immediately and sits where users expect the routine primary button.Undo action disappears before users can activate it.
Good UX Users can identify the action before activation and receive confirmation, undo, or result status after consequential actions.Cancel, Escape, and Keep archive leave the archive unchanged and return focus to Delete archive.Undo restores the deleted task to the list and reports Quarterly report restored.
Bad UX Hover-only tooltip is the only explanation for a destructive action.Every archive, filter, and dismiss action opens the same confirmation until users click through automatically.The UI promises undo for a side effect that has already notified external recipients.
Best fit Use this anti-pattern entry to audit toolbars, row actions, cards, command bars, mobile action sheets, and generated UIs with symbol-only controls.The action is destructive, irreversible, costly, security-sensitive, privacy-affecting, or externally visible.The action is common and mistakes are likely.
Avoid when The icon is paired with visible text that names the action.The action is routine and easily reversible.Recovery would restore only part of the user's lost work.
Required state Default state where the action name is visible or programmatically exposed before activation.Pre-action state with an explicit consequential trigger.Normal state before the user action.
Accessibility burden Every interactive icon control needs an accessible name that describes the action and, when useful, the affected object.Use alertdialog semantics or platform equivalent when the decision is urgent and requires a response.Make the undo control keyboard reachable and programmatically identifiable.
Common misuse Providing an accessible name such as icon, more, or button instead of the action and object.Asking users to confirm every routine action until they stop reading.Restoring only part of the prior state while implying full recovery.

Icon-only ambiguous action

UI or UX
UI + UX - Ambiguous action anti-pattern
UI guidance
Replace ambiguous symbol-only controls with visible text or icon-plus-text actions that name the verb and affected object.
UX guidance
Make users confident about what will happen before activation instead of forcing recognition, memorization, or trial-and-error.
Good UI
A report row shows Archive report, Download report, and Share report as labeled controls with matching accessible names.
Bad UI
The same box icon archives reports in one table and deletes folders in another.
Good UX
Users can identify the action before activation and receive confirmation, undo, or result status after consequential actions.
Bad UX
Hover-only tooltip is the only explanation for a destructive action.
Best fit
Use this anti-pattern entry to audit toolbars, row actions, cards, command bars, mobile action sheets, and generated UIs with symbol-only controls.
Avoid when
The icon is paired with visible text that names the action.
Required state
Default state where the action name is visible or programmatically exposed before activation.
Accessibility burden
Every interactive icon control needs an accessible name that describes the action and, when useful, the affected object.
Common misuse
Providing an accessible name such as icon, more, or button instead of the action and object.

Confirmation dialog

UI or UX
UI + UX - Consequential alert decision
UI guidance
Render an alert-style modal decision with a specific title, consequence description, safe cancellation, and a destructive action label that names the object or scope.
UX guidance
Help the person reach a clear task outcome.
Good UI
Delete Research archive? explains that 14 notes and shared links will be permanently removed, offers Keep archive, and labels the danger action Delete archive.
Bad UI
The red destructive action is enabled immediately and sits where users expect the routine primary button.
Good UX
Cancel, Escape, and Keep archive leave the archive unchanged and return focus to Delete archive.
Bad UX
Every archive, filter, and dismiss action opens the same confirmation until users click through automatically.
Best fit
The action is destructive, irreversible, costly, security-sensitive, privacy-affecting, or externally visible.
Avoid when
The action is routine and easily reversible.
Required state
Pre-action state with an explicit consequential trigger.
Accessibility burden
Use alertdialog semantics or platform equivalent when the decision is urgent and requires a response.
Common misuse
Asking users to confirm every routine action until they stop reading.

Undo

UI or UX
UX - Post-action recovery behavior
UI guidance
Show a named recovery affordance after the completed action, such as Undo delete for a specific task, near the result or in a consistent status region.
UX guidance
Let users move quickly through frequent reversible actions, then recover from mistakes after seeing the result.
Good UI
Deleting Quarterly report removes it from the list and shows a recovery panel saying Quarterly report deleted with an Undo task button.
Bad UI
Undo action disappears before users can activate it.
Good UX
Undo restores the deleted task to the list and reports Quarterly report restored.
Bad UX
The UI promises undo for a side effect that has already notified external recipients.
Best fit
The action is common and mistakes are likely.
Avoid when
Recovery would restore only part of the user's lost work.
Required state
Normal state before the user action.
Accessibility burden
Make the undo control keyboard reachable and programmatically identifiable.
Common misuse
Restoring only part of the prior state while implying full recovery.
Decision rules
  • Flag icon-only ambiguous action when users cannot identify the action, affected object, or consequence before activating a symbol-only control.
  • Use visible text or icon-plus-text for primary, destructive, privacy-sensitive, financial, sharing, permission, and low-frequency actions.
  • Allow icon-only controls only for familiar low-risk utilities when each control has a precise accessible name and equivalent focus or touch help.
  • Use confirmation dialog after the user has selected a clearly labeled high-risk action and needs to review consequence, object, and safe cancellation before commitment.
  • Use undo after a clearly named reversible action completes and users need a short recovery window without interrupting the main flow first.
  • Do not use confirmation or undo to compensate for an icon the user could not understand before activation; fix the action label first.
  • If the action is both ambiguous and destructive, add a visible label before the trigger and then choose confirmation or undo according to consequence and reversibility.
  • Do not rely on hover-only tooltip text as the primary explanation because keyboard and touch users may never receive it before acting.
Inspect live examples
Failure modes
  • Users choose the wrong row action because several icons are unlabeled.
  • A confirmation dialog asks users to confirm an action they never understood at the trigger.
  • Undo appears after an accidental symbol-only destructive action, but users still do not know what happened.
  • A screen reader announces button or icon shape instead of the action name.
  • The same symbol has different meanings across adjacent product areas.
  • Touch users cannot discover a hover tooltip before activation.

Saved items