# Input Radio: Single-Choice Groups Users Can Scan, Use, and Trust

> How to define one shared radio group component with clear parts, states, keyboard behavior, and usage rules.

**In short:** A radio group is a shared component for picking one option from a set, defined with clear parts, states, keyboard behavior and usage rules.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/input-radio

## What You Will Learn

This lesson shows you how to define Input Radio, a shared design system part that lets people choose exactly one option from a short list they can see at once. You will learn when to use it, which parts it is made of, which states it needs, and which rules keep it easy to use on every screen.

A design system is a shared set of parts and rules. Input Radio is one of those parts. Teams write it down once so every product uses it the same way, instead of each designer drawing a new version.

- **Input Radio:** A form control where the person picks one option from a group. Think of it as a round button for choosing one thing.
- **Radio group:** The full set of related radio options, plus the label that says what they are for.
- **Mutually exclusive:** Only one choice can be true at a time. Picking one choice removes the others.
- **Checkbox:** A small square box that lets people pick many options, or none.
- **Toggle:** An on-or-off switch for one setting.
- **Dropdown:** A box that opens into a list, so a long list can hide behind one closed box.
- **Component:** A reusable part, built once and placed on many screens.
- **Anatomy:** The list of parts a component is made of.
- **State:** How a component looks and behaves at one moment, such as when it is chosen or unavailable.
- **Variant:** A named version of the same component, such as a vertical or horizontal layout.
- **Helper text:** A short hint under a label that explains the choice.
- **Focus:** A visible marker that shows which control the keyboard is on right now.
- **Tap target:** The area that responds when someone clicks or taps.
- **Design token:** A named design decision, such as a colour or a gap size, stored once and reused everywhere.

## When is a radio group the right choice?

Choosing the control is the first decision, and it is often where teams go wrong. A radio group fits when three things are true. The list is short, every option should be visible, and exactly one choice must be made.

- **Short list:** Aim for roughly two to six options. One design system uses five options or fewer as its limit for radio buttons, while another switches to a dropdown once a list passes seven options. The sources disagree, so your team should pick one limit and write it down.
- **All options visible:** People should be able to compare every choice at once. Orange advises showing every option when people need to see them all. If the options can be collapsed, a dropdown saves more space.
- **Exactly one answer:** A radio group must end with one answer. Picking a second option moves the mark away from the first, so a person can never hold two picks. When the user selects another option, the previous selection is automatically deselected.

Hold one detail in mind: the rule is about the answer, not the screen. If a person might want two answers, the control is wrong even when the list is short.

Radio groups are often mixed up with other controls. Checkboxes are the right pick when several answers can be true at once. GOV.UK puts it simply: do not use the radios component if users might need to select more than one option, and use Checkboxes instead. A toggle suits a setting that takes effect right away. ServiceNow suggests a toggle when you want the change to take place immediately. A dropdown is a comparison point here only, because long lists get their own lesson.

Yes or no questions are a grey area. Michelin says not to use radio buttons for yes or no choices and to use a checkbox instead. The Intelligence Community design system allows two-option groups to be shown as a stack or in a row. Pick one rule for your team and document it.

**Quick check:** A shipping form asks which extras a customer wants: gift wrap, insurance, and engraving. The customer may pick none, one, or all three. Which control fits best?

A. A radio group, because it is always the safest choice
B. Checkboxes, one for each extra
C. A dropdown with one choice that the customer can open
D. A single toggle that turns all three extras on together

**Answer:** B. More than one extra can be chosen at once, and a radio group allows only one answer. Separate checkboxes let each extra be switched on or off on its own.

## What are the parts of the component?

Anatomy means the list of parts a component is made of. Naming each part in your documentation makes it easy for every team to build the same thing and get the same result.

- **Group label:** The question the options answer, such as Delivery speed. Assistive technology needs a group label so it can tell users what the group is for. Assistive technology means software, such as a screen reader, that reads the page aloud. Some systems mark the group label as optional, so write your own rule.
- **Helper text:** A short hint under the label that explains the choice. Radio button groups can display hint text.
- **Error text:** A message that tells the person what to fix. Radio button groups can display an error message, and the message can give guidance on what information is required.
- **Radio control:** The round mark the person clicks. When the option is chosen, a filled circle appears in the radio button to show that the user has selected it.
- **Option label:** The words for one choice. Keep the label short and positive, so people understand that checking it activates that option. A label can also carry a second line, such as a price or a date, if the example needs it.

Define these parts once, and then the team can reuse them. A new screen should not need a new kind of radio.

Layout is a variant, and sources do not agree on it. GOV.UK places each radio to the left of its label to help people using screen magnifiers find it. Emplifi places its labels on the right. These differences are real, so your team needs one decision, written down.

> **Tip:** Set one default layout: vertical for three or more options, and a row only for two-option groups. Also write where labels sit. Teams that skip this often end up with two versions of the same component.

## What are the states and variants?

A state is how a component looks and behaves at a given moment. A complete radio group needs the states below. Each one must look different from the others, so people always know where they are.

