The organisation “Public Transport Administration” is committed to making its mobile applications accessible, in accordance with the law of 28th May 2019 on the accessibility of websites and mobile applications of public sector bodies. This accessibility statement applies to:
What is digital accessibility?
Everyone should be able to easily use and consult the information on a website or an app, in particular people with disabilities and/or using assistive software or specialised equipment (blind, partially sighted or otherwise disabled people).
The content listed below is non-accessible for the following reason(s):
- There are several information-carrying images that have no text alternative, such as the pictogram indicating the number of passengers or the red dot indicating the presence of reservations. As a result, the application does not meet RAAM v1 criterion 1.2.
- There are several elements where the information is only given by its colour, such as the distinction between the departure address (red colour) and the arrival address (black colour) on the reservation screen. This does not comply with RAAM v1 criterion 2.1.
- There are some user interface components that do not have sufficient contrast (at least 3:1), such as the “Next” button on the “Details” page of the reservation process in both versions of the app. This does not comply with RAAM v1 criterion 2.3.
- The functions of some interactive components are not recognised by screen readers; therefore the application does not comply with criterion 5.1 of RAAM v1.
- Some interactive components are not operable with a keyboard (RAAM v1 criterion 5.2), such as the arrow that navigates between the selection of date and time when booking or the selection of the travel reason.
- Some interactive components, such as the button that sets the current position as the start address, initiate a context switch without being explicitly explained, making the application non-compliant with criterion 5.3 of RAAM v1.
- Some pages of the application are not structured by titles in the Android version. (Criterion 7.1 of RAAM v1).
- Some texts, for example on the home screen (such as: “Brought to you by Le gouvernement du Grand-Duché de Luxembourg – Ministère de la Mobilité et des Travaux publics – Administration des transports publics” and “Powered by Via”) are not rendered by screen readers. (Criterion 8.1 of RAAM v1).
- If the user wants to increase the font size to 200%, some content is cut off, with the result that these texts do not comply with criterion 8.2 of RAAM v1. Additionally in the iOS version of the app, it is impossible to increase the font size.
- On the “Favourites” page, the label of the “Name” form field disappears when the user starts entering text. (Non-compliance with RAAM v1 criterion 9.1).
- Multiple form field labels are not correctly linked. (Criterion 9.2 of RAAM v1).
- On the ‘Favourites’ page, some mandatory fields are not labelled as such and mandatory fields that expect a specific input format (e.g. email address or phone number) do not indicate this in advance and do not provide an example of an actual input to help users understand if an incorrect input is made. As a result, the application is not compliant with RAAM v1 criterion 9.10.
- Although keyboard navigation is consistent throughout the application, there are some screens, , such as the “Favourites” page and the “Scheduled Rides” page, where the order of recognition by assistive technologies does not comply with the requirements of criterion 10.2 of RAAM v1. There is also a keyboard trap on the “Set your pickup spot”-page that makes it impossible for users who use the keyboard as a pointing and navigational tool to book a trip. The playback order for assistive technologies is currently under revision and will be adjusted in a future update of the application.
- Selecting an option from a drop-down list can only be done with a complex two-finger gesture and as a result this function cannot be activated by a simple gesture (non-compliance with RAAM v1 criterion 11.10).
The content of the application cannot be displayed regardless of the screen orientation (portrait or landscape) as the application can only be used in portrait mode and therefore the application does not meet criterion 11.9 of RAAM v1.
Preparation of this accessibility statement
This statement was prepared on 5 May 2022. The statements contained in this declaration are accurate and based on an effective conformity assessment of these mobile applications with the requirements defined in RAAM 1 , such as an assessment conducted by a third-party: Access42. The statement was last reviewed on 23/09/2021.
Feedback and contact information
If you notice a lack of accessibility, please send us an email to email@example.com: please describe your problem and the relevant page. We promise to get back to you within 1 month. In order fix the accessibility issue in a long lasting and reasonable way, the online correction of the accessibility problem will be privileged. If this cannot be done, the desired information will be sent to you in an accessible format according to your wishes:
- in written form through a document or via email;
- orally in an interview or over the phone.
In the event of an unsatisfactory response, you have the option of informing the Information and Press Service, which is in charge of the verification of accessibility, via its online contact form, as well as the Ombudsman, mediator of the Grand Duchy of Luxembourg.
This statement is based on the document template defined in the implementing decision (EU) 2018/1523. This template is © European Union, 1998-2020 and is available under the following license: Creative Commons Attribution 4.0 International license.