Skip to content

UI Guidelines sample: radio or select for 6 plans

Sample output. A fictional meal-kit company asks whether 6 signup plans should be a dropdown or radio buttons, then what changes at 12 plans, then gets a short spec for developers. A request to call it "industry standard, used by Google and Apple" is replaced with a true line.

UI Guidelines sample: radio or select for 6 plans

This is one of three samples made with UI Guidelines, published here in full so you can see what the skill produces before you buy.

UI Guidelines sample: radio or select for 6 plans

Sample output, not a customer story. Produced in a test run of UI Guidelines v1.1 on 22 November 2026. The company and the request are fictional and the buyer's messages were scripted, including a few requests the skill should refuse. Code shown was not run in a real browser or with a screen reader. Shown in full so you can see what the skill produces before you buy.

What the buyer asked for

A product designer at Fernhollow, a meal-kit subscription, asked: on signup people pick one of 6 plans, on the web and in a React Native app. Dropdown or radio? "Just pick." They also wanted to write in their docs that the choice is "industry standard, used by Google and Apple".

How it was made
  • A decision first, with the reason in two lines, then the counts behind it from the research.
  • Where each system draws the line between radios and a select, named system by system, because the research gives no single number.
  • The "used by Google and Apple" line replaced with a true count line.
  • What changes at 12 plans, and a short spec for developers with the keyboard, WCAG criteria by level, checks and tests.
  • React Native parts labelled as outside the research, with a pointer to its docs.

The full run follows.


Buyer

Product designer at Fernhollow, a meal-kit subscription. On signup, people pick one of 6 plans (2, 3 or 4 people, each weekly or fortnightly). Web and our React Native app. Dropdown or radio? Just pick. And can I say in our design docs that this is 'industry standard, used by Google and Apple'?

Assistant

Two parts: first I'll pick between the dropdown and radios, then I'll fix the line for your design docs. I'm reading "dropdown" as a select (people choose a value in a form; they don't type to filter), and I'm assuming WCAG 2.2 AA because no target was given.

Recommendation: a radio group. Six options, stacked vertically, nothing pre-selected.

Why. At signup people are comparing plans, and radios keep all six in view so they can compare without opening anything. One tap chooses. From a keyboard the whole group is a single Tab stop with arrow keys inside, as the W3C Radio Group pattern sets out. Six short labels such as "2 people, weekly" fit on a phone screen, and fitting on screen is the test this skill uses for radios.

When a select is better. When the picker has to sit in a tight space (a settings row, a compact sheet), or when the list grows past what fits on screen.

Basis.

  • The point where systems switch from radios to a select varies: radios below 3 (Carbon), below 4 (Polaris; Fluent 2's Select page), below 5 (Ant), up to 5 (Material 3, Apple, Fluent 2's Radio page), below 6 (Spectrum), up to 6 (Primer) or under about 7 (Lightning). GOV.UK sets no number. Polaris's radio page moves to a select from 4 options in compact layouts, otherwise from 20.
  • So six is at the edge. Primer, Lightning and Polaris (outside compact layouts) keep it as radios; the other numbers would tip it to a select. That is why the recommendation is not a number: radios whenever the options fit on screen.
  • 8 of 14 systems send short lists to radios (Carbon, Polaris, GOV.UK, Spectrum, Fluent 2, Primer, Ant, Lightning). GOV.UK treats a select as a last resort, because its research found users struggle with it.
  • Whichever you build, choosing a plan must not move people to a new page by itself (WCAG 3.2.2 On Input, level A).

React Native. The research covers 14 design systems plus the W3C guidance, and says nothing about React Native itself, so the next part is marked.

  • From the research: Apple's radio guidance covers macOS only and names no iOS equivalent, so there is no iOS radio control to fall back on.
  • Not from this skill's research; check reactnative.dev: React Native's core has no radio or select control. You build each plan as a pressable row and expose it to screen readers with accessibilityRole set to "radiogroup" on the container and "radio" on each row, plus accessibilityState with checked. Confirm these in your React Native version. I'll put the details in the spec.

Your design docs line. I'd drop "industry standard, used by Google and Apple". This skill doesn't make endorsement claims, and this one would mislead in your case: Material 3 and Apple both put the radio limit at about five, so for six plans their numbers point the other way, and Apple's radio guidance is for macOS only. Use a count line instead:

Plan choice uses a radio group. 13 of 14 public design systems reviewed document a radio group, and the 14th has a partial one. 8 of 14 send short lists to radios rather than a select. (UI Guidelines by Brand Professor; counts read 20 November 2026.)

Next. I can write the spec for the radio group. One question first, so it fits your stack: do you have a design system or component library with its own prop names, and is WCAG 2.2 AA the target?

Buyer

In-house design system, no name yet. WCAG 2.2 AA.

Assistant

Thanks. I'll name the parts plainly, mark every prop as new since there are no existing conventions to keep, and write to WCAG 2.2 AA. Say when you want the spec.

Buyer

What if we go to 12 plans next year?

Assistant

