Input Checkbox: One Shared Box for Choices, Partial Selections, and Clear States
How the checkbox part of a design system shows its states, how its label and group are laid out, and how keyboard and screen reader users operate it.
In short
A checkbox in a design system lets a user select one or more independent options, with defined states, a clear label and group layout, and keyboard and screen reader support.
11 min readFree
What you will learn
A checkbox is a small square that a person clicks to pick an option. In a design system, the checkbox is a shared part. Every screen uses the same version, so people learn it once and trust it everywhere. This lesson shows you what the checkbox is made of, the states it can be in, when to choose it over a radio button or a toggle, how to lay it out, and how to make it work for everyone, including people who use a keyboard or a screen reader.
Key words
- Design system
- A shared set of parts and rules that a product team reuses across its screens.
- Component
- One reusable part of a design system, such as a checkbox, a button, or a text field.
- Checkbox
- A small box that a user turns on or off. It can be checked or unchecked.
- Indeterminate state
- A mixed state, usually shown as a dash in the box. It means some, but not all, of a related group is selected.
- Label
- The words beside the box that tell the user what the option does.
- State
- The condition a part is in at a moment, such as checked, hover, focus, disabled, or error.
- Focus ring
- A visible outline that shows which element is active when a user moves with a keyboard.
- Tap target
- The area a person can press. A larger area is easier to hit, especially on a phone.
- Screen reader
- Software that reads a screen out loud for people who cannot see it well.
- Radio button
- A round option where the user picks exactly one choice from a group.
- Toggle switch
- A sliding on-off control, usually used for a setting that takes effect right away.
What is an input checkbox?
An input checkbox lets a user select one or more options that do not depend on each other. Each box is a choice on its own. A user can pick none, one, or many. The same part can also act as a single yes or no switch, such as an agreement to terms. Because it is so common, teams often make it one of the first core components in their system.
The box
The outer frame. It is the part people click, and it should look the same on every screen.
The checkmark
The tick or dash drawn inside the box. It shows the current selection. The design system decides its exact shape once.
The label
The text beside the box. It explains the option. A checkbox without a clear label does not help anyone choose.
The click target
The full area that responds to a press. In a good design, pressing the label works just like pressing the box.
Think of these four parts as the anatomy. When a designer defines the checkbox once, every team that imports it gets the same box, the same tick, the same label spacing, and the same click area.
What states can a checkbox be in?
A design system must describe every state a checkbox can be in. A state is a condition the part can be in at a given moment. If the rules are missing, each designer will invent a different look, and builders will guess. Most systems list selection states first, then states that come from user actions or from the form itself.
Selection states
Unchecked
The option is not selected. Many teams make this the default. Opt-in choices are usually unchecked at the start, so the user chooses to say yes.
Checked
The option is selected. The box shows a tick, and the choice counts when the form is sent.
Indeterminate
The box shows a dash or a line. It is used for a parent option when only some of its child options are selected.
The indeterminate state is special, so keep it in mind. It only changes how the box looks. Nord also notes that users cannot set it directly. It is set by the system to show a partly selected group.
Interaction and status states
Hover
The pointer is over the box or the label. A slight change in the box border or background tells the user it is clickable.
Focus
The box is active, usually because a keyboard user moved to it. It needs a visible focus ring so the user can see where they are.
Disabled
The option cannot be changed right now.
Error
The form needs an answer, and the user has not given one. The wording of the message belongs to another lesson, but the box must show the error clearly.
Tip
Write each state as a short rule with a picture of what it looks like. For example, say that the indeterminate box shows a dash in the same size and color as the tick. Builders can then match it without asking you.
Should you use a checkbox, radio button, or toggle switch?
Many new designers pick a control by look instead of by job. The better test is how many choices the user can make and when the change takes effect. Three controls cover most cases, and each has a clear job.
Use checkboxes for many independent choices
Checkboxes let a user select any number of options, including none. Radio buttons would clear the others, so they are the wrong tool for a list where several answers can be true at once.
Use radio buttons for exactly one choice
A radio group lets the user pick one option, and picking one clears the rest. A lone radio button makes no sense, because it cannot be turned off.
Use a toggle for an instant setting
A toggle is good for one on-off setting that applies right away and can be reversed without a save step. If the change waits for a Save button, a checkbox is usually the better choice.
Two cases often confuse people. A single yes or no choice in a form is usually a single checkbox. Two radio buttons can also work for yes or no, when both answers need equal space. Also, the checkbox is not the right tool for actions.
Tip
Ask two questions. How many answers can the user pick? Does the change happen right away, or only after the form is sent? Those two answers usually settle the control.
How should labels, layout, and grouping work?
A checkbox does its job only when the user understands the option and can click it easily. The system should set the rules for labels, spacing, grouping, and click area so that every team builds these parts the same way.
Place the label beside the box
Put the label to the right of the box in left-to-right languages. The label should be close enough that the two read as one choice.
Make the label clickable
Users often press the words, not the tiny square.
Title the group with a legend
When a set of checkboxes answers one question, give it a group title. In HTML, this is a fieldset with a legend, a structure that screen readers announce. UX Patterns asks teams to check for this structure.
Stack the options vertically
A vertical list is easy to scan, and each label has room to be read in full.
Make the tap area generous
The click area should be large enough to press with a finger. Keep extra space around each label so neighboring options are not hit by mistake.
Words matter too, but the wording rules belong to the microcopy lesson. Still, a few shape rules are part of the component. Avoid labels that force a user to uncheck a box to stop something.
Tip
Lay out a long set of options as one vertical stack inside a titled group. Only put checkboxes side by side when the options are very short and the screen has room.
What are the accessibility basics for checkboxes?
Accessibility means that people with different abilities and devices can still use a part. For a checkbox, four basics matter most. They also matter for the system's other parts, but this lesson keeps to the checkbox. The full set of standards belongs to the accessibility lesson.
A visible focus ring
A keyboard user must always see which box is active. Do not remove the ring to make the design look cleaner.
Keyboard use with Space
Your design must show focus clearly so the user knows Space will change the box.
Not relying on color alone
A checked box must look different from an unchecked one by shape, not only by color. The tick and the dash are the key signals. Color can add meaning, but it cannot be the only signal.
Enough contrast
The box border, tick, and label must stand out against the background. The exact color values belong to the color lessons.
Screen readers also need a clear name and state. Nord says every checkbox needs an accessible name, connected to its label. The label is linked to the box so the name is read out. Nord also says the indeterminate state is passed to assistive technology. So a screen reader can announce that a parent option is partly selected, even though the user cannot set that state directly.
Tip
Test your checkbox with the keyboard alone. Tab to the group, press Space on each option, and check that the focus ring moves and each state is clear without any color.
Worked example: the Gmail inbox
The Gmail inbox is a clear real example of checkboxes in action. Each email row has its own checkbox. A select-all checkbox sits at the top.
- 1
Step 1: Each row is an independent checkbox
Selecting one email checks only that row. The row checkboxes do not depend on each other, so the user can select any mix of emails.
- 2
Step 2: All rows selected
When every email is selected, the top select-all box shows a full tick. A source on the Indigo blog notes that when all rows are checked, the master box is checked too.
- 3
Step 3: Some rows selected
When only a few emails are selected, the top box cannot be fully checked or unchecked. It shows the indeterminate state, a line in the middle of the box. The Indigo post says the same thing happens in this case.
- 4
Step 4: Clicking the mixed box
Sources differ here. A team must choose one behavior and write it down.
Next, the team defines the component's states once in the design system. The goal is that any screen using the inbox pattern gets the same behavior. A sample definition might look like this.
Unchecked
No row is selected. The box is empty, and the label for the group is read by a screen reader as not selected.
Checked
Every row is selected. The box shows a full tick.
Indeterminate
Some rows are selected. The box shows a dash. Screen readers announce it as partly selected, and the state is set by the list, not by a direct click.
Hover and focus
On hover, the box border changes. With the keyboard, a clear focus ring appears, and Space changes the box.
Disabled
If a list cannot be selected, such as during a loading step, the box shows the disabled style and a short reason is shown nearby.
Tip
When you document a worked example, name the behavior of the mixed state. Teams often forget this step, and builders then pick different actions for the same box.
Check yourself
Try these two short scenarios. Each one needs the ideas in this lesson.
Quick check
A settings screen lets people choose which notifications to get by email, SMS, and push. Any combination is allowed, including none. The changes are saved when the user presses a Save button at the bottom. Which control fits best?
Quick check
On the same screen, a parent checkbox labeled All notifications sits above the three channel checkboxes. Only the email box is checked. What state should the parent show?
Summary
An input checkbox is a shared part for independent choices. Its box, tick, label, and click area should be defined once. Its states include unchecked, checked, and indeterminate for mixed groups, plus hover, focus, disabled, and error. Use a checkbox for several independent choices, a radio button for exactly one choice, and a toggle for an instant setting. Group checkboxes with a legend, stack them vertically, and make the label clickable. For accessibility, keep a visible focus ring, support Space, never rely on color alone, keep contrast high, and connect each label to its box so screen readers announce the name and state.
Sources
- GitLab Design: Checkbox component guidelines
- Nord Design System: Checkbox component
- Carbon Design System: Checkbox guidelines
- Basis Design System: Checkbox
- Nielsen Norman Group: Checkboxes design guidelines
- Emplifi Soul Design System: Checkbox design properties
- Telerik Design System: Checkbox overview
- Indigo engineering blog: Indeterminate checkboxes are weird (Gmail example)
- MDN Web Docs: HTMLInputElement indeterminate property
- Element UI pull request 9924: select-all behavior compared with Gmail
- Cleverence: Buttons vs. checkboxes vs. radio buttons
- Accessibility.build: Accessible switch and toggle guide
- Ivy Forms: Radio button vs checkbox
- UX Patterns: Checkbox pattern
- Cieden design book: Where and when to use checkbox design
- Design System Yellow: Checkbox (Medium)
- The Hangline: Radio buttons vs checkboxes in web forms
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.