top of page

AXA Mon Épargne Entreprises

AXA digital accessibility statement

Compliance status

This accessibility statement applies to the AXA Mon Epargne Entreprises website.

The website (https://bo-external.dev-partner2.shares.io/#/companies) is not compliant with the General Accessibility Improvement Framework (RGAA) version 4.1.2.
The detailed audit results are outlined below.

Test results

The compliance audit carried out by the company on September 26, 2025, on the production site reveals that 40% of the applicable criteria of RGAA version 4.1.2 are met.
This score corresponds to an Access-Score value of D.

Non-compliant criteria

List of non-compliant criteria

The 31 criteria that do not comply with the standard are:
 

  1. 1.1 – Does each image conveying information have a text alternative?

  2. 1.2 – Is each decorative image properly ignored by assistive technologies?

  3. 3.1 – On every web page, is information not conveyed by color alone?

  4. 3.2 – On every web page, is the contrast between text color and background color sufficiently high (except in special cases)?

  5. 3.3 – On every web page, are the colors used in interface components or graphical elements conveying information sufficiently contrasted (except in special cases)?

  6. 6.1 – Is each link explicit (except in special cases)?

  7. 6.2 – On every web page, does each link have a label?

  8. 7.1 – Is each script, if necessary, compatible with assistive technologies?

  9. 7.3 – Is each script controllable by keyboard and any pointing device (except in special cases)?

  10. 7.4 – For each script that initiates a context change, is the user warned or given control?

  11. 7.5 – On every web page, are status messages properly conveyed by assistive technologies?

  12. 8.2 – For each web page, is the generated source code valid according to the specified document type (except in special cases)?

  13. 8.4 – For each web page with a default language, is the language code relevant?

  14. 8.6 – For each web page with a page title, is this title relevant?

  15. 8.7 – On every web page, is each language change indicated in the source code (except in special cases)?

  16. 9.1 – On every web page, is information structured using appropriate headings?

  17. 9.2 – On every web page, is the document structure consistent (except in special cases)?

  18. 9.3 – On every web page, is each list properly structured?

  19. 10.3 – On every web page, does the information remain understandable when stylesheets are disabled?

  20. 10.7 – On every web page, for each element receiving focus, is the focus visible?

  21. 10.8 – For each web page, are hidden contents intended to be ignored by assistive technologies?

  22. 10.11 – For each web page, can the content be displayed without requiring both vertical scrolling for a window with a height of 256px and horizontal scrolling for a window with a width of 320px (except in special cases)?

  23. 10.13 – On every web page, are additional contents appearing on focus or hover of an interface component controllable by the user (except in special cases)?

  24. 10.14 – On every web page, can additional contents appearing via CSS styles only be made visible using keyboard and any pointing device?

  25. 11.1 – Does each form field have a label?

  26. 11.2 – Is each label associated with a form field relevant (except in special cases)?

  27. 11.5 – In each form, are fields of the same nature grouped together, if necessary?

  28. 11.10 – In each form, is input control used appropriately (except in special cases)?

  29. 11.11 – In each form, is input control accompanied, if necessary, by suggestions to help correct input errors?

  30. 12.9 – On every web page, navigation must not contain keyboard traps. Is this rule respected?

  31. 12.11 – On every web page, are additional contents appearing on hover, focus, or activation of an interface component reachable via keyboard if necessary?

Establishment of this accessibility statement

Technologies used for implementation

The technologies used on the site are as follows:

  • HTML5

  • CSS

  • JavaScript (client-side and page generation framework)
     

Testing environment

The rendering of content with assistive technologies was tested in accordance with the test environment described in RGAA 4.1.2:

  1. MS-Windows 10

  2. Jaws 2023

  3. Google Chrome
     

The tests were carried out on MS-Windows 10 and Linux Fedora 42 operating systems.

 

Tools used to assess accessibility

The following tools were used to verify accessibility:

  1. Web browsers: Mozilla-Firefox, Waterfox, Google-Chrome

  2. Extensions: Web Developer Tool Bar (Mozilla-Firefox and Google-Chrome)

  3. LightHouse (Google-Chrome)

  4. ARC Toolkit (Google-Chrome)

  5. Axe Dev Tools (Google-Chrome)

  6. Tanaguru Web Ext

  7. Kontrast (color contrast measurement)

  8. Wave / Aim (Mozilla-Firefox)

  9. Jaws 2023

  10. O·C·A·A

Pages of the site used for compliance verification

  1. Home

  2. Company dashboard

  3. Company details

  4. Create a company contact

  5. Tables

  6. Edit a member

Feedback and contact

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

Send a message via the contact form.

Contact AXA’s Communications Department.

Appeal procedures

This procedure should be used in the following case: you have reported an accessibility issue to the website manager that prevents you from accessing content or one of the portal’s services, and you have not received a satisfactory response.
 

Write a message to the Défenseur des droits

Contact the regional delegate of the Défenseur des droits.

​

Send a letter by post (free of charge, no stamp required) to:
Défenseur des droits
Libre réponse 71120,
75342 Paris Cedex 07

Digital accessibility statement

bottom of page