# Toggle, Checkbox, and Radio Button

Toggles, checkboxes, and radio buttons represent different choice models: immediate binary state, independent selections, and one selection from a mutually exclusive group.

- Type: framework
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/toggle-checkbox-and-radio-button/>)

## What it means

A toggle or switch changes one on/off setting, often immediately. A checkbox selects an independent option and may be part of a multi-select group; it can also represent a mixed aggregate state. A radio button chooses exactly one option from a labeled group.

## Why it matters

Matching the control to the decision makes consequences and selection rules predictable. The wrong pattern can obscure whether a choice takes effect immediately, whether several options are allowed, or whether submission is still required.

## When to use it

Use a toggle for an immediate on/off setting, checkboxes for zero or more independent choices, and radio buttons for one required or optional choice among a small visible set. Use a select when a mutually exclusive list is too long to display comfortably.

## How it works

1. Define the choice cardinality, default, optionality, and whether changes apply immediately or on submission.
2. Choose the control whose established behavior matches that model.
3. Use persistent, specific labels and a group label where choices share a question.
4. Expose checked, mixed, disabled, invalid, and focus states through native controls when possible.
5. Test keyboard operation, touch targets, zoom, error handling, and changes that trigger costly effects.

## A practical example

Notification settings use a toggle for turning all notifications on immediately, checkboxes for independently choosing email and push channels, and radio buttons for selecting one digest frequency. The labels explain effects without relying on color or position.

## Where it breaks

Platform appearance varies, and a toggle can be confusing when a save action delays the change. Preselected choices may bias decisions, while large option groups become difficult to scan regardless of control type.

## Common mistakes

- Using checkboxes when only one option may be selected.
- Using a toggle for an action rather than a persistent binary state.
- Requiring a separate Save button for a switch that visually implies immediate effect.
- Writing labels such as “On” without naming what is on.

## Sources

1. [Checkbox Pattern](<https://www.w3.org/WAI/ARIA/apg/patterns/checkbox/>) — W3C Web Accessibility Initiative · Technical guidance
2. [Radio Group Pattern](<https://www.w3.org/WAI/ARIA/apg/patterns/radio/>) — W3C Web Accessibility Initiative · Technical guidance
3. [Switch Pattern](<https://www.w3.org/WAI/ARIA/apg/patterns/switch/>) — W3C Web Accessibility Initiative · Technical guidance

## Related topics

- [Interaction State](<https://wiki.soroush.uk/topic/interaction-state/>)
- [Form Validation](<https://wiki.soroush.uk/topic/form-validation/>)
- [Touch Target](<https://wiki.soroush.uk/topic/touch-target/>)
