Accessibility

This page outlines our digital accessibility policy and lays out how this website complies with current regulations and standards.

What is digital accessibility?

Digital accessibility refers to the rules and best practices that span all functional, visual, technical and editorial aspects. Complying with these rules and best practices ensures digital media (websites, mobile applications, PDF documents, etc.) remain accessible to users with disabilities..

An accessible site allows that following:

Customising display via operating system and/or browser (increasing or decreasing font sizes, changing fonts, changing colours, disabling animated features, etc.).
Browsing via assistive technologies such as screen readers and braille display.
Navigating without a mouse (using just a keyboard, switches, or a touch screen).
Watching and listening to video and audio content using subtitles and/or transcripts.
And more.

Digital accessibility policy

Kelio is committed to making its websites (internet, intranet and extranet), mobile apps, software and digital urban equipment disability accessible in line with Article 47 of French Law No. 2005-102 dated 11 February 2005 .

To do so, it is implementing the following strategy and action points:

A multi-year accessibility roadmap for 2025-2027.

Declaration of non-compliance with the RGAA

This declaration applies to the www.kelio.com website.

Compliance check

This website is not compliant with the RGAA (France’s Accessibility Improvement Framework) - version 4.1.2 due to the non-compliance factors given below.

Testing outcomes

The RGAA compliance audit (version 4.1.2) conducted in February and March 2026 by Ideance demonstrated that out of the following sample:

The overall compliance rate was 28.8%. This rate was calculated by dividing the number of compliant criteria by the number of applicable criteria.
The average compliance rate is 49.5%. This rate was calculated by averaging out compliance rates for each page.

Non-accessible content

Non-compliance

List of non-compliant criteria:

1.1 - Some information-containing images do not have alternative text.
1.2 - Some decorative images are not ignored by assistive technologies.
1.3 - Text alternatives for informative images are not relevant.
1.9 - Some captions are not linked to the right images.
2.2 - Some iframe titles are not relevant.
3.1 - Some information is conveyed exclusively via colour.
3.2 - In some cases, there is insufficient contrast between text colours and backgrounds.
3.3 - In some cases, there is insufficient contrast between interface component colours/information-containing graphic elements and backgrounds.
4.1 - Some videos do not have text transcripts or audio descriptions.
4.3 - Some videos are not subtitled.
4.4 - Some video subtitles are not relevant.
4.5 - Some videos do not have audio description
4.7 - Some videos are not clearly identifiable.
5.1 - Some complex data tables do not have summaries.
5.2 - Some complex data tables summaries are not relevant.
6.1 - Some links are not explicit.
7.1 - Some scripts are not compatible with assistive technologies.
7.3 - Some scripts cannot be controlled using a keyboard or pointing device.
7.4 - Context changes triggered by scripts are not indicated or controllable.
8.6 - Some page titles are not relevant.
8.7 - Some language changes are not indicated.
8.9 - Some tags are used exclusively for display purposes.
9.1 - Some information is not structured using appropriate headings.
9.2 - Page structure is not consistent.
9.3 - Some lists are not structured correctly.
9.4 - Some quotes are not flagged correctly.
10.1 - Some style sheets are not used to control display.
10.5 - Some CSS styles for background and font colours are not used correctly.
10.6 - Some links whose purpose is not clear cannot be visually distinguished from the surrounding text.
10.7 - Focus on interactive elements is not visually apparent.
10.8 - Some hidden content cannot be ignored by assistive technologies.
10.9 - Some information is conveyed exclusively via shape, size or position.
10.10 - Some information is conveyed exclusively via shape, size or position in a non-relevant manner.
10.11 - Some content cannot be displayed without horizontal scrolling on a window 320 px wide.
10.13 - Some additional content that becomes visible upon focusing on or hovering over an interface component is not controllable.
10.14 - Some additional content that appears exclusively via CSS styles cannot be made visible using the keyboard or a pointing device.
11.1 - Some form fields are unlabelled.
11.4 - Some labels and their form fields are not properly linked.
11.5 - Some fields of the same type are not grouped.
11.10 - Some input controls are not used correctly.
11.13 - The purpose of input fields cannot be inferred in order to automatically fill them with user data.
12.1 - The website does not have at least two different navigation systems.
12.6 - Some content grouping regions on several pages (header, main navigation, main content, footer and search engine) cannot be reached or bypassed.
12.7 - There is no link to bypass or quickly access the main content area..
12.8 - Tab order is not consistent.
12.9 - Navigation contains keyboard traps.
13.7 - In some cases, sudden changes in brightness/flashing effects are not used appropriately.
13.8 - Some moving/flashing content cannot be controlled.
13.10 - Some features that can be used/accessed via complex manoeuvres are not available through simple manoeuvres.

