Danone is committed to making its web site accessible, in accordance with Article 47 of Law n° 2005-102 of 11 February 2005

To this end, it implements the following strategy and actions: [multiannual scheme coming soon]

What is digital accessibility?

An accessible website is one that allows people with disabilities to access its content and functionality without difficulty. An accessible site makes it possible, for example, to:

  • Navigate with text-to-speech and/or Braille (especially used by blind and visually impaired people).
  • Customize the display of the site according to users’ needs (increase or decrease text size, change colours, etc.).
  • Navigate without using the mouse (with the keyboard only, or via touch screen, voice control or a suitable device).

To achieve this, the site must comply with the standards in force when it is created and updated

Accessibility statement

Danone is committed to making its websites (Internet, Intranet and Extranet), and mobile apps in accordance with Article 47 of French law no. 2005-102 of February 11, 2005.

This accessibility statement applies to http://www.danone.com/fr

Compliance status

"danone.com" website only partially complies with the RGAA (France’s General Accessibility Improvement Guidelines) version 4.0 due to the non-conformities and derogations listed below.

Test results

The compliance audit carried out by Atalan in November 2020 reveal that it meets 54% of the criteria of RGAA 4.0.

Non-accessible content


List of non-compliant criteria:

  • 1.1 Does each image carrying information have a text alternative?
  • 1.2 Is each decoration image correctly ignored by assistive technologies?
  • 1.8 When an alternate mechanism is missing, each image of text conveying information must be replaced with styled text, if possible. Has this rule been followed?
  • 3.1 On each Web page, information must not be conveyed through colour only. Has this rule been followed?
  • 3.2 On each Web page, is the contrast between the text and background colours sufficient?
  • 3.3 On each web page, are the colours used in the interface components or graphic elements containing information sufficiently contrasted?
  • 6.2 On each Web page, does each link, apart from anchors, have a title?
  • 7.1 Does each script support assistive technologies, if necessary?
  • 7.3 Can each script be controlled through a keyboard and any pointing device?
  • 8.2 For each Web page, is the generated source code valid according to the specified document type?
  • 8.6 For each Web page with a page title, is this title relevant?
  • 8.7 On each Web page, is each change in the human language identified via the source code?
  • 9.1 On each Web page, is information structured by the appropriate use of headings?
  • 9.2 On each Web page, is the document outline coherent?
  • 9.3 On each Web page, is each list structured appropriately?
  • 10.2 On each Web page, is visible content still available when style sheets are disabled?
  • 10.3 On each Web page, is information still understandable when style sheets are disabled?
  • 10.5 On each Web page, are CSS declarations for background and foreground colours appropriate?
  • 10.6 On each Web page, can each link whose nature is not obvious be distinguished from the surrounding text?
  • 10.7 On each Web page, is the focus visible for each element that receives focus?
  • 10.8 For each web page, are hidden contents intended to be ignored by assistive technologies?
  • 10.12 On each web page, can the text spacing properties be redefined by the user without loss of content or functionality?
  • 10.13 On each web page, are additional contents appearing when focusing or hovering over an interface component controllable by the user (except in special cases)?
  • 11.1 Does each form field have a label?
  • 12.8 On each Web page, is tabbing order consistent?
  • 12.11 On each web page, are the additional content appearing when hovering, focusing or activating an interface component accessible by keyboard if necessary?
  • 13.3 On each Web page, does each office document that can be downloaded have an accessible version if necessary?
  • 13.8 On each Web page, can each moving or blinking content be controlled by the user?

Content not subject to the obligation of accessibility

  • YouTube video player.
  • Video published before September 23rd, 2020.
  • Some video may contain accessibility issue (absence of close caption and / or transcript), however they are not subject to the accessibility obligation due to the fact that they were publish before September 23rd, 2020. Danone is in the process of finding way to improve accessibility for future videos that will be publish on the website.

Production of this accessibility statement

This statement was issued on November the 24th, 2020.
Technologies used to create the website

  • HTML5
  • CSS
  • SVG
  • JavaScript
  • ARIA

Test environment
The content playback checks were performed with the following browser and screen reader combinations:

  • Firefox 79 + NVDA 2020.2
  • Internet Explorer 11 et Jaws 2019
  • Android Talkback et Chrome 84

Tools for assessing accessibility:

  • Color Contrast Analyser
  • Outil de développement Firefox
  • Web Developer (extension Firefox)

Scope of the audit:

Feedback and contact

If you are unable to access any content or service, please contact the digital accessibilité manager who will provide an accessible alternative or offer the content in another form.


You should follow this procedure in the following situation:

You have notified the digital accessibility manager of an accessibility problem that prevents you from accessing any part of the content or services of the portal and you have not received a satisfactory response.