Accessibility statement

Inspector’s report

“The ZOU ! website is partially accessible, with 66.66% of criteria met.”

Non-conformities

• Criterion 1.2: On several pages, certain images <svg> are not ignored by assistive technologies.
• Criterion 1.3: On several pages, at least one alternative is not relevant
• Criterion 3.2: On the ‘Create an account’ page, the colour contrast between the text and its background is insufficient.
• Criterion 3.3: On the “Buy tickets, season tickets and cards – Catalogue_step 1/8” page, the search field <input> has insufficient colour contrast against its background, at a ratio of 1.1:1.
• Criterion 6.1: On several pages:
  • Some links have the same label, such as the three card links on the home page labelled "Discover".
  • Several links that are already self-explanatory have alternative text with the same label.
• Criterion 6.2: On all pages, the image link for the ‘Southern Region’ logo has no label.
• Criterion 7.1: On all pages, several components do not meet the technical requirements for compatibility with assistive technologies.
• Criterion 8.6: On some pages, the web page title is not relevant.
• Criterion 8.9: On several pages, HTML tags are used for a purpose other than that specified in the standards (in relation to the declared document type) to structure the information.
• Criterion 9.1: On several pages, certain text content is not correctly structured using headings.
• Criterion 9.3: On several pages, certain list items that are visually grouped together as a list are not correctly structured.
• Criterion 10.9: On some pages, several icon images conveying information – such as opening a new tab – do not have alternative text.
• Criterion 11.2: On several pages, some labels are not relevant.
• Criterion 11.5: On some pages, fields of the same type are not grouped together.
• Criterion 11.13: On several pages, certain form fields whose purpose relates to user infomation do not have autocomplete functionality.
• Criterion 12.1: On all pages, the website does not have the two expected navigation systems.
• Criterion 12.2: On the ‘Create an account’ page, the menu and navigation bars are missing.
• Criterion 12.6: On some pages, the main navigation area lacks a targeting element such as a landmark or a quick access link.

Technologies used to develop ZOU !

• HTML5 ;
• CSS ;
• JavaScript.

• NVDA
• Color Contrast Analyser
• Chrome
• Firefox
• Arc Toolkit
• Stylus
• Web developer

“The audit carried out on the ‘Allez ZOU !’ app shows that measures relating to digital accessibility need to be implemented; several key issues need to be addressed to ensure an inclusive experience for all users.

Certain non-conformities may hinder or even prevent access to information or certain features. These barriers relate in particular to issues of comprehension, visibility or navigation.

Corrections are therefore necessary to ensure equitable accessibility, particularly for people who are blind, visually impaired, have cognitive impairments or use only the keyboard to navigate."

Non-conformities

• Criterion 1.1: Screens 07 and 08: At least one decorative graphic element is read out by the screen reader.
• Criterion 1.2: Screens 14 and 15: In the results, some icons are not read out.
• Criterion 1.3: Screens 07, 08 and 20: The Zou and Région Sud logos are read aloud as “Zoo logo”.
• Criterion 2.2:
  • Screens 07, 08 and 16: Some text lacks sufficient contrast against the background.
  • Screens 13, 14 and 15: Several transport lines have insufficient contrast. This does not invalidate the criterion under accessibility rules, as these elements are considered logos and are therefore exempt.
• Criterion 5.1:
  • Screen 01: The labels for the ‘home’ and ‘work’ buttons are not relevant or sufficiently self-explanatory.
  • Screen 01: The button opening the actions menu for the journey(s) has no label.
  • Screen 02: When the tab is selected, the new ‘Selected’ state is not announced. Screen reader output: "Headings, Tab 2 of 4"
  • Screen 08: On the verification screen, the ‘I haven’t received the code’ component lacks interactive semantics.
  • Screen 08: On the verification screen, when entering the numeric-only code, the standard keyboard is displayed.
• Criterion 5.2:
  • On most screens: Components at the bottom of the screen that are not displayed cannot be accessed using the keyboard.
  • Screens 07, 08 and 20: It is not possible to navigate using the keyboard; only the back buton can be accessed/activated.
  • Screen 14: The filters cannot be accessed via the keyboard.
  • Screen 14: During testing with VoiceOver and an external keyboard, interface components are not read out correctly. Screen reader output: “Loading complete”.
• Criterion 5.3: Screen 13: When the departure and arrival points are selected, the search starts automatically and the user is taken directly to the search results.
• Criterion 5.4: Screen 16: When it appears, the error message regarding the total number of passengers is not read out by the screen reader
• Criterion 7.1:
  • Screen 07: Inappropriate use of headings.
  • On most screens: Headings are missing.
• Criterion 7.2:
  • Screen 06: Results presented as a list are not rendered as a list.
  • Screen 07: The list of password rules is not rendered as such.
  • Screen 18: In the ‘Withdrawal method’ modal, the three withdrawal methods appear visually as a list but are not rendered as a list.
• Criterion 8.1: Screen 15: In the journey details, certain stages are not displayed correctly. The user cannot understand which mode of transport to take.
• Criterion 8.2:
  • Screen 02: The screen title is truncated in both portrait and landscape modes.
  • Screen 07: Increasing the font size to 200% is ineffective. It is only possible to zoom using finger gestures such as pinching and spreading. (These gestures are complex and make it difficult for people with disabilities to view the content).
• Criterion 9.8: Screen 10: The "Telephone number" field does not use the expected format.
• Criterion 9.9: Screen 10: When a field contains an error, the error message is not displayed when focus is placed on the field.
• Criterion 9.10: Screen 10: For the incident date and time field, the error message does not include a concrete example of what should be entered.
• Criterion 9.12: Screen 10: Some fields collect data that can be filled in automatically, but they do not have the ‘autocomplete’ attribute.
• Criterion 10.2: Screen 15: In the "Saved Journey" modal, when the screen reader has focus, the journey preview is not rendered correctly.
• Criterion 11.10: Screen 6: On the station screen, the transport mode tabs can only be accessed via complex gestures (horizontal swipe).

Flutter.

• Colour Contrast Analyser ;
• External keyboard.

4) Remedies

This procedure should be used in the following situation: you have reported an accessibility issue to the website or mobile app manager that is preventing you from accessing content or a service, and you have not received a satisfactory response.

• Write to the Defender of Rights
• Contact the Defender of Rights’ regional representative
• Send a letter by post (free of charge, no stamp required):
  Défenseur des droits 
  Libre réponse 71120 
  75342 Paris CEDEX 07