# Select: One Shared Pick-One Field for Long Lists

> Learn when a Select fits, how to define its parts and states, and how to make it work for keyboards, screen readers, and phones.

**In short:** A Select is a shared pick-one field for long lists, and a design system defines its parts and states so it works for keyboards, screen readers and phones.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/select

## What You Will Learn

This lesson teaches Select, the shared design system part that lets a person pick one option from a list. The list stays hidden until the person opens the field. In this course, Select means the one component the whole team reuses, not a one-off drop-down built for a single screen.

You will learn when Select is the right choice, how to define its parts and states, and which keyboard, screen reader, and phone basics every version must meet. A worked example then walks through a country field in a checkout form.

- **Select:** A form field that shows one chosen value and opens a hidden list of options when a person clicks or taps it.
- **Native control:** A form part the browser or phone already provides, so the team does not have to rebuild how it behaves.
- **Label:** The visible name that tells people what the field is for.
- **Placeholder:** Faint prompt text, such as 'Choose a country', shown before anything is picked.
- **Helper text:** A short note under the field that explains what to enter.
- **Listbox:** The list of options that opens from the field.
- **Type-ahead:** Jumping to an option by typing its first letters.
- **Screen reader:** Software that reads the page aloud for people who cannot see it well.

## When does a Select fit?

A Select is for one choice from a list that is long enough to be worth hiding. A rough working rule for this course is that a list of about six or more options, in a place where space is tight, is a good candidate. Shorter lists usually work better as visible choices, because people can see every option at once and pick faster.

Teams do not agree on one exact number. Some systems suggest a Select from four options, others from seven, and some possibly only past eight. That is why each team should write its own threshold into its rules and then test it with real people.

- **Long lists:** People scan many options, such as countries, time zones, or product sizes. Hiding that list keeps the page calm.
- **Tight space:** A form with many fields may have no room for a stack of radio buttons, so a collapsed field fits better.
- **One answer only:** A Select returns one chosen value. If a person must pick several answers, the field should be something else.
- **Optional answers:** Some questions can be left empty. A placeholder lets the person return to a nothing-chosen state.

### How does a Select differ from radio buttons, checkboxes, and combo boxes?

Choice components compete for the same job, so a team must know which one fits. The cards below give the main contrast. Dropdown menus that open from a button to run actions have their own lesson, so this section covers only form choices.

- **Radio buttons:** Radio buttons show every option at once. They suit short lists, which some guides put at about four options or fewer, and any list where seeing every choice first helps the person decide.
- **Checkboxes:** Checkboxes let a person tick several answers. A Select should not allow several picks, so use checkboxes whenever more than one answer is valid.
- **Styled dropdowns:** Some systems call a Select a dropdown, while others use the word for a styled menu.
- **Searchable combo box:** When a long list needs typing to narrow it down, a searchable combo box is the better fit.

> **Tip:** Ask one question first: can the person see every option at once without losing space? If yes, prefer visible choices. If no, and only one answer is valid, a Select is the likely fit.

## What is the anatomy of a Select?

Anatomy means the named parts that make up the component. A shared Select defines each part once, so product teams do not invent their own version.

1. **Label:** Place a visible label above the field. It says what the list is for, and it must stay on screen, not only in the code. Keep it short. One guide suggests that a label ideally be a single word.
2. **Placeholder:** Show prompt text such as 'Choose a country' until the person picks something. Without it, an empty field can look like a plain text box. UK Parliament research notes this confusion.
3. **Selected value:** After a choice, show the chosen text in the field, and keep it visible after the list closes. The field is only one line high, and overflow is hidden so the chevron stays visible. Decide that truncation rule in advance.
4. **Option list:** This is the hidden list of choices. Order it alphabetically or by popularity so people can predict where to look. Some sources suggest hiding options that do not apply to the person's earlier answers. Hennepin advises against using earlier answers to decide which options appear, because this can confuse users.
5. **Helper text:** A short note under the label that explains what is needed, such as which country to pick for a billing address. It gives guidance before any error happens.
6. **Error text:** A message shown when the field is left empty or wrong. Start it with the word Select, such as 'Select your country.' Place it near the field and say what to fix.

## What states does a Select have at each moment?

A state is the look and behavior a component has at one moment. A shared Select needs a written rule for each of these five states.

