Link

Angular

See content

Blazor

See content

Links are navigational elements and can be used inline with text or on their own.

Usage

Links provide a lightweight option for navigation but like other interactive elements, too many links will clutter a page and make it difficult for users to identify their next steps. This is especially true for inline links, which should be used sparingly.

When to use

Use it when you want the user to:

  • Navigate to another page of the application

  • Go to another website

  • To propose a shortcut to the user

  • To go up or down in the page, etc.

Anatomy

  1. Label: Communicates what is being linked to.

Types

Internal Link

This type of link redirects the user to something inside the actual website.

External link

This type of link redirects the user to another website. The link should open into a new tab. The icon indicates that is an external link.

Moreover, it is necessary to inform the user of this change in context. Therefore, in addition to using target="_blank", it is necessary to add an indication (such as "new window" or "new tab") either directly in the link label (e.g., <a>Michelin Podcasts (new window)</a>) or in the title tag as a complement to the label (e.g., <a title="Michelin Podcasts: New tab">Michelin Podcasts</a>).

Accessibility

The link name/title (contained between <a> and </a>, alt="[link destination]" for link images, aria-label or aria-labelledby) must never be empty and must be explicit in context.

Explicit implies that among the text, the link must be underlined so as not to confuse it and understand that it has a target.

The visible name must be contained in the accessible name. The title attribute must therefore always include the link name.

If the link redirects to an external page with target="_blank", the user must be informed (either in the label itself, or via a title attribute). In the case of our Angular component for example, we have added ": New window" in the title attribute when the link has a target="_blank".

If the links are identical in the page (label + context), they must have the same destination.

Do's & Don'ts

  • Don't use a link to trigger an action, use a button instead.

  • The label must indicate where it will redirect when the user clicks on the link.

  • On hover, the link's color must change.

  • When the user has already clicked once on the link, change its color to show to the user that he already has clicked on the link.

When the link is focused, pressing the Enter key must open it.

Avoid click here or here, as the user has no information on the target page

Do

Do use the links inside the body text. If you need to add a noticeable link, think about another call to actions like buttons for instance.

Don’t

Do not add link inside header. Links should be inside the body text.

Do

Links should be clear and straight to the point for accessibility. Links need to be understandable so that the user can anticipate what will happen when they click.

Don’t

Avoid “click here” or “here”, as the user has no information on the target page.

Do

When the user has already clicked once on the link, change its color to show to the user that he/she already has clicked on the link.

Don’t

Don’t keep the same color after the user clicked on the link.

Do

Decide between the link and the button according to the use.

Don’t

Do not mix between link and button. Select a component according to its function.

Do

The accessible name must include at least the visible name. Either they are identical, or the accessible name is equal to the visible name plus additional information (e.g., Visible name + 'New tab').

Don’t

The accessible name does not include the visible name or the necessary additional information is not provided.

Do

To avoid being confused with the text, ALL links must be underlined.

Don’t

Merely changing the color IS NOT sufficient to indicate the presence of a link.

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.