- **Default:** Nothing has been chosen yet, or the component shows its starting look. The unselected view is the starting state for a radio button.
- **Hover:** The look changes when a mouse pointer rests on an option. Design system blueprints list hover as its own state, alongside focus, pressed, and disabled.
- **Focus:** A visible marker that shows which option the keyboard is on. Radio buttons have their own states for focus and for being disabled. Focus is not the same as choosing. The keyboard can rest on an option that is not yet chosen.
- **Selected:** The option the person has chosen. Use a clear shape change, not only a new colour. The chosen option is the only one filled in.
- **Disabled:** The option is shown but cannot be chosen. Disabled means the radio button is not interactive. Explain in helper text or nearby copy why it is unavailable.
- **Error:** The group needs attention before the person can continue. The error state shows when there is an issue with the selection. One system also changes the group label and the radio buttons to red. Red alone is not enough, as explained later in this lesson.

A variant is a named version of the same part. Name each variant in your library, so teams do not invent their own versions.

- **Vertical stack:** The standard form. Each option sits on its own line, with the label beside its circle.
- **Horizontal row:** Use only for two-option groups where the options are easy to read at a glance. Do not use it for a yes or no pair, which should use a checkbox.
- **With helper text:** Adds one hint line under the group label for context.
- **With description:** Each option has a second line of detail, such as a price or an arrival date. Radio buttons can be used in tiles, list items, dialogs, and forms.

## What design decisions make radios consistent and usable?

Once the parts and states are named, the next step is to write down the decisions that keep every radio group the same. Four decisions matter most: keyboard behavior, a large click area, cues that do not rely on colour, and design tokens.

### How should the keyboard work?

Some people use only a keyboard, so the group must work without a mouse. Document three rules: the Tab key brings focus into the group, arrow keys move between options, and a further Tab leaves the group. Pressing Tab moves focus to a radio button in the group, arrow keys move focus among the buttons, and Tab moves focus out to the next element.

1. **Enter with Tab:** Focus lands on the chosen option. If nothing is chosen, focus lands on the first option. If a radio button is checked, focus goes to it; if none is checked, focus goes to the first radio button in the group.
2. **Move with arrows:** Down and Right move to the next option. Up and Left move back. From the last option, focus wraps to the first, and from the first it wraps to the last. In the reference example, the arrow key also chooses the option it lands on. Some teams prefer that the Space key does the choosing instead. Space checks the focused radio button if it is not already checked.
3. **Leave with Tab:** A further Tab moves focus out of the group to the next control. Focus should never get stuck inside a group.

Write your choice clearly. Teams often disagree on whether arrows choose or only move, so the rule belongs in the documentation, not in each designer's head.

### A Large Clickable Target

The circle is small, so the whole row should respond to a click or tap. Make the tap target include the label, because using only the small radio as the target is frustrating. Clicking or tapping the label should select the option. A small hit area is also harder for some people. Smaller radios and checkboxes are harder for some people to use because the hit area is smaller. Picking an option should change only the choice, never send the person to another page. Selecting a radio should never navigate users somewhere new.

> **Tip:** Write the clickable area as a rule, such as 'the circle and its label, across the full row', instead of a vague instruction to make it big.

### Focus and Selected Marks Beyond Color

Colour alone is not enough. Some people cannot tell colours apart, and some use high contrast settings. GOV.UK's new radios take the colour of the text and use a transparent background, which works better for people who change their browser's default colours or use high contrast themes. Give the selected option a filled shape, as already described, so the state still shows without colour. Give focus a clear outline, not only a faint tint. Give errors written text, because using error messages also follows best practice guidance for accessible interfaces.

### Design Tokens for Size, Color, and Spacing

A token is a named design decision stored once and reused. For radios, name tokens for the circle size, the tap area, the text and border colours, the focus outline colour, and the gaps between options and between a circle and its label. GOV.UK's component takes the gap below each option from a shared spacing scale. Tokens let a brand change in one place, and every radio group follows.

> **Tip:** Name tokens by their job, such as focus outline or gap between options. Do not name them by value, such as blue or a number. A value name becomes wrong the moment the brand changes.

### Defaults and Required Choices

Sources disagree on defaults. Emplifi also preselects one option by default. GOV.UK advises against pre-selecting radio options. The CMS design system warns against radios on optional questions, because once a radio button is selected from a list, it or another choice will remain selected. GOV.UK notes the same limit: once a user has selected an option, they cannot go back to having no option selected without refreshing the page.

Our rule: preselect an option only when one choice is a clearly sensible starting point that the person does not need to weigh. If the choice is personal, leave it empty and mark the group as required. If an answer is optional, add a None option, which Michelin suggests when people need a way to skip the selection.

## Worked Example: Delivery Speed at Checkout

Picture a shipping step at a checkout, such as the ones used by large shops. Treat this example as a model to build, not a description of any one site. Imagine a delivery speed group with three options: Standard, Express, and Next-day. Each row shows a price and an arrival date.