- **Default:** The field is closed. It shows the label and either the placeholder or the chosen value, with a clear edge so it reads as a field.
- **Focus:** The field has been reached by keyboard or click and is ready for input. Show a clear focus outline. Never remove it, because keyboard users rely on it to see where they are.
- **Open:** The option list is showing. The current option is highlighted, and the list opens close to the field so the eye does not travel far.
- **Disabled:** The person cannot change the value, for example while a related field is loading. Avoid the disabled state attribute, because disabled inputs are hard to tell apart and do not explain why they are locked.
- **Error:** The field needs a fix. Use an error colour and an icon, plus the error text under the field. Colour alone should never carry the message.

### How do you handle long lists, grouped options, and empty results?

Long lists need the most care. A plain list of two hundred items is hard to scan, so the rule should say when to add search or switch to a different component. Native controls have limits here.

Grouped options, such as countries sorted under regions, need a plan. Test what your chosen control shows on each platform before you promise grouping in the rules, because guides do not all describe native behavior the same way.

Empty results happen when a search or filter matches nothing. The rule should say what the person sees, such as a short message that says no matches were found and suggests checking the spelling. The list should never look blank or broken.

## Keyboard and Screen Reader Basics

Every Select must work with a keyboard alone. Many people cannot use a mouse, and screen reader users depend on the same controls. UK Parliament cites government research showing that people struggle when they cannot close a select or when they try to type into it. The rules below describe what a person must be able to do.

- **Opening and moving:** With the field closed, the Up or Down arrow key can open it. With the list open, the arrow keys move from one option to the next.
- **Choosing:** Enter or Space picks the highlighted option. Escape closes the list without changing the value, and focus returns to the field.
- **Type-ahead:** Typing a letter jumps to the first option that starts with it.
- **Jumping to ends:** Home and End move to the first and last option, and Page Up and Page Down move faster through a long list.
- **Visible labels:** A label must be visible on screen and connected to the field, so a screen reader can say what the field is for.
- **Screen reader announcements:** A native Select gives screen readers the role, the name, and the chosen value without extra work. A custom version must supply that information by hand.
- **Phones and tablets:** That picker is often easier to use than a custom list on a small screen.

> **Tip:** Before you approve any Select, run a quick check. Tab to it, open it with the keyboard, type a letter, press Escape, and listen to what a screen reader announces. If any step fails, the component is not ready.

### Native or Custom: The Trade-Off

The native Select comes from the browser and the phone. It handles keyboard, screen reader, and mobile behavior out of the box, but it is hard to style the same way on every platform. A custom Select can match the brand exactly, but the team then owns every behavior, including focus, scrolling, and announcements.

Most accessibility guides advise starting with the native control. Build a custom version only when the product truly needs search, rich option content such as icons, or options that load from a server as the person types.

Some teams use a hybrid. Phones and tablets get the native control, while mouse users get a styled list. This doubles the testing work and needs a clear reason, so write the reason into the rules.

> **Tip:** If the only reason for a custom Select is looks, keep the native control. Styling the label and the field around it usually gets most of the way there.

## Worked Example: The Country Field in a Checkout Form

Picture a checkout address form. Most fields are short text boxes, but one asks for the shopper's country, and the list holds about two hundred countries. A designer proposes a custom dropdown with a neat panel and rounded corners. Should the team accept it, or use a Select? Walk through the decision.

1. **Check the list length:** Two hundred options is far past the point where a visible list works. Radio buttons would fill the screen, so the field must collapse into a hidden list.
2. **Pick the component:** Single choice alone does not settle it, because NYC guidance says a combo-box suits choosing one item from more than 15 options. A searchable combo box could help later, but it is a separate component, and the team should adopt it on purpose.
3. **Set the label and placeholder:** Label the field 'Country' above it. Show 'Choose a country' as the placeholder, so the empty field does not look like a text box.
4. **Add type-ahead:** A shopper types 'Ca' and lands on Canada. The team confirms that this works from the keyboard alone, and that Escape closes the list without changing the choice.
5. **Check the phone:** On a phone, tapping the field opens the system's own picker. The shopper scrolls and taps, with no custom panel to fight with.
6. **Write the error:** If the field is left empty at checkout, show 'Select your country' under the field. Keep the answers in the rest of the form intact.

Why the custom dropdown loses: the neat panel may open with a mouse but not with the keyboard. A screen reader may not announce it as a list, or may not say which country is chosen. On a phone, the panel may be small and fiddly. Each failure can block a real shopper at checkout. The native Select handles these cases by default, so the team's effort goes into the label, placeholder, and error text that the shopper actually reads.

> **Tip:** If your team does need search for a two-hundred-item list, do not force a plain Select to do it. Document search as a separate component with its own rules.

## Writing the Select Rules for Your Team

