Danone endeavours to provide its website in accordance with **EN 301 549 / WCAG 2.1 AA** and to take into account the legal framework for private providers under the **Accessibility Reinforcement Act (BFSG/BFSGV)**.

https://www.danone.com/ is not in compliance with the general accessibility improvement framework.

This accessibility statement applies to https://www.danone.com/, including the following localized paths:

danone.com/de/de (DE), danone.com/de/en (EN)

This declaration was prepared on 19 May 2025.

The audit carried out by Razorfish France reveals:

• 47% of the criteria of RGAA version 4.1.2 are met.
• The average compliance rate of the online service is 81%.

• HTML5
• CSS3
• JavaScript 

• NVDA 2024.4.2 and Chrome

• Accessibility Insights for Web v2.46.0
• RGAA Wizard v4.1.2
• Web Developer Toolbar
• Browser Inspector

1. Cross-sectional element - header, footer, breadcrumb
2. Homepage
3. Contact
4. Accessibility Statement
5. Legal notice
6. About us
7. Careers
8. Shareholders
9. Danone Overview
10. Newsroom
11. Results center
12. evian
13. Research

Nonconformity

• 1.2 Is every decorative image properly ignored by assistive technologies?
• 1.3 For each information-carrying image with a textual alternative, is this alternative relevant (except in special cases)?
• 1.6 Does each information-carrying image have a detailed description, if necessary?
• 3.2 Is the contrast between the colour of the text and the colour of its background sufficiently high on each web page (except in special cases)?
• 4.1 Does each pre-recorded time-based media have, if necessary, a verbatim transcript or an audio description (except in special cases)?
• 4.3 Does each pre-recorded synchronised time-based media have, if necessary, synchronised captions (except in special cases)?
• 4.4 For each pre-recorded synchronised time-based media with captions, are these captions relevant?
• 4.5 Does each pre-recorded time-based media have, if necessary, synchronised audio description (except in special cases)?
• 4.7 Is each time-based media clearly identifiable (except in special cases)?
• 4.11 Is the playback of each time-based media, if necessary, controllable by the keyboard and by any pointing device?
• 4.13 Is every time-based and non-time-based media compatible with assistive technologies (except in special cases)?
• 5.1 Does every complex data table have a summary?
• 6.1 Is each link explicit (except in special cases)?
• 7.1 Is each script compatible with assistive technologies, if necessary?
• 7.3 Is each script controllable by the keyboard and by any pointing device (except in special cases)?
• 7.4 For each script that initiates a context switch, is the user notified or in control?
• 8.2 Is the generated source code of each web page valid according to the specified document type (except in special cases)?
• 8.7 Is each language change indicated in the source code on each web page (except in special cases)?
• 8.9 Are tags not used solely for presentation purposes?
• 9.1 Is the information on each web page structured by the appropriate use of headings?
• 9.3 Is each web page properly structured?
• 10.1 Are style sheets used to control the presentation of information?
• 10.4 Is the text on each web page legible when the font size is increased by at least 200% (except in special cases)?
• 10.5 Are CSS declarations of background and font colours used correctly?
• 10.6 Is every non-obvious link visible compared to the surrounding text on every web page?
• 10.7 For each element receiving focus, is the focus visible on every web page?
• 10.8 Is hidden content intended for specific contexts correctly ignored by assistive technologies?
• 10.9 Is information not conveyed solely by shape, size or position?
• 10.10 Is information not given only by shape, size or position – and is the implementation relevant?
• 10.13 Can additional content that appears on focus or hover on an interface component be controlled by the user (except in special cases)?
• 11.1 Does every form field have a label?
• 11.2 Is each label relevant to the associated form field (except in special cases)?
• 11.5 In each form, are fields of the same nature grouped together, if necessary?
• 11.9 In each form, is the title of each button relevant (except in special cases)?
• 12.3 Is the 'site map' page relevant?
• 12.6 Can content clustering areas present in multiple web pages (header, main navigation, main content, footer, and search areas) be reached or skipped?
• 13.3 On each web page, does every downloadable office document have an accessible version, if necessary (except in special cases)?
• 13.5 On each web page, does every cryptic content (ASCII art, emoticons, cryptic syntax) have an alternative?
• 13.8 On each web page, is every moving or flashing piece of content controllable by the user?
• 13.11 On each web page, can actions triggered by a pointing device at a single point on the screen be cancelled (except in special cases)?

If you are unable to access any content or service, please contact the Digital Accessibility Officer, who will provide you with an accessible alternative or offer the content in an alternative form:

• Send us a message
• Contact

If you have reported a barrier to us and have not received a (satisfactory) response within four weeks, you may contact – for private offers under the BFSG – the Market Surveillance Authority of the German Länder for the Accessibility of Products and Services (MLBF). Please use the official contact channel of the MLBF (e.g., via the federal/ Länder accessibility portal).