Switch
A switch turns one setting on or off, and the change usually happens right away.
A real example
When you turn on dark mode, the screen changes to dark colors at once.
Main parts
- 01Visible label
- 02Interaction target
- 03Current state
- 04Keyboard behavior
Use it when
Use it for a saved on-or-off setting with a clear label.
Do not use it when
Never put it in a form where people must still press a separate Save button.
Name used in code
role="switch" 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.
Outcome: Use Switch to solve this user need without losing the current context. User context: When you turn on dark mode, the screen changes to dark colors at once. Recommended pattern: Switch. Why it fits: Use it for a saved on-or-off setting with a clear label. Do not use it when: Never put it in a form where people must still press a separate Save button. 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 Switch. Definition: A switch turns one setting on or off, and the change usually happens right away. 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.