When to use this component
Use the button component to help users carry out an action like starting an application or saving their information.
How it works
Write button text in sentence case, describing the action it performs. For example:
- ‘Start now’ at the start of the service
- ‘Sign in’ to an account a user has already created
- ‘Continue’ when the service does not save a user’s information
- ‘Save and continue’ when the service does save a user’s information
- ‘ Save and come back later’ when a user can save their information and come back later
- ‘Add another’ to add another item to a list or group
- ‘Pay’ to make a payment
- ‘Confirm and send’ on a check answers page that does not have any legal content a user must agree to
- ‘Accept and send’ on a check answers page that has legal content a user must agree to
- ‘Sign out’ when a user is signed in to an account
You may need to include more or different words to better describe the action. For example, ‘Add another address’ and ‘Accept and claim a tax refund’.
Align the primary action button to the left edge of your form.
Use a default button for the main call to action on a page.
Avoid using multiple default buttons on a single page. Having more than one main call to action reduces their impact, and makes it harder for users to know what to do next.
Use a start button for the main call to action on your service’s start page. Start buttons do not submit form data, so they use a link tag rather than a button tag.
Use secondary buttons for secondary calls to action on a page.
Pages with too many calls to action make it hard for users to know what to do next. Before adding lots of secondary buttons, try to simplify the page or break the content down across multiple pages.
You can also group default and secondary buttons together.
Warning buttons are designed to make users think carefully before they use them. They only work if used very sparingly. Most services should not need one.
Only use warning buttons for actions with serious destructive consequences that cannot be easily undone by a user. For example, permanently deleting an account.
When letting users carry out an action like this, it’s a good idea to include an additional step which asks them to confirm it.
In this instance, use another style of button for the initial call to action, and a warning button for the final confirmation.
Do not only rely on the red colour of a warning button to communicate the serious nature of the action. This is because not all users will be able to see the colour or will understand what it signifies. Make sure the context and button text make clear what will happen if the user selects it.
Disabled buttons have poor contrast and can confuse some users, so avoid them if possible.
Only use disabled buttons if research shows it makes the user interface easier to understand.
Use a button group when two or more buttons are placed together.
Any links within a button group will automatically align with the buttons.
Stop users from accidentally sending information more than once
Sometimes, users double click buttons because they:
- have used operating systems where they have to double click items to make them work
- are experiencing a slow connection which means they are not given feedback on their action quickly enough
- have motor impairments such as hand tremors which cause them to click the button involuntarily
In some cases, this can mean their information is sent twice.
If you are working in production and research shows that users are frequently sending information twice, you can configure the button to ignore the second click.
In the case of slow connections, aim to give the user information about what’s happening, for example, by showing a loading spinner or a modal, before ignoring the second click.