Icon-only ambiguous action

Problem Context

• A toolbar, table row, card, or compact navigation surface contains icon-only controls.
• The icon is not conventional in the product domain, resembles multiple actions, or changes meaning by context.
• The action can archive, delete, share, expose data, change permissions, spend money, or otherwise create user risk.
• Mouse users may see a tooltip, but touch, keyboard, voice, and screen reader users need the action name before activation.

Selection Rules

• Flag this anti-pattern when the icon meaning is not clear from the visible label, surrounding row, action group, and product convention.
• Use visible text for primary, destructive, financial, security-sensitive, sharing, permission, and low-frequency actions.
• Use icon plus text when a symbol helps scanning but the action still needs explicit meaning.
• Allow icon-only buttons only for familiar low-risk utilities such as search, close, back, or play when each control has a precise accessible name.
• Use confirmation dialog when the user has already chosen a clearly labeled high-risk action and must review consequence before commitment.
• Use undo when a clearly named reversible action has completed and users need a short recovery window.
• Do not use hover-only tooltip text as the only way to understand an action.

Required States

• Default state where the action name is visible or programmatically exposed before activation.
• Hover, focus, and touch-accessible help state for compact actions that still need supplemental explanation.
• Activated state that confirms the named action, affected object, and result.
• Risk review state for destructive or privacy-sensitive actions.
• Recovery state such as undo, restore, or confirmation cancellation when the action has consequences.

Interaction Contract

• The visual control, accessible name, and action result use the same verb and object.
• Keyboard focus reveals the same action meaning that pointer users receive, without relying on hover alone.
• Touch users can identify the action without long-press discovery or trial activation.
• Repeated icons in a row or toolbar are differentiated by accessible names such as Archive report, Download report, and Share report.
• The icon does not change meaning across pages unless the surrounding visible label or control text changes with it.
• Risky icon actions provide prevention or recovery through confirmation, preview, undo, or restore.

Implementation Checklist

• Audit every icon-only button for visible action text, accessible name, affected object, and consequence.
• Prefer text labels for primary and high-risk actions; use icon plus text when space allows.
• If icon-only is justified, set a specific accessible name that describes the action, not the icon shape.
• Keep tooltip text supplemental and make sure keyboard and touch users receive equivalent information.
• Avoid reusing the same symbol for different verbs in the same product area.
• Pair destructive icon actions with confirmation, undo, or restore according to consequence and reversibility.
• Test with keyboard navigation, screen reader announcement, touch input, zoom, localization, and first-time users.

Common Generated-UI Mistakes

• Using a trash, tray, box, arrow, or exclamation icon for archive, delete, download, export, and warning actions without visible words.
• Providing an accessible name such as icon, more, or button instead of the action and object.
• Putting the only explanation in a tooltip that appears on hover but not focus or touch.
• Using the same icon for Archive on one page and Delete on another.
• Hiding destructive row actions until hover, then presenting only symbols.
• Relying on color or placement to distinguish icon actions with different consequences.

Critique Questions

• Can a first-time user name the action and consequence before pressing the control?
• Will the screen reader announcement match the visible label or tooltip text?
• Does the icon mean the same thing across this workflow and product area?
• Would a touch or keyboard user receive the same explanation as a mouse user?
• If the action is destructive or exposes data, is there confirmation, preview, undo, or restore?