12

Button labels: is “OK” ok?

 11 months ago
source link: https://uxdesign.cc/button-labels-is-ok-ok-e4b47298cc8a
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Button labels: is “OK” ok?

Buttons are amongst the most important interactive design elements that allow users to manipulate the interface. There are many great articles dedicated to their appearance, yet surprisingly little guidance on their content — labels.

Published in
5 min read1 day ago

I’d like to preface this article with a note that the following principles should be used as guidelines, not rules. Language changes in response to its context and evolves over time, so trust your instincts, stay consistent and test extensively!

Light, camera, action!

A button is an interactive element that changes the state of the interface (if it doesn’t, it’s should likely be a link). For this reason, its label should include a verb that clearly describes the action it performs.

Large button with a label “Let’s go!”

Rule of thumb: a button label should include a verb.

Let’s now look at some of the most common actions and the best button labels for them.

Confirmation

By clicking the button, the user confirms that they familiarised themselves with the information and accept its message. The most common labels for this are:

  • Accept
  • Agree
  • Confirm

The choice will depend on your tone of voice, as well as the formality of the agreement.

Two modals: first titled “Agree to terms and conditions?” with a call-to-action “Agree”; second titled “Are you sure you want to proceed?” with a call-to-action “Confirm”.

“Accept”, “Agree” and “Confirm” can often be used interchangeably, but the first two are more common in formal agreements.

Conversely, you may need to give the user an option to “Disagree” and label the button accordingly. However, since the progress often relies on the user agreeing to whatever information they are given, it is more common to pair the confirmation button with labels like:

  • Cancel
  • Dismiss
  • Go back
Two modals: first titled “Agree to terms and conditions?” with two calls-to-action “Agree” as the primary and “Disagree” as the secondary; second titled “Are you sure you want to proceed?” with two calls-to-action “Confirm” as the primary and “Cancel” as the secondary.

If the user can’t proceed without agreeing, it’s better to use a label that clearly explains the consequences of their disagreements, such as “Cancel” or “Go back”.

One notable exception is the “OK” button, which is often used to dismiss modals. This label is ambiguous, since it lacks an action word, so it’s not always…


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK