Forms & inputExplore · Adapt · Compose
Radio Group
A set of mutually exclusive options styled like modern radio controls. Make the expected input clear before someone interacts, and keep the current value, help text and validation feedback connected. Explore the live examples, inspect their source and choose the composition that fits your interface before connecting it to your application's data.
The examples use @/components/kamod-ui/radio-group in a Preact project. Follow the live result and its source together: compare supported options in the API reference, refine presentation with the component styles guide, and use shared theme tokens for consistent colors and surfaces. Preserve keyboard behavior and meaningful labels as you replace the sample content.
In this guide 7 sections
Installation
Import RadioGroup and RadioGroupItem from @/components/kamod-ui/radio-group. Label pairs cleanly via id and htmlFor.
pnpm add @kamod-ch/uiThe @/components/kamod-ui/… imports in these examples refer to local source files. Configure that alias when copying source, or use the corresponding exports from @kamod-ch/ui when installing the package. Connect the global theme CSS and Tailwind source detection before your first render.
Usage
Use defaultValue for uncontrolled groups, or value with onValueChange when the parent owns state. Omit name to get a stable generated group name. Pair each item with Label for accessible names; use size="sm" for dense layouts. disabled and aria-invalid on items match form and validation patterns.
import { RadioGroup } from "@/components/kamod-ui/radio-group";Choose a complete composition from the examples below; required child components and props vary by pattern.
Component examples & variants
Explore Radio Group in different contexts, from the starting pattern to the compositions below. Begin with Default, then compare the examples that match your content, state and layout. These are working patterns to adapt, not a list of interchangeable variant values: check the API reference before using a prop or combining behaviors. Look at the surrounding labels, supporting text and spacing as well as the component itself.
Read the result and its implementation together. Use each showcase’s Code view to inspect imports and composition, or its Prompt view to prepare a setup or adaptation brief. Try the narrow preview and local theme controls before connecting real data, and use Reset to return an example to its initial state. Keep layout changes in class utilities where appropriate; follow the component styles guide for hierarchy and the theming guide for shared surfaces and colors. The accessibility notes explain what to preserve when making those changes.
Default
Classic row layout with visible focus rings and clear typography, similar to shadcn/ui.
import { Label } from "@/components/kamod-ui/label";
import { RadioGroup, RadioGroupItem } from "@/components/kamod-ui/radio-group";
export const Example = () => (
<RadioGroup defaultValue="option-one" class="grid gap-3">
<div class="flex items-center gap-3">
<RadioGroupItem value="option-one" id="rg-option-one" />
<Label size="sm" htmlFor="rg-option-one">
Option one
</Label>
</div>
<div class="flex items-center gap-3">
<RadioGroupItem value="option-two" id="rg-option-two" />
<Label size="sm" htmlFor="rg-option-two">
Option two
</Label>
</div>
</RadioGroup>
);Description
Stack a title and helper line beside each control for settings-style lists.
Choice card
Clickable cards with the control aligned to the primary label.
Field group
Use Field for a group heading, description, and stacked options.
Disabled & invalid
Per-item disabled state and aria-invalid for validation feedback.
Inline & small
Horizontal groups and compact indicators for toolbars.
Props and data
Configure Radio Group using the contracts below. Read the documented options alongside the source definitions to understand which values your application supplies and which details the component owns. Start with a prop or helper, then follow its type link to inspect the declaration without leaving the page.
Props, slots and variants for this component.
TypeScript source at build time. Props inherited through HTMLAttributes, Omit or variant helpers remain references in those declarations; their fields are not flattened here. Match the reference to your installed version, and check a package’s exports before writing an import type. A type exported by a source file is not necessarily re-exported by @kamod-ch/ui.TypeScriptComponent props
? means a field can be omitted; it does not promise a fallback value. Existing documented defaults remain alongside the descriptions. For callbacks, check the argument and return types before connecting your own state or services.Radio Group
Radio Group component props and accepted values.
| Prop / type | Description |
|---|---|
name | When omitted, a stable unique name is generated (forms can still submit if you add name to inputs manually). Documented default |
defaultValue | Documented defaultValue option for Radio Group. Check its type alongside the usage examples before supplying a value. Documented default |
value | Documented value option for Radio Group. Check its type alongside the usage examples before supplying a value. Documented default |
onValueChange | Documented onValueChange option for Radio Group. Check its type alongside the usage examples before supplying a value. Documented default |
RadioGroupItem value | Documented RadioGroupItem value option for Radio Group. Check its type alongside the usage examples before supplying a value. Usage requirementRequired |
RadioGroupItem size | Documented RadioGroupItem size option for Radio Group. Check its type alongside the usage examples before supplying a value. Documented default |
RadioGroupItem disabled | Documented RadioGroupItem disabled option for Radio Group. Check its type alongside the usage examples before supplying a value. Documented default |
RadioGroupItem aria-invalid | Documented RadioGroupItem aria-invalid option for Radio Group. Check its type alongside the usage examples before supplying a value. Documented default |
Data type reference
Expand a card to inspect and copy the exact declaration. The code header identifies its repository file; follow imported or inherited types in the implementation source when you need the complete dependency chain. Required-field summaries cover fields declared directly in that type. Source-only helpers and inferred schema outputs describe the local implementation, not additional props you can pass to every component.
RadioGroupPropsRadioGroupItemPropsvalueAccessibility
Build the complete interaction, including the parts outside Radio Group. The notes below distinguish the current implementation from the labels, content and behavior your application supplies. Start with the live preview, check the props and data reference, and test the finished composition with real content rather than assuming that an unchanged visual example covers every use case.
Built-in behavior and defaults
RadioGroup exposes role="radiogroup"; its items contain native radio inputs sharing the group's name. RadioGroupItem wraps its input and children in a label, so meaningful option text participates in the input's name.
Labels and relationships
Give the group an overall question using aria-labelledby or aria-label, then name each option distinctly. Keep descriptions of trade-offs visible. Use unique group names for unrelated questions so browser-native radio navigation does not join them accidentally.
Keyboard and focus
Native radio behavior handles selection within the same named set. Test Tab entry and arrow-key movement in supported browsers. Use the group's value callback for controlled state so the visible selection and the checked input agree.
States and integration details
Avoid nesting additional buttons or links inside an option's label. Explain unavailable options outside the disabled control, and distinguish no selection from a valid option whose value happens to be an empty string.
Verify the complete interaction
Check behavior as well as markup. Work through these scenarios in the application where the component will be used. Automated checks can help find structural problems; also review the reading experience with a screen reader, keyboard focus and the actual feedback from your application.
- Read the group question and each option name using assistive technology.
- Move through options with the keyboard, skip disabled choices and verify a single selected value.
- Render two unrelated groups and ensure their selection and keyboard behavior remain independent.
Recheck the result after changing theme tokens, translations or class overrides. Include text enlargement, narrow layouts and reduced-motion settings where animation is present. Inspect the component source when a behavior differs from your expectation; a role or state attribute does not implement keyboard interaction by itself.
For background, read the WAI-ARIA authoring guidance and keyboard interface guidance. These explain the patterns; verify browser and assistive-technology behavior for the implementation and audience you actually support.
Build it into your interface
Use the Radio Group examples as a starting point, then review the behavior in the context of your own screen. Layout, state and content should work together.
Connect the behavior
Choose where the value lives before wiring up validation. Use the documented change callback, preserve the field name when submitting a native form, and associate help or error text with the control. A placeholder supplements a label; it does not replace one.
Copy the composition, then connect its intent. Replace sample records and callbacks with your own data flow. For options such as value, defaultValue, open or onChange, use only those documented in this component's API; different components expose different contracts.
Give each piece of state one owner. Keep a temporary selection inside the interface when nothing else needs it; lift shared values into a parent when other controls depend on them. Read the prop reference before combining controlled values with defaults. A default normally initializes a control; it is not a substitute for updating its current value.
Connect requests in an event handler or your application’s data layer, never as a side effect of rendering. Keep pending, completed and failed outcomes distinct, preserve useful input after an error, and offer a clear recovery action. If the integration subscribes to an external source, remove that subscription when its owner unmounts; cancel or ignore obsolete requests so an earlier response cannot replace newer results.
Start with the live preview, then exercise the same interaction with your actual data. The type definitions describe accepted values; they do not implement persistence, navigation or server-side validation for you. Keep those responsibilities in the application that composes the UI.
Refine the presentation
Let a parent own the surrounding spacing. Keep related elements together with gap and use semantic surface/foreground pairs so the composition follows the active theme. The wrapper below changes the surrounding layout without assuming extra props on Radio Group.
import type { ComponentChildren } from "preact";
export function ExampleSurface({ children }: { children: ComponentChildren }) {
return (
<div class="grid min-w-0 gap-4 rounded-lg border border-border bg-card p-4 text-card-foreground sm:p-6">
{children}
</div>
);
}Put the chosen example inside ExampleSurface, then refine supported variants and sizes using the API above. For application-wide changes, adjust theme tokens instead of repeating fixed colors. See Component styles for hierarchy, density and focus treatments.
Review the complete interaction
- Try an empty value, a valid value and a rejected value; keep the correction visible beside the field.
- Navigate using only the keyboard and verify the label identifies the focused control.
- Check disabled and read-only behavior separately where supported; they communicate different intentions.
The preview's narrow control changes its container width. Also resize the browser when checking viewport-based Tailwind utilities such as sm: and md:, and test overlays in the full page where their portals render.
Compose a complete interface
Radio Group is one part of the interaction. Choose companion components for the information or actions that still need a place on the screen. The references below are suggestions to compose deliberately, not extra dependencies you must add to every example.
Keep one source of truth for the operation and let each component communicate a different part of it. For example, waiting, no results and failure need different explanations. Avoid showing contradictory states together, and keep recovery actions close to the message that explains them.
Start with the smallest composition that explains the task. Browse the component library for individual controls or the block collections for complete layouts. Reuse shared theme tokens so these pieces feel consistent in light and dark mode.
Sources & design references
Follow Radio Group from its implementation to the ideas behind your own composition. Start with the local API, explore a visual direction, then bring the result back to your app’s shared styles.
Bring it back to your app
A reference becomes useful when it fits your real content. Work through these decisions in order:
- Keep the behavior grounded. Start with the interactive examples, then connect your data and callbacks using the integration guidance. Preserve labels, keyboard access and disabled states as you change the presentation.
- Make the styling repeatable. Use the styles guide for local
classadjustments and theming documentation for shared color decisions. Keep semantic surface and foreground pairs together in both light and dark mode. - Check the complete screen. See how components combine in the block collections, then try long labels, loading states and narrow layouts in your own composition. The Theme Toggle guide helps you expose a scheme switch in the finished interface.