This page is a reusable-component split from the source checklist row Checkbox / radio / switch. The source row remains authoritative.
- Job
- Choose
- Requirement
- must specify if forms in chrome
- States / rules
- States + label
- Specified means
- Not separately stated in this row.
- Hardest context
- Disabled why
Theme switch
Switch with no label
Preview
Preview — not a published component API.
Usage
Job: Choose.
A consuming product should document the job, its rules, and the hardest context before treating the component as specified.
When not to use
Do not use for a choice that requires a separate Save action to take effect; switches imply immediate state change.
Variants
The checklist row does not authorize this page to invent a final component API. Where the source rule names a variant, preserve it; otherwise keep the implemented variant set minimal and job-driven.
States & behavior
States + label
Default, Hover, Focus, Active/Pressed, and Disabled apply to interactive controls. Error, Loading, Empty, and Success apply where the component takes or reports data.
Accessibility
- Use native semantics whenever they match the job.
- Keep keyboard focus visible and distinct from hover.
- Do not rely on color alone for state.
- Maintain touch-operable targets and no hover-only actions.
- For composite/overlay controls, document focus movement, Escape, and return focus as applicable.
Responsive behavior
Document sm/md/lg behavior explicitly: whether the component reflows, collapses, changes density, or stays structurally the same. Preserve touch targets and avoid hover-only behavior.
Theme comparison
The component job and interaction contract stay stable while product expression changes.
Tokens
Bind the implementation to semantic roles for surface, text, border, focus, spacing, shape, and motion as needed. Actual token names must come from the implemented Foundation; this demo deliberately does not mint package-level token names.
Code / Storybook
When this component exists in code, this section should link to its source and Storybook stories for executable states, Controls, viewport, accessibility checks, and interaction tests. The documentation page remains responsible for job, guidance, source contract, product decisions, themes, and Catalog lineage.