Template éditorial

subtitle in H5

This is an introduction text in Bold in 18px Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut non faucibus sem. Phasellus purus quam, pulvinar sed elit nec, tempor gravida diam.

subsubtile in H6

This is a paragraph text in 16px regular. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut non faucibus sem. Phasellus purus quam, pulvinar sed elit nec, tempor gravida diam. Nam ut mi nibh. Nam hendrerit odio at neque bibendum, quis viverra purus fermentum.

Lorem

Ipsum

Dolor

Sit

Amet

Consectetur

Adipiscing

Elit

Ut

Nulla ultricies, sapien non placerat rutrum, ligula turpis placerat enim, Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut non faucibus sem. Phasellus purus quam, pulvinar sed elit nec, tempor gravida diam. Nam ut mi nibh. Nam hendrerit odio at neque bibendum, quis viverra purus fermentum. Nulla ultricies, sapien non placerat rutrum, ligula turpis placerat enim, Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut non faucibus sem. Phasellus purus quam, pulvinar sed elit nec, tempor gravida diam. Nam ut mi nibh. Nam hendrerit odio at neque bibendum, quis viverra purus fermentum. Nulla ultricies, sapien non placerat rutrum, ligula turpis placerat enim, Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut non faucibus sem. Phasellus purus quam, pulvinar sed elit nec, tempor gravida diam. Nam ut mi nibh. Nam hendrerit odio at neque bibendum, quis viverra purus fermentum. Nulla ultricies, sapien non placerat rutrum, ligula turpis placerat enim, Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut non faucibus sem. Phasellus purus quam, pulvinar sed elit nec, tempor gravida diam. Nam ut mi nibh. Nam hendrerit odio at neque bibendum, quis viverra purus fermentum. Nulla ultricies, sapien non placerat rutrum, ligula turpis placerat enim,

APPLY TO YOUR DASHBOARD

  • Use layout to create a hierarchy between data.

  • Use title and subtitle with different size of font to create understandable context to your data.

subtitle in H5

Digital accessibility refers to the universal ability of different users and help devices to access the content and functionality of a digital product or service, regardless of their physical or cognitive abilities. Digital devices must be designed in order to make sure that understanding, interaction and navigation are easy for everyone. Digital accessibility concerns us all, because each and every one of us may be faced with a disability or impairment in the course of our lives.

For example, disability or impairment situational, temporary or permanent.

subtitle in h5

The accessibility guidelines and criteria have been organized into four design principles. WCAG contents are based of principles P.O.U.R. These are Perceivable, Operable, Understandable and Robust.

Web Content Accessibility Guidelines (WCAG) 2.1
  • PERCEVAIBLE

    • Visual and auditory perception facilitated

    • Non-textual content has equivalents

  • OPERABLE

    • Orientation of the user during navigation

    • Functionalities accessible with the keyboard

    • Sufficient time for the user to perform the actions

    • Content not likely to cause epileptic

  • UNDERSTANDABLE

    • Pages are navigable in a predictable manner

    • Users are assisted in correcting input errors

  • ROBUST

    • Pages are navigable in a predictable manner

    • Users are assisted in correcting input errors

subtitle in h5

When designing an application or website, developers and designers need to consider the criteria of the RGAA and WCAG. These guidelines help ensure accessibility and usability for all users.

  • DESIGNERS

    • Functional design:

    • Table, images, forms, navigate, consult

    • Graphic design:

    • Color, presentation

    • Multimedia design:

    • Video, sub-title, audio

  • DEVELOPPERS

    • Frames

    • Pictures

    • Links

    • Mandatory elements

    • Structuring of information

    • Presentation of information

    • Forms

    • Navigation

    • Consultation

The 6 pillars

Eco-design relies on six fundamental pillars

  • A MINDSET

    Integrate the environment as a qualitative criteria of any project.

  • THINK FUNCTIONAL UNIT

    You do not eco design an app, you eco design a business action

  • LIFE CYCLE ASSESSMENT

    Think through the global life cycle of a product from raw materials to its end life.

  • ENVIRONNEMENTAL KPIs

    Integrate several KPIs (such as greenhouse effect, toxicity, resources consumption etc).

  • FULL ARCHITECTURE INTEGRATION

    Keep in visibility the full architecture picture (servers, data centers and network)

  • GLOBAL CONTEXT

    Take into consideration all the environment of a product (partners, suppliers etc)

The French Institut Numérique Responsable created a handbook to provide a framework based on the triptych:

  • PEOPLE

    Reduce the social gap and improve living conditions through digital technology.

  • PLANET

    Reduce the environmental footprint of digital technology.

  • PROSPERITY

    Digital technology, as a lever for growth, must be an opportunity for everyone.

PRINCIPLE OF FRUGALITY

Define the primary need and eliminate the non essential !

  • ABOUT 45%

    of the functionalities requested are never used

  • 70%

    are not essential

The definition of the need is therefore a crucial step and each functionality must be challenged by the Product Owner or the UX designer. The project's stakeholders can base their reflections on the functional unit. The functional unit corresponds to the main function that the service fulfills and often translates into a business act.

QUESTIONS TO ASK

First question to ask is "For who this digital service will be needed ?"

  • Is there a user need to use digital for this service?

  • Are there other non-digital solutions to meet this user's need?

  • What are the real user needs that justify the creation of the service?

  • Does the added value of the service justify the mobilization of the resources required for its creation?

  • Do we create more value than we destroy?

  • Is this functionality really necessary? Can we do it otherwise?

  • What would happen if we did not have it?

  • What are the risks of a rebound effect when using the service?

Sign in

I have a Michelin ID and/or email

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

  • A Michelin ID (e.g. F012345)
  • A double authentification (with ForgeRock application or SMS)
  • A password associated to a 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 never logged into the Design System, you can submit an access request using this link: Request an access