Accessibility Statement: IDFM Carpooling Lines

Published on

Île-de-France Mobilités undertakes to make this online service accessible in accordance with Article 47 of Law No. 2005-102 of 11 February 2005. This accessibility statement applies to this mobile application: IDFM Carpooling Lines (IDFM Carpooling Lines – Apps on Google Play and https://apps.apple.com/fr/app/lignes-de-covoiturage-idfm/id6741570430).

In addition, and in accordance with Decree No. 2019-768 of 24 July 2019, Île-de-France Mobilités details the strategy for making its digital services accessible in the following documents:

Compliance status

The IDFM carpooling line mobile application does not comply with the general accessibility improvement framework (RAAM version 1.1). This accessibility statement is dated 24/04/2026.

Test results

The compliance audit carried out reveals that:

  • on the iOS version: 19.05% of the criteria of RAAM 1.1 are met;
  • on the Android version: 25.00% of the RAAM 1.1 criteria are met.

Non-accessible content

Non-conformities

  1. Criterion 1.1 — Decorative graphic elements ignored by TAs (Platforms: iOS and Android — Level: A)
    Fill asterisks and field dividers (E20), white space read by TalkBack (E02).
  2. Criterion 1.2 — Accessible alternatives to information-carrying graphic elements (Platforms: iOS and Android — Level: A)
    Interactive map markers (E03), "+" buttons for adding a photo (E07), +/- quantity buttons (E10), card icons (E11), address reversal control (E14), route buttons and icons (E15), password "eye" icon (E02 Android), Burger Menu icon and Driver/Passenger toggle (E03 Android).
  3. Criterion 1.3 — Appropriateness of Accessible Alternatives to Graphic Elements (Platforms: iOS and Android — Level: A)
    Titles that are too generic ("Benchmark on the map" on E03), "+" and "+/-" buttons that are not explicit (E07, E10), uninformative labels on the cards (E11), Pass Navigo and passenger icons (E15, E16), telephone code (E02), Driver/Passenger toggle (E03).
  4. Criterion 1.9 — Correct reproduction of captioned graphic elements (Platforms: iOS — Level: AA)
    The "+33" area code associated with the flag, static non-interactive, should be merged with the telephone field (E02).
  5. Criterion 2.2 — Sufficient contrast between the text and its background (Platforms: iOS and Android — Level: AA)
    Grey text in time badges (E03), column headings of the table "DATE / DEPARTURE / EARNINGS" (E04), label "Payment method" (E05), "Driver code" (E07), "Add a vehicle" (E09, E10).
  6. Criterion 2.3 — Sufficient contrast of interface components and graphical elements (Platforms: iOS and Android — Level: AA)
    Green/blue badges located on the right on the driver's trip screen (E15).
  7. Criterion 5.1 — Compatibility of Interface Components with Assistive Technologies (Platforms: iOS and Android — Level: A)
    Buttons and fields that do not render their role (E01, E02), Bottom Sheet component that traps focus (E03), voiced text without an interactive role (E04, E05, E07).
  8. Criterion 5.2 — Keyboard and Pointing Device Controllable Components (Platforms: iOS and Android — Level: A)
    Button show/hide password inaccessible to TAs (E02), touch areas less than 48 dp (E05, E07, E08, E11), invisible selection focus (E02 Android).
  9. Criterion 5.3 — Notification of context changes (Platforms: iOS and Android — Level: A)
    Accordion sections without status change announcement (E08), bottom sheet opening silently (E13, E18, E19).
  10. Criterion 5.4 — Restitution of status messages by TAs (Platforms: iOS and Android — Level: AA)
    Form error messages not automatically announced (E02, E10), success notifications not voiced (E08), setup confirmation not reported (E09), driver/passenger mode change not explicit (E03, E11).
  11. Criterion 5.5 — Sensitivity of the states of a toggle control (Platforms: iOS and Android — Level: A)
    Status of the button show/hide password not perceptible (E02, E22), no announcement on the Driver/Passenger toggle (E03, E11), activation/deactivation of route stages not explicit (E15).
  12. Criterion 6.1 — Reproduction of texts in the main language of the screen (Platforms: iOS and Android — Level: A)
    VoiceOver switching to English voice on the toggle (E14), use of the word "Driver" on the Driver/Passenger toggle (E03, E14), term "Bottom Sheet" vocalized as is (E03).
  13. Criterion 6.2 — Interface elements not used solely for presentation purposes (Platforms: iOS and Android — Level: A)
    Buttons announced without a "button" role (E01, E02), tickets and labels declared as plain text (E02), missing labels on passenger icon buttons (E15, E16).
  14. Criterion 7.1 — Structuring of information through the use of tickets (Platforms: iOS — Level: A)
    No ticket detected by the Rotor on the login screen (E02) — structuring elements are declared as StaticText instead of heading.
  15. Criterion 8.1 — Accessibility to AT of visible content that carries information (Platforms: iOS and Android — Level: A)
    Empty focusable elements corresponding to hidden error areas (E02), partially non-vocalizable bottom panel (E03), date read without semantic context (E04), invisible elements receiving focus (E08), non-explicit toggle (E11), € symbols not pronounced (E12), geolocation icon ignored (E03 Android).
  16. Criterion 8.2 — Increase in font size by up to 200% (Platforms: iOS and Android — Level: AA)
    Components that do not fit text zoom (E01, E02, E03, E04, E07, E08, E10, E11)—truncated or inaccessible content.
  17. Criterion 8.3 — Sufficient Contrast of Components in a Text Environment (Platforms: iOS and Android — Level: A)
    Colors used for "Open" status that are difficult to distinguish (E18).
  18. Criterion 8.5 — Focus Visibility (Platforms: iOS — Level: A)
    Keyboard focus indicator not visible on the "Transfer" and "Credit my fundraiser" buttons (E04), "Validate this amount" button (E05).
  19. Criterion 8.6 — Information not based solely on shape, size or position (Platforms: iOS and Android — Level: A)
    Edit "pencil" icons and navigation cells without a "Button" role (E08).
  20. Criterion 9.2 — Label available to TAs for each form field (Platforms: iOS and Android — Level: A)
    Phone field generating a hidden element (E02), field values not rendered (E08), input fields advertised as plain text (E10), labels not associated with fields (E14, E18, E20), placeholder "DD/MM/YYYY" read letter by letter (E22 Android).
  21. Criterion 9.3 — Appropriateness of Field Labels (Platforms: iOS — Level: A)
    "Close" label too generic (E14), selected value read without units (E18).
  22. Criterion 9.4 — Conjoined Field Label and Associated Field (Platforms: iOS — Level: A)
    Phone and password fields that do not form a consistent set (E02).
  23. Criterion 9.5 — Appropriateness of Form Button Titles (Platforms: iOS — Level: A)
    Edit buttons without explicit title (E08).
  24. Criterion 9.6 — Identification of fields of the same nature (Platforms: iOS — Level: A)
    Error messages not related to the affected fields (E02).
  25. Criterion 9.7 — Correct identification of required fields (Platforms: iOS and Android — Level: A)
    Compulsory nature not restored by the TAs (E02, E10, E20, E22).
  26. Criterion 9.8 — Availability of the expected data type and/or format (Platforms: iOS and Android — Level: A)
    Type/format not provided for the registration form fields (E22).
  27. Criterion 9.9 — Accessibility of Input Errors (Platforms: iOS and Android — Level: A)
    Non-vocalized and non-field-related errors (E08, E10, E20, E21, E22).
  28. Criterion 9.10 — Suggested Expected Types, Formats or Values (Platforms: iOS and Android — Level: AA)
    Status announcement missing when opening the DatePicker (E08), no suggestions on vehicle size (E10), password requirements not associated with the field (E22).
  29. Criterion 10.2 — Consistency of the order of restitution by the TAs (Platforms: iOS and Android — Level: A)
    Native VoiceOver backtracking gesture inoperative (E02), non-logical scan order (E03), poorly organized focus on the Account screen (E07), focus not moved when opening accordions (E08), heterogeneous vehicle card labeling (E09), focus trapped by hidden error messages (E10), duplicate focus on the address (E17), erratic focus in the minute selector (E18).
  30. Criterion 10.3 — Absence of Focus Trap (Platforms: Android — Level: A)
    Components below the bottom sheet taken into account by TalkBack (E13 Android).
  31. Criterion 11.1 — Control of Time Limits Modifying Content (Platforms: iOS and Android — Level: A)
    Bottom sheet opens silently, focus remains on the main screen (E19).
  32. Criterion 11.2 — Ability to stop or remove a session time limit (Platforms: iOS and Android — Level: A)
    Automatic bottom sheet without user control (E19).

Content not subject to the accessibility obligation

None

Test environment

Content rendering checks were performed based on the combination provided by the RAAM 1.1 baseline, with the following versions:

  • iPhone - iOS (latest stable version) with VoiceOver (latest stable version)
  • Android Smartphone - Android (latest stable version) with TalkBack (latest stable version)

Technologies used for the realization

  • React Native
  • JavaScript / TypeScript

Tools used in the evaluation

  • Accessibility Inspector (iOS)
  • Accessibility Scanner (Android)
  • Color Contrast Analyser
  • System accessibility settings (text size, contrast, inversion, etc.)
  • VoiceOver (iOS) and TalkBack (Android) screen readers

Pages of the site that have been verified for compliance

The audit covered a sample of 22 screens representative of the main user journeys (login, consultation of the kitty, creation and management of trips, profile, registration forms). The same screens were evaluated on iOS and Android.

  1. E01 — Welcome Screen
  2. E02 — Login Screen
  3. E03 — Home page
  4. E04 — My Fundraiser
  5. E05 — Crediting my fundraiser
  6. E06 — Transferring My Pot
  7. E07 — Account
  8. E08 — Personal Information
  9. E09 — Trip Parameters
  10. E10 — Add a Vehicle
  11. E11 — My Journeys
  12. E12 — Detail of the route
  13. E13 — Bottom sheet Help
  14. E14 — "Where are you going?" screen
  15. E15 — Your Driver's Journey
  16. E16 — Your Passenger Journey
  17. E17 — Current journey (driver)
  18. E18 — "When will you arrive at the stop?" (passenger)
  19. E19 — Meeting at the stop (passenger)
  20. E20 — Identify the driver
  21. E21 — Registration Form
  22. E22 — Information form

Feedback and contact

If you are unable to access any content or service, you may contact the person responsible for the website to be directed to an accessible alternative or to obtain the content in another form.

Contact Île-de-France Mobilités' digital accessibility referent

Remedies

This procedure is to be used in the following case: you have reported to the person responsible for the website a lack of accessibility that prevents you from accessing any of the content or services of the portal and you have not received a satisfactory response.