Accessibility Statement

Legal Context

The implementation of Article 47 of the French Law of 11 February 2005 on equal rights and opportunities states that all online services provided by the government must be accessible to everyone.

What Is Digital Accessibility?

An accessible website is one that allows people with disabilities to access its content and features without difficulty.

For example, an accessible website enables users to:

- Navigate using a screen reader and/or a braille display (used primarily by blind or visually impaired individuals)

- Customize the display according to their needs (text enlargement, color adjustments, etc.)

- Navigate without a mouse (using only a keyboard, touch screen, voice input, or any other adapted device)

To ensure accessibility, the website must comply with current standards during both development and updates.

Accessibility Statement

RATP Dev is committed to making its websites and mobile applications accessible in accordance with Article 47 of Law No. 2005‑102 of 11 February 2005.

To this end, the company is implementing a strategy and actions described in its multi‑year accessibility plan, currently under preparation.

This accessibility statement applies to the website: RATP DEV

Compliance Status

The “RATP DEV” website is partially compliant with the General Accessibility Improvement Framework (RGAA v4.1).

Test Results

The compliance audit conducted by mc2i on 06/03/2026 indicates that:
60% of RGAA v4.1 criteria (AA level) are met.

Compliance rate by standard level:

Level A: 56.60%

Level AA: 70.59%

Non‑Compliance

Several non‑conformities were identified, some appearing on multiple pages:

Frames

2.2 For each frame with a frame title, is the title relevant?

Colors

3.2 Is the contrast between text and background colors sufficient (except in specific cases)?

3.3 Are the colors used in interface components or graphic elements conveying information sufficiently contrasted?

Mandatory Elements

8.2 Is the generated source code valid according to the document type, except in specific cases?

8.6 For each web page with a page title, is the title relevant?

8.7 Is every language change correctly indicated in the source code?

8.9 Are tags avoided when used for presentation purposes only?

Forms

11.1 Does each form field have a label?

11.10 Is input validation used appropriately?

11.11 Is input validation accompanied, when needed, by suggestions to help users correct errors?

Images

1.1 Does each informative image have a text alternative?

1.2 Are decorative images correctly ignored by assistive technologies?

1.3 Is the text alternative for informative images relevant?

Links

6.1 Is every link explicit?

6.2 Does every link have a label?

Multimedia

4.1 Does each pre‑recorded time‑based media have a transcript or audio description if needed?

4.7 Is each time‑based media clearly identifiable?

4.13 Are all time‑based and non‑time‑based media compatible with assistive technologies?

Navigation

12.6 Can users reach or skip repeated content areas (header, main navigation, main content, footer, search engine)?

Presentation

10.1 Are style sheets used to control the presentation of information?

10.5 Are CSS declarations for background and text colors used correctly?

10.7 For each element receiving focus, is the focus clearly visible?

10.11 Can content be displayed without requiring both vertical scrolling (for a 256px height window) and horizontal scrolling (for a 320px width window)?