← Back to Catalog

OK/Cancel default vs explicit verb

ok-cancel-default-vs-explicit-verb

OK / Cancel as Ant default labels (CONFLICT). Spec still defaults to OK/Cancel but also: use a verb; describe the result (Publish, Login); if primary is negative, stress consequences (Delete / Cancel). Dual-cite vs NN/g `explicit_verb_not_ok`. Do not pick a winner. Prefer cited verb-names-the-outcome as pass when both apply; Ant default is a conflict flag, not a second invented rule.

Description

Ant’s button spec still defaults to OK/Cancel while also telling authors to use a verb that describes the result (Publish, Login) and, when the primary is negative, to stress consequences (Delete / Cancel). Dual-cite NN/g explicit-verb-not-ok; do not pick a winner. When both cites apply, prefer the outcome-naming verb as the pass; treat Ant’s OK/Cancel default as a conflict flag, not a second invented rule. Fail generic OK treated as satisfying the verb cite, or a house always/never that deletes the other cite.

When to use

Labeling dialog or form primary and cancel actions under Ant.

Not when

House rules that always ban OK or always require OK/Cancel only.

Agent hint

Prefer a verb that names the outcome; flag OK/Cancel as the Ant conflict.

Pass

When both cites apply, the primary names the outcome (Publish, Login, Delete); if primary is negative, the pair stresses consequences (Delete / Cancel).

Fail

Generic OK where a specific verb is available and treated as satisfying the verb-names cite; or a house "always OK/Cancel" / "never OK" that deletes the other cite.

Citations

Ant Design — Button spec

https://ant.design/docs/spec/buttons

Open UX · cited UX rules agents audit against

Privacy · Sources ·