Compliance status
This accessibility declaration applies to OTPS CMA-CGM Web site.
The OTPS CMA (https://tariff.cma-cgm.com/otps/home) site is not compliant with the Référentiel Général d'Amélioration de l'Accessibilité (RGAA) version 4.1.2.
CMA CGM is committed to making its OTPS CMA-CGM Web site accessible in accordance with Article 47 of French Law No. 2005-102 of February 11, 2005.
To this end, CMA CGM is implementing the following actions:
- An action plan for the year 2025
- A multi-year remediation plan at the group level and for each digital service is being developed.
Audit result
The conformity audit carried out by the company Wavestone on 17 october 2025 on the site in production reveals that 29 % of the applicable criteria of the RGAA version 4.1.2 are respected.
This score corresponds to an Access-Score D value.
Non-compliant criteria
List of non-compliant criteria
The 36 criteria not in compliance with the standard are:
- 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 colors used in interface components or graphic elements carrying information sufficiently contrasting (excluding special cases)?
- 5.1 - Does every complex data table have a summary?
- 5.7 - For each data table, is the appropriate technique used to associate each cell with its headers (excluding special cases)?
- 6.1 - Is every link explicit (except in special cases)?
- 7.1 - Is every script compatible with assistive technologies, if necessary?
- 7.3 - Can each script be controlled from the keyboard or any other pointing device (except in special cases)?
- 7.4 - For each script that initiates a context switch, is the user warned or does he have control over it?
- 7.5 - On each web page, are status messages correctly rendered by assistive technologies?
- 8.1 - Is every web page defined by a document type?
- 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.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.2 - In every web page, does the visible, information-carrying content remain present when style sheets are deactivated?
- 10.3 - Does the information on each web page remain comprehensible when style sheets are deactivated?
- 10.4 - On every web page, does the text remain legible when the font size is increased to at least 200% (excluding special cases)?
- 10.5 - In each web page, are the CSS declarations for element background and font colors used correctly?
- 10.7 - In each web page, for each element receiving focus, is the focus visible?
- 10.12 - In every web page, can text spacing properties be redefined by the user without loss of content or functionality (except in special cases)?
- 11.1 - Does each form field have a label?
- 11.3 - In each form, is every label associated with a form field having the same function and repeated several times in the same page or in a set of pages consistent?
- 11.4 - In each form, are each field label and its associated field next to each other (except in special cases)?
- 11.6 - In each form, does each grouping of fields of the same type have a caption?
- 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.3 - Is the "site map" page relevant?
- 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?
Drawing up this declaration of accessibility
Technologies used for production
The technologies used on the site are as follows:
- HTML5
- CSS
- JavaScript (client and page generation framework)
Test environnement
The rendering of content using assistive technologies has been tested in accordance with the test environment described in the referential:
- MS-Windows 10;
- Jaws 2023;
- Google Chrome.
The tests were carried out on MS-Windows 10 and Linux Fedora 42 operating systems.
Tools for assessing accessibility
The following tools were used to check accessibility:
- Web browser: Mozilla-Firefox, Waterfox, Google-Chrome ;
- Extensions:
- Web developper Tool Bar (Mozilla-Firefox and Google-Chrome);
- ARC ToolKit (Google-Chrome);
- Axe Dev Tools (Google-Chrome);
- Tanaguru Web Ext;
- Kontrast (mesure de contraste de couleurs);
- Wave / Aim (Mozilla-Firefox)
- Jaws 2023
- O·C·A·A
Site pages used for compliance verification
Feedback and contact
If you are unable to access any content or service, please contact our Accessibility team to be directed to an accessible alternative or to obtain the content in another form.
Recourse
Under French law, this procedure is to 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 one of the portal's services 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 use a stamp) to:
Défenseur des droits,
Libre réponse 71120,
75342 Paris Cedex 07.