Digital accessibility declaration

The compliance audit carried out by Wavestone on 26 February 2024 on the site in production revealed that 42% of the applicable criteria of RGAA version 4.1.2 were met. This score corresponds to an Access-Score value of D.

Non-compliant criteria

List of non-compliant criteria

The 42 criteria that do not comply with the standards are:

1.1 - Is there a text alternative for every image that provides information?
1.2 - Is every decorative image correctly ignored by assistive technologies?
1.3 - For each information-bearing image with a text alternative, is this alternative relevant (excluding special cases)?
1.6 - Does each image carrying information have a detailed description, if necessary?
2.2 - For each frame with a frame title, is this frame title relevant?
3.1 - On every web page, information doesn't have to be provided by color alone. Is this rule respected?
3.2 - On each web page, is the contrast between text color and background color sufficiently high (excluding special cases)?
3.3 - In each web page, are the colours used in interface components or graphic elements carrying information sufficiently contrasting (excluding special cases)?
4.1 - Does each pre-recorded time-lapse medium have a text transcription or audio description (except in special cases)?
4.4 - For any pre-recorded time-synchronized media with synchronized subtitles, are these subtitles relevant?
4.7 - Is each temporal medium clearly identifiable (excluding special cases)?
6.1 - Is every link explicit (except in special cases)?
7.5 - On each web page, are status messages correctly rendered by assistive technologies?
8.2 - For each web page, is the generated source code valid for the specified document type (excluding special cases)?
8.3 - Is the default language present on every web page?
8.5 - Does every web page have a page title?
8.6 - For each web page with a page title, is the title relevant?
8.7 - Is every language change indicated in the source code of every web page (except in special cases)?
8.9 - On every web page, tags must not be used solely for presentation purposes. Is this rule respected?
9.1 - Is the information on each web page structured by the appropriate use of headings?
9.2 - Is the structure of each web page consistent (excluding special cases)?
9.3 - Is every list on every web page properly structured?
10.1 - Are style sheets used to control the presentation of information on the website?
10.3 - Does the information on each web page remain comprehensible when style sheets are deactivated?
10.5 - In each web page, are the CSS declarations for element background and font colours used correctly?
10.7 - In each web page, for each element receiving focus, is the focus visible?
10.8 - For each web page, are hidden contents intended to be ignored by assistive technologies?
10.11 - For each web page, can content be presented without using both vertical scrolling for a 256px-high window and horizontal scrolling for a 320px-wide window (excluding special cases)?
11.1 - Does each form field have a label?
11.6 - In each form, does each grouping of fields of the same type have a caption?
11.9 - In each form, is the title of each button relevant (excluding special cases)?
11.10 - In each form, is the input control used appropriately (excluding special cases)?
11.11 - In each form, is the input check accompanied, if necessary, by suggestions for correcting input errors?
11.13 - Can the purpose of an input field be inferred to facilitate automatic filling of fields with user data?
12.6 - Can content grouping zones present on several web pages (header, main navigation, main content, footer and search engine zones) be reached or avoided?
12.7 - Is every web page equipped with an escape or quick-access link to the main content area (excluding special cases)?
12.8 - Is the tab order consistent on every web page?
12.9 - On every web page, navigation should be free of keyboard traps. Is this rule respected?
13.3 - Does every web page and every downloadable office document have an accessible version (except in special cases)?
13.4 - For each office document with an accessible version, does this version offer the same information?
13.5 - In every web page, does every cryptic content (ASCII art, emoticon, cryptic syntax) have an alternative?
13.9 - On each web page, can the content be consulted regardless of screen orientation (portrait or landscape) (excluding special cases)?
 

Drawing up this declaration of accessibility

Technologies used for production

The following technologies are used on the site:

1. HTML5
2. CSS
3. JavaScript (client and page generation framework)
    

Testing environment

The rendering of content using assistive technologies has been tested in accordance with the test environment described in the 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 39 operating systems.

Tools for evaluating accessibility

The following tools were used to check accessibility:

1. Web browser: Mozilla-Firefox, Waterfox, Google-Chrome.
2. Extensions: Web developper Tool Bar (Mozilla-Firefox and Google-Chrome).
3. LightHouse (Google-Chrome).
4. ARC ToolKit (Google-Chrome).
5. Axe Dev Tools (Google-Chrome).
6. Kontrast (colour contrast measurement).
7. Wave / Aim (Mozilla-Firefox)
8. JAWS 2023
9. O·C·A·A

Site pages used for compliance verification

1. Homepage
2. Newsletter subscription
3. Investor Registration Form (finance)
4. Our activities (video, editorial)​
5. Our publications (PDF downloads)
6. Search
7. Foundation > Our partners
8. Cookies Pop-in des cookies
9. Site map
    

Additional information to be published on the site

These 2 paragraphs must be added to the declaration published on your site by adapting the sample content provided.

Feedback and contact

If you are unable to access any content or service, you can contact the site manager to be directed to an accessible alternative or to obtain the content in another form. Send a message using the contact form. Contact the CMA CGM Communications Department.

Recourse

This procedure should be used in the following case: you have notified the website manager of a lack of accessibility that is preventing you from accessing content or services on the portal and you have not received a satisfactory response. Write a message to the Human Rights Defender. Contact the Rights Defender delegate in your region. Send a letter by post (free of charge, do not put a stamp on it) to: Défenseur des droits, Libre réponse 71120, 75342 Paris Cedex 07.