1. **Set the question:** Write the group label as Delivery speed. Add helper text such as Arrival dates depend on your address. The label tells every user, including screen reader users, what the group is for.
2. **Check the fit:** Three options sits inside the two-to-six range. All three should be visible so people can compare price and date. Exactly one choice is needed to continue. So a radio group is the right control.
3. **Set the default:** Standard is a common starting point, so the team can preselect it. If the team wants people to think about speed, it can leave all three empty and mark the group as required.
4. **Show the selected state:** When Express is chosen, its circle fills in and its row gets a clear outline. The change does not depend on colour alone.
5. **Show focus:** When someone tabs into the group, a visible focus outline sits on the chosen option. The Down and Up arrows move the outline between the three rows.
6. **Handle the disabled option:** Next-day is not offered to a remote address. Its row looks muted and cannot be chosen. The helper text explains why, such as Not available to this address.
7. **Handle the error:** If someone presses Continue with nothing chosen, the group label takes the error style and a message says Choose a delivery speed to continue. One component shows every state here. The screen only passes in the options and their status.

> **Tip:** Keep the price and date inside each option's row, not as separate controls. That way the tap area covers everything the person reads, and the keyboard meets only three stops.

## Documenting the Component

A component is reusable only when other people can read its rules without asking you. Write a usage page that covers when to use it, when not to use it, its anatomy, its states, keyboard behavior, and content rules.

- **Write the rules:** State the option limit, the one-answer rule, the checkbox alternative, and your layout and default decisions.
- **Show good and bad examples:** Pair each rule with one correct screen and one incorrect screen, so readers can see the difference.
- **Set content rules:** Keep labels short and positive. Do not use radios to run an action. Michelin says not to use radio buttons to perform commands or actions.

## Check Your Understanding

**Quick check:** A settings screen needs a user to choose a language from a list of 30 options. A separate screen asks users to choose either Monthly or Yearly billing. Which control suits each screen, and why is a radio group right for only one of them?

A. A radio group for both, because each screen needs exactly one choice
B. A dropdown for language and a radio group for billing
C. Checkboxes for both, so users can change their mind later
D. A toggle for both, because each choice has two states

**Answer:** B. Thirty options are too many to show at once, so a dropdown hides them in one box. Monthly and Yearly are two visible options with exactly one chosen, which is the job of a radio group.

**Quick check:** A radio group has Standard, Express, and Next-day. Express is chosen. A user tabs into the group and then presses the Down arrow twice. Where does focus land?

A. On Express, because the chosen option keeps focus
B. On Next-day, because it is the last option
C. On Standard, because the arrows wrap past the last option
D. Outside the group, because the second arrow leaves it

**Answer:** C. The first Down arrow moves focus from Express to Next-day. The second moves past the last option and wraps back to the first, Standard. Only Tab leaves the group.

## Summary

Input Radio lets people choose exactly one option from a short, visible list. Define it once. Say when to use it, name its parts and states, choose one layout, write the keyboard rules, make the click area include the label, show selection with shape as well as colour, and store size, colour, and spacing as tokens.

> **Tip:** Before you publish a radio group, check three things: the option count is within your limit, exactly one answer is needed, and every state can still be told apart with no colour.

## Sources

- [Carbon Design System, Radio button usage](https://v10.carbondesignsystem.com/components/radio-button/usage/)
- [Uber Base Design System, Radio](https://base.uber.com/6d2425e9f/p/0982fd-radio/b/0223ca)
- [ServiceNow Horizon Design System, Radio buttons](https://horizon.servicenow.com/components/now-radio-buttons)
- [Michelin Design System, Radio button](https://designsystem.michelin.com/components/radio-button)
- [GOV.UK Design System, Radios](https://design-system.service.gov.uk/components/radios/)
- [GOV.UK Technology blog, Improving forms with new radios and checkboxes](https://technology.blog.gov.uk/2016/12/13/improving-forms-with-new-radios-and-checkboxes/)
- [UK Parliament Design System, Radio buttons](https://designsystem.parliament.uk/forms/radio-buttons/)
- [Intelligence Community Design System, Radio button](https://design.sis.gov.uk/components/inputs/radio)
- [Orange Design System, Radio buttons](https://system.design.orange.com/0c1af118d/v/latest/p/79b010-radio-buttons)
- [Emplifi Soul Design System, Radio button usage](https://soul.emplifi.io/latest/components/components/radio-button/usage-PbkzvgqT)
- [CMS Design System, Radio](https://design.cms.gov/components/radio/)
- [Design Systems Surf, Radio Button Blueprints](https://designsystems.surf/blueprints/radio-button)
- [W3C WAI-ARIA Authoring Practices 1.1 (Note, 2017)](https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/)
- [WAI-ARIA Authoring Practices 1.1 mirror, Radio Group keyboard section](https://bocoup.github.io/aria-practices/aria-practices.html)
- [W3C WAI-ARIA Authoring Practices 1.2, Radio Group Example](https://www.w3.org/TR/2021/NOTE-wai-aria-practices-1.2-20211129/examples/radio/radio.html)
- [GOV.UK Design System backlog, Smaller checkboxes and radio buttons issue](https://github.com/alphagov/govuk-design-system-backlog/issues/162)
