6/27/2023 0 Comments Click for more info button![]() When using the active imperative form, avoid instructional terms that tell users how to use their device. It gives them certainty that the button will perform the intended action, which helps their decision-making. Users trust and understand commands on button labels more. All you need to include on your button label is a verb with an adverb or direct object. This form allows you to drop the subject and unnecessary articles for a more concise button label. The active imperative form turns verb phrases into commands. When you use the imperative form in an active voice, you minimize the number of words and make the button label easier to scan. Too many words on a button label make users read more. This button label is clearer and gives users certainty to act. As a result, users get the impression that the app will post their review to the public after they press the button. In contrast, the word “publish” is specific to online publishing. When users read it, it’s unclear what happens because the label is not specific to the task. But that would make the button labels vague and generic. To illustrate, the word “submit” is a technical term you can use for most buttons. Users need to know the result of their actions, and only task-specific language can do this. They’re unsure what the button will do because the label doesn’t specify. ![]() Rule 3: Use Task-Specific LanguageĪ vague and generic button label causes uncertainty in users. The “remove” label is more precise because the action takes the song out of the playlist, but does not destroy it. This diction is wrong because that’s not what happens. In a playlist, the “delete” label makes users think they’ll lose their song. Using these words in the wrong context can cause users concern when they press the button. “Remove” implies that the button will separate the item from a group. “Delete” implies that the button will erase the item from the system. If your diction isn’t precise, users can misinterpret what the button will do.įor example, the words “delete” and “remove” are similar in meaning, but different in connotation. Action verb button labels are more task-efficient.Įach action verb you use has a specific connotation. The button labels with action verbs allow users to take action, but the buttons that use “Yes/No” labels don’t. To illustrate, the example below blocks out the dialog so that only the buttons are visible. Passive labels not only make it riskier to take action, but it forces users to do more work. If they skip or misread the dialog, they’ll press the wrong button. Users have to read the dialog before they can take action. They can take action without reading any supporting text such as confirmation dialog.Ĭompare that with generic “yes/no” button labels often used on confirmation screens. When users read an action verb, they know what the button will do. Your button labels should inspire users to act with action verbs. Follow these five rules, and your users will have no trouble taking the right action on your app whenever they see a button. Here are five rules to help you choose the right words to make your buttons actionable. If you want to make it easy for users to take action on your app, you need to choose the right words on your button labels. Using the wrong words on your button labels cause users confusion, more work, and slower task times. What your buttons say is as important as how they look.
0 Comments
Leave a Reply. |