| Table of Contents |
|---|
...
The radio will have an hovered/active state when hovering/clicking both the radio or the label describing it.
Validations and errors
Please refer to Field validation page for more information.
...
Best practices
List options in a logical order:
Most likely to least likely to be selected.
Simplest to most complex operation.
Make the most likely or convenient radio button option the default.
If you need to have an unselected state, add a radio button with a None option.
If you can't have a comprehensive list of all possible options, add an Other option.
Try to align radio buttons vertically instead of horizontally, especially for long labels. Horizontal alignment is harder to read and localize.
Use a radio button when the options being presented are important enough to occupy more screen space.
They should only be used if the user needs to see all available options instantly and side by side.
Do not use a radio button if:
You need to offer the user the option of multiple selection. In this case, use checkboxes instead because radio buttons are for single-selection contexts only.
The default option is recommended for most users in most situations. In this case, consider a dropdown list instead, which uses less space by not showing all options straightaway.
You need to present more than 8 options. Use a dropdown menu.
In special cases, there are only two mutually exclusive options. Combine them into a single checkbox or toggle switch. For example, use a checkbox for “I agree” (for example, to terms and conditions) instead of two radio buttons for “I agree” and “I don’t agree”.
The options are numbers with fixed steps. Use a slider.
...
Zeplin link | Screen thumbnail |
|---|---|
  |
Current appearances in our products
...