A button communicates actions users can take with a single click or tap. They are found throughout the interface, typically in dialogues, cards, forms, and modals.



import { Button } from "@twilio-labs/match/components";
const Component = () => (
<Button variant="secondary" size="small" onClick={() => {}}>


variant?ButtonVariant'primary''primary', 'inverse', 'secondary', 'tertiary'
type?ButtonTypenull'button', 'submit', 'reset'
size?ButtonSize'normal''normal', 'small', 'icon'
prompt?booleanfalseShould the button include an animated prompt?
href?stringnullA URL to route to. The button's 'type' attribute will be ignored.
disabled?booleanfalsePrevent actions from firing on the Button.
fullWidth?booleanfalseSets the button width to 100% of the parent container.
download?booleanfalseShould the link trigger a download dialog? Must be used with the 'href' attribute.


About Buttons

The Button component enables users to trigger an event such as submitting a form, opening a modal and confirming or canceling an action. Buttons make it clear what users should do to continue with their main flow. They may be used as CTA's to guide a user through a desired journey.

Prioritize the actions on a page using button sizes and types to clarify which are the most important. If you have many actions, consider using button links to offer less important ones.


Here are some quick accessibility tips to ensure a positive user experience for all users.

  • Choose button text that clearly describes the action that is about to happen
  • Use anchors that look like buttons sparingly. Voice dictation users may encounter issues when trying to activate them. A user may say, “Click the read more button”, but the dictation software won’t respond since it can’t tell what the anchor looks like visually. Use an alternative where possible, such as an anchor with an icon or with a larger font size.
  • Avoid using only color to communicate information. Use another indicator such as an icon or button copy for users to be certain of the action and the next step.
  • Avoid small font sizes and blinking / moving text within the button. Font sizes also affect whether it meets AA / AAA under WCAG guidelines.
  • The area for clicking and tapping the button must have enough space within and around the button for usability on all devices.


Use a button to indicate that users can trigger an action.

In general, align buttons to the direction of the text (e.g., left-aligned in English) for easy scanability.

When moving customers through a sequence, place the primary button in the direction of the movement (e.g., a “Next” button goes on the right in an English-language flow).



Primary buttons indicate the most important action a user may take on the current screen.


Secondary buttons indicate a recommended action for a user, but is not the most important one available on the current screen.


Tertiary buttons are used for actions that are not as equally important in the user experience. They are used in cases where the secondary button is not accessible due to the background color, such as darker colors.


Inverse buttons are formatted for use on top of various background colors, where the hover and active state of the primary or secondary buttons may clash against the background.


All variants support the animated prompt icon.


Disabled buttons will not receive any click events. It should be obvious to the user why the button might be disabled (e.g. it follows an empty text field).

Text and Icon

Buttons of any variety and size may include an icon from one of the Match icon libraries. Always place icons to the right of the button text.

Icon Only

Icon only buttons must use the icon size, but may be used with any variant. Be sure to include a descriptive title for your icon.