

Accessibility
Accessibility Statement
Compliance status
This accessibility declaration applies to current website
www.cevalogistics.com. The website is not compliant with the
General Accessibility Improvement Framework (RGAA) version
4.1.2.
The details of the audit results are stated below.
Test Results
The compliance audit conducted by Périscope Créations on May 3, 2024, and updated on June 20, 2025, on the production site revealed that 61% of applicable criteria of RGAA version 4.1.2 are met.
Multi-Year Plan 2024-2026
CEVA Logistics is currently working on a comprehensive remediation plan for all of its assets, which will result in a detailed roadmap for 2024-2026 by the end of 2025.
Non-compliant criteria
List of non-compliant criteria:
- Criterion 1.2: Is each decorative image correctly ignored by assistive technologies?
- Criterion 2.2: For each frame with a frame title, is the title relevant?
- Criterion 3.2: On each web page, is the contrast between text color and background color sufficiently high (excluding special cases)?
- Criterion 3.3: On each web page, are the colors used in interface components or graphic elements conveying information sufficiently contrasted (excluding special cases)?
- Criterion 4.1: Does each pre-recorded time-based media have, if necessary, a text transcript or audio description (excluding special cases)?
- Criterion 4.3: Does each pre-recorded synchronized time-based media have, if necessary, synchronized subtitles (excluding special cases)?
- Criterion 4.7: Is each time-based media clearly identifiable (excluding special cases)?
- Criterion 4.9: For each non-time-based media that has an alternative, is the alternative relevant?
- Criterion 4.13: Are both time-based and non-time-based media compatible with assistive technologies (excluding special cases)?
- Criterion 5.5: For each data table with a title, is the title relevant?
- Criterion 6.1: Is each link explicit (excluding special cases)?
- Criterion 7.1: Is each script, if necessary, compatible with assistive technologies?
- Criterion 7.3: Can each script be controlled by both keyboard and pointing device?
- Criterion 7.4: For each script that initiates a context change, is the user warned or in control?
- Criterion 8.2: On each web page, is the generated source code valid according to the specified document type (excluding special cases)?
- Criterion 8.4: For each web page with a default language, is the language code relevant?
- Criterion 10.2: On each web page, does the visible content conveying information remain present when stylesheets are disabled?
- Criterion 10.3: On each web page, does the information remain understandable when stylesheets are disabled?
- Criterion 10.5: On each web page, are CSS declarations for background and font colors correctly used?
- Criterion 10.7: On each web page, for each element receiving focus, is the focus indicator visible?
- Criterion 10.9: On each web page, is information not conveyed solely by shape, size, or position?
- Criterion 10.14: On each web page, can additional content appearing only via CSS be made visible via keyboard and any pointing device?
- Criterion 11.5: In each form, are fields of the same type grouped when necessary?
- Criterion 11.11: In each form, is data validation accompanied, if necessary, by suggestions to help correct input errors?
- Criterion 12.11: On each web page, are additional contents appearing on hover, focus, or component activation keyboard-accessible when necessary?
- Criterion 13.5: On each web page, does each cryptic content (ASCII art, emoticons, cryptic syntax) have an alternative?
- Criterion 13.11: On each web page, can actions triggered by a single-point pointing device be undone (excluding special cases)?
Exemptions for disproportionate burden
No exemption identified
Content not subject to accessibility requirements
No content not subject to accessibility requirements
Drawing up this declaration of accessibility :
Technologies used for the website development
- HTML
- CSS
- JavaScript
- PHP
Test environment
- Google Chrome
- Mozilla Firefox
Tools for auditing accessibility
- Web Developper Toolbar
- Component Inspector
- RGAA Assistant
- Color Contrast Checker
- Disable CSS
Site pages used for compliance verification
- Home
- Contact Us
- Case Studies
- Get a Quote
- Ceva Insights
- Sitemap
- FAQ
- Terms & Conditions
- News
- Content
- Search
- Shipment Tracking
- Careers
Feedback and contact
If you are unable to access content or a service, you can contact the website administrator to be directed to an accessible alternative or to obtain the content in another form.
Recourse
This procedure is to be used in the following case:
You have reported to the website administrator an accessibility issue that prevents you from accessing content or services on the portal, and you have not received a satisfactory response.
- Write a message to the Defender of Rights
- Contact the Defender of Rights 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.