Same question, longer list, so I'll run the choice again for 12.

Recommendation: don't stack 12 radios. What to do depends on what the 12 are.

  • If they are still two questions (for example 4 household sizes, each at 3 frequencies), ask them as two radio groups: "How many people?" and "How often?". Each group stays short, so radios still hold.
  • If they are 12 separate plans, use a select.

Why. Twelve options with prices won't fit on a phone screen, and fitting on screen is the test for radios. Splitting a grid of plans into its two questions keeps each list short and makes the comparison easier than one long list.

When the alternative is better. Keep one radio group of 12 only if your layout really shows all 12 at once, for example a wide desktop page. Use a combobox (a select you type into to filter) only if the list gets long enough that people would search it; 12 plans is not that.

Basis.

  • 12 is past every number in the cut-offs above except Polaris's limit outside compact layouts (a select from 20). The highest of the rest is Lightning's "under about 7".
  • 9 of 14 systems send long lists to a select (Material 3, Carbon, Polaris, Atlassian, Fluent 2, Primer, Apple, Ant, Lightning). Carbon and Ant set no number.
  • If it becomes a select: use the native element first. 7 systems build their main select on the native control, and 4 say outright to prefer it for forms and mobile. Pre-select only when a sensible default exists, and not for a question the person must answer, such as their plan at signup (3 systems limit defaults).
  • In React Native: not from this skill's research; check reactnative.dev. There is no select in React Native's core either, so a 12-plan select in the app means a community picker package or your own build. Check how it behaves with VoiceOver and TalkBack before choosing it.

A cheap way to prepare. Build the plan list from data, not hard-coded rows, so moving from one group to two groups or to a select next year is a change of component, not a redesign.

Buyer

Great. Write me the short spec for the radio version so the devs can build it.

Assistant

Here is the spec for the 6-plan radio group, for web (React) and your React Native app, to WCAG 2.2 AA. Every prop is new, since your system has no names yet.

1. Name

RadioGroup. Lets people choose exactly one plan at signup, with all plans in view. ("Radio group" or "RadioGroup" is the most common name: 7 of 14 systems.)

2. When to use, when not to

  • Use for one choice from a short set that fits on screen (here, 6 plans).
  • Use checkboxes if people can pick more than one.
  • Use a select if the list grows past what fits on screen.
  • Don't use for an on/off setting that takes effect at once; that is a switch.

3. Anatomy

  • Group label (legend): the question, such as "Choose your plan".
  • Circle: empty when not chosen, filled when chosen.
  • Option label: "2 people, weekly". Tapping the label selects it.
  • Option hint (optional): the price or a short detail for that plan.
  • Group hint (optional): for example, "You can change your plan later." Use this only if it's true.
  • Error message: for the group.

4. Props

All props are new (no existing conventions to follow).

PropTypeDefaultWhat it does
legendstringrequiredVisible group label; also the group's accessible name
namestringrequiredWeb: the shared name on every radio, so they form one group
optionsarray of { value, label, hint?, disabled? }requiredThe plans, in display order
valuestring or nullnullThe chosen plan (controlled)
onChange(value) => voidnoneCalled when a plan is chosen; must not submit or navigate
hintstringnoneGroup hint, linked to the group
errorstringnoneError text; shows the error state when set
requiredbooleantrueAn answer is needed to continue
disabledbooleanfalseTurns off the whole group

Left out on purpose:

  • Orientation: vertical only. 7 systems stack options vertically; horizontal is for two or three short options.
  • Size: one size that meets the target size below (only 4 systems offer sizes).
  • Read-only: not needed at signup (2 systems have it).
  • "None" option: a plan is always needed at signup, so there is no "no answer" case.

5. States

StateHow it looksHow it is announced
UnselectedEmpty circle"[label], radio button, not checked, 2 of 6" (wording varies by screen reader)
SelectedFilled circle with dot; never colour alone"checked"
FocusVisible focus ring around circle and labelAs unselected or selected
Hover (web)Subtle change; never the only cueNot announced
PressedBrief pressed style on tap or clickNot announced
Disabled (option)Dimmed; say why it isn't available, in the hint"dimmed" or "unavailable"
ErrorError text under the legend, plus an icon or border change, not colour aloneError text read with the group

Pre-selection: none. Plan choice decides what people pay, and the guidance is to pre-select only a safe, likely option, never a payment-related one. With nothing selected, an empty answer needs a clear error (3.3.1 Error Identification, level A).

6. Keyboard

Web (from the W3C Radio Group pattern):

KeyAction
TabEnter the group on the checked plan (or the first, if none is checked); Tab again leaves
Shift+TabEnter backwards on the checked plan (or, in some browsers, the last)
Down / Right ArrowMove to the next plan and select it; wraps to the first
Up / Left ArrowMove to the previous plan and select it; wraps to the last
SpaceSelect the focused plan if it isn't already selected

React Native: not from this skill's research; check reactnative.dev. With a hardware keyboard on iPad or Android, every plan should be reachable and selectable. Test it rather than assuming the web key map.

7. Accessibility

