Switch

Angular

See content

Blazor

See content

Switches are digital on/off switches.

Usage

Switches toggle the state of a single item on or off. They are best used for changing the state of system functionalities and preferences.

General guidelines

Use a switch when a user can toggle between two opposing states, such as on and off.

Switch action has immediate results, giving users the freedom to control their preferences as needed.

The switch has always a default value, make sure to deliver immediate results that don't require the user to click Save or Submit to apply the new state.

Label

The option that the switch controls, as well as the state it's in, should be made clear from the corresponding inline label.

Avoid creating a switch that includes the text on and off within the graphic itself. The switch alone should be enough.

Put the label above or on the left of the switch (in the reading direction of your users).

Keep labels for toggle switches short and direct, don't use excess phrases. The description should be on what the control will do when the switch is on, don't make neutral or ambiguous sentences.

Anatomy

A switch is successfully toggled when the switch thumb slides to the other side of the track upon user interaction.

  1. Thumb

  2. Track

Do's & Don'ts

  • Use the accent color to identify the ON state.

  • The switch should animate when the user toggles it.

  • The switch relies on both color and slide for visual cues, there's no need to use the labels on/off.

  • Don't use switch if the result doesn't take immediate effect and needs a validation. Use radio button or checkbox instead.

  • Don’t use on and off for the switch label.

Do

Switches are used to depict an immediate effect.

Don’t

Do not use components like checkboxes for activate action.

Do

Switches are used like themselves, acting as a stand alone control.

Don’t

Do not use switches with buttons like “send”, “submit” or “save”. Switches are acting as a stand-alone control in general cases.

Do

Use checkbox to collect consent from the user.

Don’t

Do not use switches when there’s no immediate effect.

Log in

Log in with Michelin ID

To connect to the Design System, I will need:

  • A Michelin ID (e.g. F012345)
  • Double authentification (with the NetIQ application or by SMS)
  • A password associated with your Michelin ID

I don’t have a Michelin ID and/or email

In order to connect to the Design System, I need:

  • A user ID or an email
  • A password

If you have never accessed the Design System, you can request access via this link.