Use buttons to signal actions.
Default Button
Primary Button
Success Button
Transparent Button
Button Size Variations
Inverse Buttons
Danger Button
Deprecated
Do not use.
Button icons
- Add an inline SVG icon and it will become the same color as the button text. For the crispest icon rendering, ensure the icon has a square
viewBoxwith values that are multiples of8(ie.24x24). - Use the margin utility class to add spacing between the icon and button text.
Button inline with field
The button is the same height as a single-line text field.
<Button>
The Button component accepts its text as children (AKA inner HTML), which
means you can also pass in HTML or custom components. This gives you a lot of
flexibility and supports a variety of advanced use cases. The most common use
case would be passing in an SVG icon along with the text.
In addition to the supported props listed, you can also pass in additional
props, which will be passed to the rendered root component. For example,
you could pass in a target prop to pass to the rendered anchor element.
Code snippet
Props
| Name | Type | Default | Description |
|---|---|---|---|
analytics | boolean | Analytics events tracking is enabled by default. Set this value to | |
analyticsLabelOverride | string | An override for the dynamic content sent to analytics services. By default this content comes from the heading. In cases where this component’s heading may contain sensitive information, use this prop to override what is sent to analytics. | |
analyticsParentHeading | string | If needed for analytics, pass heading text of parent component of button. | |
analyticsParentType | string | If needed for analytics, pass type of parent component of button. | |
childrenrequired | string | React.ReactNode | Label text or HTML | |
className | string | Additional classes to be added to the root button element. Useful for adding utility classes. | |
disabled | boolean | ||
href | string | When provided the root component will render as an | |
inputRef | MutableRefObject<any> | ((...args: any[]) => any) | Access a reference to the | |
inversed | boolean | Applies the inverse theme styling | |
onClick | (...args: any[]) => any | Returns the | |
size | 'small' | 'big' | ||
type | React.ComponentProps<'button'>['type'] | 'button' | Button |
variation | 'primary' | 'danger' | 'success' | 'transparent' | A string corresponding to the button-component variation classes.
The |
Guidance
When to use
- Use buttons for the most important actions you want users to take on your site, such as "Download," "Sign up," or "Apply."
When to consider alternatives
- Less popular or less important actions may be visually styled as links.
- Buttons are for performing actions, not making choices. If you need your users to make a choice, use something else like radio buttons. Alternatively, if one choice is much less important then try styling it as a link instead.
Usage
- Use the "primary" button variation for the button most users should click. This is your primary call-to-action.
- Avoid using too many buttons on a page. Aim to use only one button per page.
- Avoid similar styles elsewhere on the page that could be confused for buttons.
- Use buttons for the primary action and links for secondary actions.
Label text
- Use sentence case for button labels.
- Button labels should be as short as possible with “trigger words” that your users will recognize to clearly explain what will happen when the button is clicked (for example, “Save and continue,” “Download” or “Sign up”).
- Make the first word of the button’s label a verb. For example, instead of “Complaint Filing”, label the button “File a complaint.”
- If a button has an icon, it should still have accompanying text describing the action.
Destructive buttons
- Use the "danger" button variation for destructive buttons. For example, buttons that delete or reset a user's information.
- Confirm the user meant to trigger a destructive action before following through with the action.
- Provide a method for a user to undo a destructive action.
Disabled buttons
- Don’t disable buttons, unless there’s a good reason to.
- If you do disable a button, make sure it receives the disabled styling. A
buttonelement will automatically be styled as a disabled button when it has thedisabledHTML attribute, but anaelement will need to have the.ds-c-button--disabledclass applied to it.
Accessibility
- Buttons should display a visible focus state when users tab to them.
- Create a button with a
buttonoraelement to retain the native click functionality. Avoid using<div>or<img>tags to create buttons. Screen readers don't automatically know either is a usable button. - When styling links to look like buttons, remember that screen readers handle links slightly differently than they do buttons. Pressing the
Spacekey triggers a button, but pressing theEnterkey triggers a link. - Dimmed or unavailable buttons should have the
disabledattribute applied. This removes native click and keypress events from the button. It also prevents automated scanners from logging a low contrast error. Finally, it announces the button as "dimmed" or "disabled" to screen readers, offering users additional context.
Learn more
- Beyond Blue Links: Making Clickable Elements Recognizable
- 7 Basic Best Practices for Buttons
- The Grammar of Interactivity
- GOV.UK navigation buttons discussion
Button alignment
ARIA
Google Analytics
Analytics event tracking is disabled by default.
Enable event tracking
Import and set the setButtonSendsAnalytics feature flag to true in your application's entry file:
import { setButtonSendsAnalytics } from '@cmsgov/<design-system-package>';
setButtonSendsAnalytics(true);
On applications where the page has utag loaded, the data goes to Tealium which allows it to route to Google Analytics or the currently approved data analytics tools.
Disable event tracking
For the analytics prop, pass the value false to the component to disable analytics tracking for a singular component instance
analytics={false}
Override event tracking
A custom heading value can be sent for an analytics event by using the prop analyticsLabelOverride. It is recommended that this value be used to prevent sensitive personal information from being passed to analytics trackers.