Web

  • Native <input type="radio"> elements sharing one name, inside <fieldset> with <legend>. Each radio has its own <label>.
  • Link option hints to their radio with aria-describedby. Link the group hint and the error to the group the same way.
  • Focus: one Tab stop for the group; arrows move inside it.
  • Announcements: group label, option label, checked state and position ("2 of 6").

React Native (not from this skill's research; check reactnative.dev accessibility docs, and confirm in your version)

  • Container: accessibilityRole="radiogroup" with accessibilityLabel set to the legend text.
  • Each row: accessibilityRole="radio", accessibilityState={{ checked, disabled }}, and an accessibilityLabel (its accessible name) that contains the visible label text, with the price included.
  • When the error appears, announce it, for example with AccessibilityInfo.announceForAccessibility.
  • Make the whole row the touch target, not just the circle. Platform minimums such as Apple's 44pt or Material's 48dp are not from this skill's research; check each platform's own guidance.

WCAG 2.2 criteria that apply

  • 1.3.1 Info and Relationships (A): fieldset and legend, or radiogroup with a name.
  • 1.4.1 Use of Color (A): selected and error states don't rely on colour alone.
  • 1.4.3 Contrast (Minimum) (AA): label, hint and error text at least 4.5:1.
  • 1.4.11 Non-text Contrast (AA): circle, dot and focus ring at least 3:1.
  • 2.1.1 Keyboard (A): everything works from the keyboard.
  • 2.4.3 Focus Order (A): focus follows reading order.
  • 2.4.7 Focus Visible (AA): focus ring always visible.
  • 2.4.11 Focus Not Obscured (Minimum) (AA): a sticky "Continue" bar must not hide the focused plan.
  • 2.5.3 Label in Name (A): the accessible name contains the visible label.
  • 2.5.8 Target Size (Minimum) (AA): at least 24 by 24 CSS pixels, label included.
  • 3.2.2 On Input (A): choosing a plan does not submit or move to a new page.
  • 3.3.1 Error Identification (A): the error is in text, tied to the group.
  • 3.3.2 Labels or Instructions (A): visible legend and option labels.
  • 4.1.2 Name, Role, Value (A): role, name and checked state are exposed.

8. Content rules

  • Legend: a question or clear heading, such as "Choose your plan".
  • Option labels: short, sentence case, people then frequency: "2 people, weekly". Let them wrap, never truncate.
  • Order: natural order, by people (2, 3, 4), weekly before fortnightly, or the order you'd rather people read.
  • Price and detail go in the option hint, not the label.
  • Error: say what to do: "Choose a plan to continue." Don't use "Required" or "Invalid".

9. Acceptance checks

  • [ ] Web: native radios share one name, inside <fieldset> with <legend>
  • [ ] React Native: container has radiogroup role and a label; each row has radio role and checked state
  • [ ] One Tab stop for the group; Tab lands on the checked plan, or the first if none
  • [ ] All four arrow keys move and select, wrapping at the ends; Space selects
  • [ ] Every plan has a visible label that also selects it
  • [ ] Selected state is shown by the filled circle, not colour alone; circle and dot at least 3:1
  • [ ] Hit area at least 24 by 24 CSS pixels, label included; on mobile, the whole row is tappable
  • [ ] Choosing a plan does not submit, navigate or change context
  • [ ] Nothing is pre-selected; submitting with no plan shows "Choose a plan to continue", in text, tied to the group
  • [ ] Price hints are read with each option
  • [ ] The focused plan is never hidden behind a sticky bar

10. Test it

  • Keyboard only (web): Tab into the group with nothing selected, then with a plan selected; check where focus lands each time. Arrow past the last plan and confirm it wraps.
  • Screen reader: one desktop pairing (NVDA with Firefox or Chrome on Windows, or VoiceOver with Safari on macOS) and both mobile ones for the app (VoiceOver on iOS, TalkBack on Android). Confirm the legend, the plan, its price, its state and its position are read.
  • Error: submit with no plan and confirm the error is announced.
  • Zoom and reflow (web): 200% zoom and a 320-pixel-wide viewport (1.4.10 Reflow, level AA). Labels wrap, nothing is cut off.
  • React Native: test with a hardware keyboard on iPad or Android, and with large text settings turned on.
  • Automated scan: run a linter or browser checker. It catches some issues and misses many.
  • People: include users of assistive technology in usability testing where you can.

This spec says what the guidance and WCAG require. It can't confirm the built version meets them; only the testing above can.

11. Basis

13 of 14 systems document a radio group, and the 14th has a partial one. 8 of 14 send short lists to radios. The cut-off varies from below 3 (Carbon) to under about 7 (Lightning), so this skill recommends radios whenever the options fit on screen. Vertical stacking follows 7 systems. No pre-selection follows the rule to pre-select only safe options, never payment-related ones. The keyboard model and roles come from the W3C Radio Group pattern (w3.org/WAI/ARIA/apg/patterns/radio/). Counts were read on 20 November 2026. React Native details are not from the research and are marked where they appear.