AXA digital accessibility statement

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

The savings website (https://www.axa-mon-epargne-entreprises.com/) is non‑compliant with the General Accessibility Improvement Reference Framework (RGAA) version 4.1.2.
The details of the audit results are outlined below.

Test results

Non-compliant criteria

The 26 criteria that are non‑compliant with the reference framework are:

​

1. 1.2 – Is each decorative image correctly ignored by assistive technologies?

2. 1.3 – For each information‑carrying image that has a text alternative, is that alternative relevant (except for special cases)?

3. 3.2 – On each web page, is the contrast between the text color and its background color sufficiently high (except for special cases)?

4. 6.1 – Is each link explicit (except for special cases)?

5. 7.1 – Is each script, when necessary, compatible with assistive technologies?

6. 7.5 – On each web page, are status messages correctly conveyed by assistive technologies?

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

8. 8.6 – For each web page that has a page title, is that title relevant?

9. 8.9 – On each web page, are tags not used solely for presentation purposes? Is this rule respected?

10. 9.1 – On each web page, is the information structured through the appropriate use of headings?

11. 9.2 – On each web page, is the document structure coherent (except for special cases)?

12. 9.3 – On each web page, is each list correctly structured?

13. 10.3 – On each web page, does the information remain understandable when style sheets are disabled?

14. 10.4 – On each web page, does the text remain readable when font size is increased up to at least 200% (except for special cases)?

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

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

17. 11.4 – In each form, are each field’s label and its associated field placed next to each other (except for special cases)?

18. 11.5 – In each form, are fields of the same type grouped together when necessary?

19. 11.6 – In each form, does each grouping of similar fields have a legend?

20. 11.10 – In each form, is input validation used appropriately (except for special cases)?

21. 12.6 – Can content grouping areas present on several web pages (header, main navigation, main content, footer, and search engine) be accessed or skipped?

22. 12.7 – On each web page, is a skip link or quick access link to the main content area present (except for special cases)?

23. 12.8 – On each web page, is the tab order coherent?

24. 12.9 – On each web page, does navigation avoid containing any keyboard traps? Is this rule respected?

25. 13.2 – On each web page, is the opening of a new window not triggered without user action? Is this rule respected?

26. 13.3 – On each web page, does each downloadable office document have an accessible version when necessary (except for special cases)?

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 11

2. NVDA 2024

3. Google Chrome
    

The tests were carried out on MS‑Windows 11 operating systems.

​

Tools used to assess accessibility

The following tools were used to verify accessibility:

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

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

A. Tanaguru Web Ext

B. HeadingsMap

C. WCAG Contrast Checker (color contrast measurement)

D. Wave (Google Chrome)

3. NVDA 2024

4. O·C·A·A