Interface Core A1 · Official standard

Checkbox

A checkbox is a box you can check or clear. Each choice can stand on its own.

Try an example
You might call it tick boxcheck box

Try an example

Checkbox

A real example

A person can choose email updates, product research, both choices, or neither one.

Main parts

  1. 01Visible label
  2. 02Interaction target
  3. 03Current state
  4. 04Keyboard behavior

Use it when

Use checkboxes when several choices may all be true, or for an optional agreement.

Do not use it when

Never use one for a setting that changes at once. A switch often explains that better.

Name used in code

<input type="checkbox">

Before you ship

Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery.

Request you can copy

Outcome: Use Checkbox to solve this user need without losing the current context. User context: A person can choose email updates, product research, both choices, or neither one. Recommended pattern: Checkbox. Why it fits: Use checkboxes when several choices may all be true, or for an optional agreement. Do not use it when: Never use one for a setting that changes at once. A switch often explains that better. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Checkbox. Definition: A checkbox is a box you can check or clear. Each choice can stand on its own. Release checks: Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

A1
How official is this term?

Official standard

A named standard sets the rules described on this page.

The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example.

Scope
HTML and ARIA
Document status
living standard
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · WHATWG · living standard HTML Living Standard — Checkbox input state Checkbox input state Scope: Web platform; direct scope: Checkbox input state Role here: Direct term reference Source covers: canonical name, definition, semantics, implementation Authority source · WHATWG · living standard HTML Living Standard Scope: Web platform Role here: Authority within stated scope Source covers: canonical name, definition, semantics, implementation Authority source · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 Scope: Web accessibility semantics Role here: Authority within stated scope Source covers: canonical name, definition, semantics, implementation

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.