InputsComponentBeta

Radio Group.

One clear answer from a set of choices.

RadioGroup owns the selected value and native radio navigation. Each labeled Radio.Root owns its visual settings. The group orientation controls layout; radios remain circular and unchecked choices stay neutral.

Make it yours

Preparing the example…

PROPERTIES6

Composition

Anatomy

RadioGroup owns the selected value and native radio navigation. Each labeled Radio.Root owns its visual settings. The group orientation controls layout; radios remain circular and unchecked choices stay neutral.

Component structure
RadioGroup (accessible name, value, disabled)
└── label
    ├── Radio.Root value=plan
    │   └── Radio.Indicator (decoration)
    └── Plan label

A place to start

Usage

Import the stylesheet once at your application root. This complete example reflects the properties selected above.

Loading example…

Details that make a difference

Examples & states

Sizes

Compare the three Dixy shirt sizes side by side.

Example loads as it comes into view.

Loading source…

Visual treatments

Emphasis changes presentation while the primitive keeps behavior.

Example loads as it comes into view.

Loading source…

Semantic colors

Semantic color supplements the selected state or measurement.

Example loads as it comes into view.

Loading source…

Materials

Optional static finishes use the same public component. Import materials.css in your application.

Example loads as it comes into view.

Loading source…

Orientation

The owning primitive controls layout and keyboard behavior as documented above.

Example loads as it comes into view.

Loading source…

The finer details

API reference

Generated from Dixy’s local TypeScript interfaces. Native and Base UI RadioGroup props are forwarded; this table covers the options Dixy adds.

RadioRoot

PropType / descriptionDefault
size"sm" | "md" | "lg"

Component proportions; preserves the shared interaction target.

md
variant"soft" | "solid" | "outline"

Visual emphasis; behavioral state remains primitive-owned.

solid
color"neutral" | "accent" | "danger" | "success"

Semantic emphasis; unselected controls remain neutral.

accent
material"matte" | "glossy" | "soft" | "metal" | "paper"

Optional static finish; import materials.css.

Theme.material

RadioGroup

PropType / descriptionDefault
orientation"horizontal" | "vertical"

Visual layout; native radio keyboard behavior is unchanged.

vertical
Explore the full Base UI API

Built from the same foundations

Styling tokens

Change Theme settings above to compare appearance, accent, neutral, radius, spacing density, motion and direction. Override component aliases on a Theme root so custom properties follow portaled content too. The wrapper merges className, style, refs and render composition with its owning primitive.

TokenPurpose
--dixy-choice-sizeThe component-specific starting point.
--dixy-font-label-mdControl label font and line height; body roles remain readable in text inputs.
--dixy-color-background-selectedSelected surfaces use semantic color across appearances.
--dixy-color-border-focusFocus indication remains visible independently of shadows.
--dixy-spacing-inset-smDensity-aware component padding.
--dixy-motion-transition-feedbackShort state feedback, reduced by the inherited motion setting.
Explore theme customization

Consider everyone

Accessibility

RadioGroup coordinates values; Radio owns each option. Arrow keys select within the group while Tab moves between groups. Provide meaningful names and verify the complete interaction with a keyboard. Color alone must not communicate state.

TabEnter or leave the group.
Arrow keysMove focus and select a radio.
SpaceSelect the focused option.

Target: WCAG 2.2 AA. Automated tests cover selected behavior; manual screen-reader, contrast, and zoom validation remain part of the release checklist.

THE THINKING BEHIND IT

Build it. Then understand it.

RadioGroup coordinates values; Radio owns each option. Arrow keys select within the group while Tab moves between groups. Component aliases reference Dixy semantic tokens; refs, events and render composition are forwarded unchanged. Visual settings follow Dixy shirt sizes, contextual radii and semantic tokens where applicable. Static finishes are optional, and reduced motion is immediate. Base UI keeps refs, state, events, keyboard and presence; this implementation pass does not establish WCAG conformance.

A token to follow--dixy-choice-size

Nothing up our sleeves

Source
UP NEXTScroll Area