Provide a clear call-to-action

Send my application

Create an image


Use verbs and describe the action they perform

Use short, descriptive verbs that help users know what action they are about to perform. Using single words is fine if the context of the action is clear.




Avoid ambiguous words on buttons

Ambiguous buttons will not have one obvious action giving the user less confidence.

Avoid using multiple primary buttons

UI with one primary button

Try to use a single call to action on each page/screen

If users need to make a choice you can differentiate from primary buttons with a secondary buttons. Or style it as a link if the choice is less important.

UI with multiple primary buttons

Buttons are for performing actions, not making choices

Having multiple primary buttons creates choice and a lack of clear direction for the user.

Use buttons to guide users through workflows

UI with a primary button on each screen

Primary buttons are great for guiding users through each step of a workflow

Don't hide buttons

UI with button not hidden.png

Make buttons visible

Making the button visible will help set expectations and with a clear call-to-action will give the user context.

UI with button hidden.png

Avoid buttons being revealed

Presenting the primary button only after a set of actions reduces visibility for users. They won't know when they can expect the action or what they are trying to do in that step.

Don't disable buttons

While it is a sure way to stop users from carrying on, it creates a jarring experience.

Users will also lose the ability to click the button to learn if what they entered is right or if they made a mistake.


If you do disable buttons you must provide another way for the user to continue, add an error message or text to explain why the button is disabled.


Google Trends Compare

This website can help you conpare words / terms are trending most


Writing for buttons

This will be a link to the writing guide