Confirm and cancel wording must be opposed and clear

What it is

Outcome-opposed dialog actions state the result of each button and make the pair distinguishable, such as “Keep draft / Discard draft.” Users should not parse a negative question and then infer whether “Yes” confirms or reverses the negation. Opposition concerns outcomes, not visual left and right: focus, default action, order, and the close icon must not silently change the wording's promise.

Why it happens

“Don't save changes?—Yes/No” requires users to track negation, map an answer to an action, and resist default-focus or position habits, all while possibly distracted. Direct result labels bind each choice to an end state and allow a final check at the control. Keyboard Enter behavior, screen-reader order, mobile stacking, and platform primary-button positions vary, so color, side, or focus creates another hidden language. A close icon also has behavioral semantics: if it means cancel, keep, or discard, it must agree with the corresponding path.

Studying it

Test the actual heading, body, button order, and keyboard or screen-reader behavior. Before activation, ask users to restate both results. Swap visual position, remove color, change focus, and introduce unsaved state to see whether choices remain stable. Record the resulting state after the close icon, Escape, back gesture, and scrim click, verifying that alternate exits do not contradict the pair. Dedicated confirmation research adds safeguards for high-risk errors.

Where it stops holding

“Cancel” fits a path that truly aborts the pending action and preserves the state from before the dialog. If dismissal loses input, stops work, or retains partial changes, use a specific result label. A pure notice may have one “Got it” action; it needs no artificial opposition. Platforms may prescribe order or default focus, and products should respect those interaction conventions, but wording still stands on its own. Objects, scope, and stronger friction for irreversible actions belong to high-risk confirmation rules.

Applying it

• Rewrite the question as an unambiguous state statement, then label each path with action plus object or end state. Avoid double negatives such as “Don't cancel” and “Yes, don't keep.”
• Maintain one outcome table for visible buttons, default focus, Enter, Escape, close icon, back, and scrim click. No implicit path may cause an undisclosed destructive result.
• Do not use left/right position, primary color, or a “recommended” mark as a substitute for wording. Name the destructive result; place default focus on the safe path allowed by the organization's risk model.
• After localization, regress both results and every exit with keyboard, touch, and screen reader. If either label is interpreted as the opposite end state, rewrite the whole question–answer set rather than only swapping order.

Related

• Same group: T2.01.1 Button text should describe the specific action that will happen · T2.01.2 Generic words prevent users from predicting outcomes · T2.01.3 A button and its context form the sentence together
• Adjacent: T2.06.2 Buttons must restate the action, not say OK · T2.06.1 State the specific object and irreversibility scope
• Search terms: dialog button pair · double negative · dismiss behavior