Accessibility Statement

Compliance Status 

https://www.emeis.com/en is partially compliant with the General Accessibility Improvement Framework (RGAA).

Test Results

The compliance audit carried out by Arneo shows that 70% of the criteria from RGAA version 4.1.2 are met.

Non-Accessible Content

Non-Compliance Issues

1.2 – Is each decorative image properly ignored by assistive technologies?
3.2 – On every web page, is the contrast between the text color and its background color sufficiently high (excluding specific exceptions)?
6.1 – Is each link explicit (excluding specific exceptions)?
6.2 – On every web page, does each link—except anchors—have a label?
7.1 – Is each script, when necessary, compatible with assistive technologies?
7.3 – Is each script operable using both a keyboard and any pointing device (excluding specific exceptions)?
7.4 – For each script that initiates a context change, is the user warned or in control of it?
7.5 – On every web page, are status messages properly conveyed to assistive technologies?
8.2 – For each web page, is the generated source code valid according to the specified document type (excluding specific exceptions)?
8.8 – On every web page, is the language code of each language change valid and relevant?
9.1 – On every web page, is information structured using appropriate headings?
9.3 – On every web page, is each list properly structured?
9.4 – On every web page, is each quotation correctly marked up?
10.4 – On every web page, does the text remain readable when font size is increased up to at least 200% (excluding specific exceptions)?
10.7 – On every web page, is focus visibility ensured for each focusable element?
10.13 – On every web page, are additional contents that appear on focus or hover over an interface component controllable by the user (excluding specific exceptions)?
11.5 – In every form, are fields of the same type grouped together when necessary?
12.11 – On every web page, are additional contents that appear on hover, focus, or activation of an interface component reachable via keyboard when necessary?
13.3 – On every web page, does each downloadable office document have an accessible version when necessary (excluding specific exceptions)?

Preparation of this Accessibility Statement

This statement was made on February 21, 2025. It was last updated on March 13, 2025.

Technologies Used for the Audit

· HTML

· CSS

· Javascript

· PHP (Drupal)

Testing Environment

Content rendering checks were carried out using the combinations provided in the RGAA reference base, with the following versions:

  - On macOS using Chrome and VoiceOver

  - On Windows using Firefox and NVDA

Tools Used to Evaluate Accessibility

· Web Developer Toolbar

· HeadingsMap

· WCAG Contrast checker

· Component Inspector

· W3C HTML Validator

· RGAA Checker

Website Pages Subject to the Compliance Audit

· Home https://www.emeis.com/en 

· Contact https://www.emeis.com/en/lets-talk 

· Legal notices https://www.emeis.com/en/legal-information-terms-use-and-intellectual-property 

· Search https://www.emeis.com/en/search?text=emeis 

· Standard Content https://www.emeis.com/en/search?text=emeis 

· News List https://www.emeis.com/en/spotlight 

· News https://www.emeis.com/en/spotlight/mental-health/mental-disorders-hidden-face-connected-teenagers 

· General shareholders meeting https://www.emeis.com/en/investors-shareholders/investors-shareholders/annual-general-meetings/general-shareholders-2

Feedback and Contact

If you are unable to access any content or service, you can contact Emeis to be directed to an accessible alternative or to obtain the content in another format.

· Send a Message https://www.emeis.com/en/lets-talk