Additional notes

Validity of the generated source code

The source code generated by the website’s pages isn’t fully valid depending on the specified document type.

However, for the reasons given below, RGAA criterion 8.2 related to this point has been given as compliant.

Officially, the WCAG criterion 4.1.1 (linked to said RGAA criterion 8.2) has been removed from WCAG 2.2, and must be considered as being satisfied under the terms of WCAG 2.1 in addition to European standard EN 301 549.

In practice, this criterion no longer benefits accessibility for users with disabilities. Any potential accessibility issues that may arise from the generated source code being invalid are covered by other aspects of the RGAA.

Third-party elements not audited

Cookie manager

The ‘Didomi’ third-party cookie manager was not fully audited in depth. Checks were, however, run to ensure that its presence does not impact on using or checking the rest of the website.

Video player

The ‘Youtube’ video player was not fully audited in depth. Checks were, however, run to ensure that it can be used with various assistive technologies.

Declaration log

This declaration was logged on 5 March 2026.

Technologies used to create the website

HTML5.
ARIA.
CSS.
JavaScript.

Test environment

Testing was conducted using the following web browser and screen reader combinations:

Firefox 147 and NVDA 2025.3.2 in Windows 11.
Firefox 147 and JAWS 2025 in Windows 11.
Safari and VoiceOver in macOS 26.2.
Safari and VoiceOver in iOS 26.2. Tools used to assess accessibility
Colour Contrast Analyser.
Contrast Finder.
Firefox development tools.
Web Developer (Firefox extension).

Website pages that were used to check compliance

Improvement policy

In March 2026, an audit for RGAA (version 4.1.2) compliance was carried out by Ideance, and resulted in an overall compliance rate of 28.8%.

Based on these findings, we undertake to:

Correct any non-compliant elements identified on the audited pages, with priority given to semantic structure, keyboard navigation and interactive components;
Build accessibility requirements into the design for all new features and content;
Provide contributing teams with training in best editorial practices: text alternatives, link labels and heading hierarchy.

Feedback and contact

If you cannot access content or a service on this website, get in touch using one of the methods below with a description of the issue:

Send us a message using our contact form.
Write to us at webmaster@bodet.com.
Call us on +33(0)2 41 71 44 00.
Send a letter to Boulevard du Cormier – BP 40211 – 49302 CHOLET Cedex France

We promise to get back to you within a month.

Means of appeal

If you’ve been using our website and have spotted one or several cases of non-compliance with digital accessibility regulations (accessibility issues, lack of mandatory declarations, etc.),
and if you’ve been in touch about it
and aren’t happy with our response,

you can:

Contact Arcom

To flag one or more cases of non-compliance with digital accessibility regulations, head to the ‘Report a digital accessibility issue’ page on Arcom’s website.

Contact the French ‘Defender of Rights’

To assert your rights surrounding any accessibility obstacles you might have encountered:

Either contact the delegate for your region via the French ‘Defender of Rights’ directory of delegates.
Or fill in the French ‘Defender of Rights’ complaints form, taking care to select ‘I have experienced discrimination’ followed by ‘Private services and goods’ and ‘Disability’.
Or send a letter (free of charge within France, no stamp required) to the following address:
Défenseur des droits - Libre réponse 71120 75342 Paris CEDEX 07