1. **Name the anatomy:** List every part: label, placeholder, selected value, option list, helper text, and error text. Give each one a short definition.
2. **Describe every state:** Write a sentence each for default, focus, open, disabled, and error. Say what the person sees and what they can do.
3. **Set the choice thresholds:** State when a Select is right, when radio buttons or checkboxes win, and what the team does near the boundary. Name the number your team chose.
4. **Define long-list and empty behavior:** Say when search is required, how groups appear, and what message shows when nothing matches.
5. **Set the keyboard and phone rules:** List the keys that open, move, pick, and close the list. Add the rule that phones use the system picker where it exists.
6. **Test with real people:** Ask people, including keyboard and screen reader users, to finish a task with the Select. Revise the rules wherever they struggle.

Deeper testing tools, unit tests, version numbers, and how the component is listed in a catalog each have their own lesson. Treat this lesson's rules as the shared starting point those lessons build on.

## Check Your Understanding

Try two short scenarios. Each one needs the ideas above to answer.

**Quick check:** A signup form asks users to choose a plan from 3 options. A second field asks for their country from about 200 options. Which field should use a Select, and which should use something else?

A. Radio buttons for the plan, and a Select for the country
B. A Select for the plan, and radio buttons for the country
C. Checkboxes for both fields, so people can pick more than one
D. A custom dropdown for both fields, so the form looks the same

**Answer:** A. Three plan options are short enough to show at once, so radio buttons let people compare them without opening anything. Two hundred countries would fill the page as radio buttons, so a Select saves space. Checkboxes would allow several picks, which breaks the one-choice rule. A custom dropdown adds keyboard and screen reader work that a native Select already handles.

**Quick check:** A shipping step offers 9 methods. Each method has a price, a delivery time, and an icon. Shoppers must compare them before they choose. What is the best component?

A. A native Select with the price and time typed into each option name
B. Radio buttons with the price and delivery time shown beside each choice
C. A checkbox group, so shoppers can pick several shipping methods
D. A hidden custom dropdown, because the icons need a custom panel

**Answer:** B. Shoppers need to compare before they choose, and radio buttons keep every method and its details in view. Checkboxes allow several picks, which does not fit choosing one method. A custom dropdown brings back the keyboard and screen reader work and hides the comparison.

## Sources

- [UK Parliament Design System: Select](https://designsystem.parliament.uk/forms/select/)
- [Scottish Government Design System: Select (dropdown)](https://designsystem.gov.scot/components/select)
- [Hennepin County Design System: Select](https://www.hennepincounty.gov/design-system/components/components-library/select)
- [NYC Digital Design System: Drop-down select](https://designsystem.nyc.gov/components/drop-down-select.html)
- [NSW Government Design System: Select](https://designsystem.nsw.gov.au/components/select/index.html)
- [Kolibri Design System: KSelect](https://design-system.learningequality.org/kselect/)
- [Hover Design System: Select](https://design-system.hover.to/components/forms/select)
- [Carbon Design System: Dropdown guidelines](https://www.carbondesignsystem.com/building-blocks/core/components/dropdown/guidelines)
- [Stellae UI Pattern Guide: Select Component](https://www.stellae.design/en/components/select)
- [SEB Design Library: Select](https://designlibrary.sebgroup.com/components/component-select/)
- [GOV.UK Select component pattern source (UX Pattern Guide)](https://uxpatternsguide.com/sources/govuk-select-component/)
- [Accessible Listbox Guide](https://accessibility.build/guides/accessible-listbox)
- [Atomic Accessibility: Select dropdown listbox testing checklist](https://www.atomica11y.com/accessible-web/select/)
- [LEGO Engineering: Building an accessible Select component in React](https://medium.com/lego-engineering/building-accessible-select-component-in-react-b61dbdf5122f)
- [DesignDev: Building a Select Component, native or custom](https://www.designdev.io/posts/building-a-select-component-when-to-use-native-and-when-to-go-custom)
- [CSS-Tricks: Striking a Balance Between Native and Custom Select Elements](https://css-tricks.com/striking-a-balance-between-native-and-custom-select-elements/)
- [Access Guard: Accessible Combobox Pattern and Keyboard Guide](https://getaccessguard.com/posts/how-to-build-accessible-custom-dropdowns-comboboxes-that-actually-work)
- [Design System Problems: Accessible Select Dropdown Design](https://designsystemproblems.com/accessibility-compliance/accessible-select-dropdown/)
- [DEV Community: Creating A Custom, Accessible Drop Down](https://dev.to/emmabostian/creating-a-custom-accessible-drop-down-3gmo)
