You are currently on Anvil1, which is now in maintenance mode. Visit Anvil2 to get the latest version of the design system.
components / Actions and Inputs

Toggle Switch


Toggle Switch Labels

Toggle Switch labels are on the right side of the toggle element. They generally have two pieces: the action being taken, and the subject matter.

Label Help

Labels can have a help icon with a tooltip to provide additional context to a label.

Action Only

Sometimes it make sense for the toggle's subject to be separated from the toggle itself. This is useful in a list-context or if the subject is tied to a more complex UI component such as a Card, Table, or Page title.

Action Only With Cards

Action Only In a List

When scanning a set of options, it may make sense to separate the toggle's subject to the left. This can be done with caution: the user should be able to understand they are toggling the text to the left on or off.

No Label

A toggle switch can also have no label when the context of what it turns on or off can be clearly understood. A tooltip can also be applied to describe the toggle's current state.


Constant Labeling

The Toggle Switch label is always the same text. It describes what the "ON" state of the toggle is. The label should not switch based off the toggle's state.

Positive Wording

Labels in general should be positive. Since the label and toggle are generally thought of as turning something on, labels should reenforce this. Examples include “Show”, “Hide”, “Activate”, “Group [by]”, “Track”, and “Activate”. Negative labeling can be used with caution, if it makes sense to a user to perform a negative action.


Immediate Results

In general, toggle switches should provide immediate feedback that something has occurred.

Consider using a Checkbox when a button needs to be pressed in for the setting to take place.

In a form

A Toggle Switch can also be added into a Form component.


Disabled State


Best Practices

  • Toggle Switches in general should provide immediate results.
  • Toggle Switch options should be reducible to an On/Off choice.
  • Labels should be framed positively.
  • If using a Tooltip, display the current Toggle Switch state.
  • When in doubt, use the label to describe both the action and the subject of the Toggle Switch.
  • Use visual indicators such as disabled and active states on other elements to reenforce the state of the Toggle Switch.

Content Guidelines

Give a descriptive, direct label

The toggle switch label should describe what the control does when it is turned on. Rule of thumb: say the label name and add an “on/off”.

Use sentence case (capitalize only the first word and proper nouns) so control labels are easy to scan. Do not use periods for short phrases or single sentences.

Give the user the information they need to make an informed decision

The toggle switch label might not give the required information and context they need to make an informed decision about the option.

Inline help is the best option for this situation because it requires no user interaction and is always visible. Keep inline help to 1-2 sentences. Use the content guidelines for inline help.

Avoid using a tooltip to communicate this kind of information about an option. It’s an additional step for users to mouse over the tooltip to reveal its information, and users can’t refer to the tooltip content and take action at the same time.


Components

  • When needing a Yes/No choice, or needing to submit a form, use a Checkbox.
  • For more complex, mutually exclusive choices, use a Button Toggle or Radio.

Patterns

  • Form design pattern for how related controls are ordered.

Importing

import { ToggleSwitch } from '@servicetitan/design-system';