Buttons must restate the action, not say OK

What it is

Action-specific confirmation controls restate the pending commitment with a short verb phrase such as “Delete album” or “Discard changes,” while the alternative clearly names the result of declining it. “OK” and “Yes” merely answer a question and cease to predict consequences when separated from the heading or encountered in a screen-reader control list. Restatement does not put quantity, timing, and every risk into the button: the body owns scope, while the control names the committed action.

Why it happens

People often scan dialogs through their controls, and assistive technology may expose buttons directly. An action label restores information scent at the last decision point and reduces applying one dialog's answer to another. With “OK/Cancel,” even Cancel can leave unclear whether it cancels the pending action or the wider task. Pairs such as “Discard changes/Keep editing” and “Leave/Stay on page” oppose outcomes. Defaults and initial focus amplify a label's effect, so a consequential option cannot be distinguished only by color or become easy to trigger merely through layout convention.

Studying it

Use brief exposures and keyboard tasks with realistic save, delete, replace, leave, permission, and subscription dialogs. Ask participants to restate both button outcomes from the controls alone, then make the intended choice. Record slips, hesitation, body rereading, the destination after decline, and accidental keyboard submission; include screen-reader button navigation and voice control. Hold body copy, order, visual weight, and default focus constant when comparing labels so those factors do not masquerade as wording effects.

Where it stops holding

A purely informational message with one dismissal control can use a locally natural “Got it” or equivalent because there is no competing commitment. Familiar, low-risk actions may also use terse standard labels. The decline side need not literally say “Cancel”; “Keep editing” is clearer when the return state matters. Platform conventions, bidirectional text, and narrow screens constrain length, but not at the expense of the core verb. Full scope remains in accessible dialog copy.

Applying it

• Record the execute outcome and decline outcome for every button pair. Use a concrete verb plus only the necessary core object for commitment; name the stable result of declining on the other control.
• Keep labels compact: do not repeat quantities, rationale, and complete consequences in the button. If an object name is long, use a short category and let heading and body disambiguate rather than truncating the core verb.
• Keep visible label and accessible name aligned, placing extra scope in a programmatically associated description. Never rely only on red color, side, or icon to communicate destructiveness.
• Set focus, default action, and Escape or Back behavior according to the platform pattern. Prefer not to make a high-consequence action the target of an incidental Enter, and verify that keyboard, screen reader, voice control, and touch expose both outcomes distinctly and accessibly.

Related

• Same group: T2.06.1 State the specific object and irreversibility scope · T2.06.3 Warning intensity must match actual consequence
• Adjacent: T2.01.1 Button text should describe the specific action that will happen · T2.01.4 Confirm and cancel wording must be opposed and clear
• Search terms: confirm button label · action-specific control · dialog default action