Radio buttons allow users to select exactly one choice from a group.
Radio buttons are a common way to let users know to make a single selection from a list of options. Only one radio button can be selected at a time within the same group. They also spell out each possible choice as its own item, with its own label (whereas checkboxes show a single label and the checking/unchecking of that item means opposite things). For example, if the question was, “Do you prefer blue or red?” the radio button options would be “blue” or “red.”
Users can’t “unselect” a radio button after they’ve selected it. One way to remedy this is to add a “none of the above” option to a radio button group, which essentially allows users to “unselect” a radio button they’ve already clicked on.
When to use the radio button component
- To display a single selection. When users need to select only one option from a set of mutually exclusive choices.
When to consider something else
- Multiple selections. If users need to select more than one option or if there’s only one item to select, use checkboxes instead.
- Limited space. Consider a dropdown if you don’t have enough space to list out all available options.
- Selecting none. If users should be able to select zero of the options or change their mind and unselect an option, consider using checkboxes. You can also choose to add a “none of the above” option to the radio button group instead.
- Use the label as a target. Users should be able to select either the text label or the radio button to select or deselect an option.
- List items vertically. Vertically-listed options are easier to read than those that are listed horizontally. A horizontal layout can make it difficult to tell which label belongs to which radio button.
- Use adequate spacing. Make sure selections are adequately spaced for touch screens. Consider using the tile variant for larger touch targets.
- Set default values with caution. Setting a default value can bias a decision, seem pushy, or alienate users who don’t fit your assumptions. Only use a default selection if you have data to back it up.
- Don’t mix default and tile variants. Pick one implementation and stick with it. When mixed, tiles can appear to indicate a bias or preference toward that option.
- Use a logical order. Make sure the selection options are organized in a meaningful way, like alphabetical or most-frequent to least-frequent. This helps users easily find the option they’re looking for.
- Customize accessibly. If you customize the radio buttons, ensure they continue to meet the accessibility requirements that apply to all form controls.
Use fieldset and legend. Group related radio buttons together with
<fieldset>and describe the group with
Use proper labels and attributes. Each radio button should have a
<label>. Associate the two by matching the
forattribute to the
Radio buttons settings
Tile background color when selected
Tile border radius for rounded corners
Tile border thickness
Tile border color
Tile border color when selected
Radio buttons variants
|usa-checkbox__input--tile||Input tiles provide a larger interaction area and neatly group the label with the form control for readability. They’re useful in application forms and questionnaires, but may not be recommended when they create clutter on the page.|