Button

Angular

See content

Blazor

See content

Buttons are interactive elements, they allow users to take actions and make choices

Usage

Buttons are call to action, present on almost all interfaces. They allow users to interact with your system. They can have different shape, size and color. They are interactive elements.

When to use

If the user must trigger an action, like:

  • Submitting a form

  • Beginning a new task or go to the next one

  • Displaying information hidden before

  • Specify a new or next step in a process

If this action redirects the user to a new page, use a hyperlink instead of a button.

Anatomy

  1. Icon (optional): Use it to convey more meaning

  2. Label: Text that indicates the result of selecting the button.

anatomy button

Buttons can contain a combination of a clear label and an icon. The content should always be centered inside the button.

Icon

An icon is easier to memorize than a single label if you have large screen. If not, for text buttons, text should be as short as possible, while clearly describing the action that the button performs.

If the button contains exclusively an icon, use content description for describing the action associated with the button.

Label

The label must indicate the action of the button and should be speaking in the sense of the user's understanding, rather than in the system's language. The label must be short.

Types

Accent

Accent button is used for the most important action to the screen. The button’s color contrast with the rest of the interface to attract eyes of the user. There is only one primary button per screen.

Primary

Primary buttons are used for regular actions. It can be placed several times on the same screen.

Secondary

Secondary buttons are used for secondary actions.

Disabled

Disabled button is a button that can’t be used. Its usage depends on the context. It could be activated if the right data is entered. Use it to indicate that the user can do this action and explain why (for example, with a tooltip).

Disabled buttons should be avoided as much as possible as it has poor contrast and can confuse users.

Placement

Generally, the primary button is on the right and the secondary button on the left. It is important to keep the same logic of placement everywhere in your application.

Button with opposite actions (examples: Discard and Save) must be placed together.

πŸ™ˆ Keyboard navigation: Pay attention to build a logical path through keyboard navigation.

Dos & Don'ts

Do

Button labels use sentence case (Capitalize only the first letter or proper name) and are as short as possible. Button indicates an action.

Don’t

Use label that clearly indicates what happens when the button is activated.

Do

A button represents an action and then, label needs to reflect the action that a user is taking which is commonly a verb. Favor verbs first.

Don’t

Avoid nouns & adjectives as labels for buttons. They can be unclear, muddled and/or disorienting for the user.

Do

Use no more than 4 words for button label’s. It have to stand in one line. Text must describe action that happens when it is activated.

Don’t

Do not use wordy labels, be concise to gain in clarity.

Do

Button labels use sentence case (Capitalize only the first letter or proper name) and are as short as possible. Button indicates often an action.

Don’t

Use label that clearly indicates what happens when the button is activated.

Do

When we use 2+ buttons, we have to prioritize buttons information.

Don’t

When we use 2+ buttons, avoid to insert multiple accent buttons.

Do

For Mobile buttons, apply margins.

Don’t

Do not use a full screen length button for mobile buttons.

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.