Radio and RadioGroup components let you present a set of mutually exclusive options so the user can pick exactly one. Both are Status: Draft and are backed by Mantine’s Radio primitive. Clementine exports them directly from @clementine-ds/ui with the Clementine theme applied.
When to use
- You need to let the user select one and only one option from a small, fixed set (typically 2–6 items).
- All options should be visible at once — no scrolling, no searching.
- The choice requires clear visual separation between options (radio circles make mutually exclusive semantics obvious).
When not to use
- Non-exclusive selection — use
Checkboxinstead so the user can pick multiple items. - Many options (more than ~6) — use
Selectto keep the interface compact. - A single on/off toggle — use
Switch, which communicates binary state more clearly.
Usage
Import bothRadio and RadioGroup from @clementine-ds/ui. Wrap individual Radio items inside a RadioGroup to wire up accessible group semantics, keyboard navigation, and shared controlled state.
Uncontrolled group
Controlled group
Disabled state
Props
Radio
RadioProps extends Mantine’s RadioProps, which itself extends the native <input type="radio"> element. All standard HTML input attributes are forwarded to the underlying input.
RadioGroup
RadioGroupProps extends Mantine’s RadioGroupProps.
Interaction states
Accessibility
- Each
Radiorenders a native<input type="radio">, which provides full browser and assistive-technology support out of the box. - Wrapping radios in
RadioGroupaddsrole="radiogroup"andaria-labelledbypointing at the group label. - Arrow keys move focus between options within the group.
Tabmoves focus out of the group. - Always provide either a
labelprop or anaria-label/aria-labelledbyattribute on eachRadio. An unlabeled input will not be announced correctly by screen readers. - When you use
RadioGroup, set thelabelprop on the group — it becomes the accessible name for the entireradiogroupregion.