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).
These mobile applications are not compliant with the European Standard EN 301 549 and RAAM version 1 . The reasons for this non-compliance are listed below.
The content listed below is non-accessible for the following reason(s):
- Some decorative graphic elements, such as the images in the tutorial, are not ignored by assistive technologies, so that criterion 1.1 of RAAM v1 is not met.
- Several informative images, such as the “Mobilitéitszentral” logo, have no textual alternative (criterion 1.2 of RAAM v1).
- Several colours have insufficient contrast between text and background colours (criterion 2.2 of RAAM v1). To meet this criterion, the Public Transport Administration commits to increase the contrast ratio between text and background colour to at least 4.5:1 for texts, as required by RAAM v1.
- Several interface components and graphic elements containing information are not sufficiently contrasted and do not meet criterion 2.3 of RAAM v1.
- The application does not meet criterion 5.1 of RAAM v1, which requires each interface component to be compatible with assistive technologies. Some interactive components are not accessible with a screen reader and others cannot be enabled while using a screen reader.
- Not all interface components are usable via keyboard or other assistive technologies (voice navigation, touch control, external keyboard) and therefore the app does not meet the requirements of criterion 5.2 of RAAM v1.
- Some pages of the app are not structured by headings (e.g. the tutorial page or the privacy page) (criterion 7.1 of RAAM v1).
- Visible content carrying important information is not always accessible to assistive technologies, and the actual order of the content is not always maintained when using a screen reader (criterion 8.1 of RAAM v1).
- The Apple iOS-Version of the app does not meet criterion 8.2 of RAAM v1, which demands the possibility of increasing the font size to 200%.
- When the user presses the button to open the menu, the focus of the screen reader is not on the first item (the “Login” Button to access the Login-page) that was just displayed (criterion 10.2 of RAAM v1).
- There are some form fields that do not have visible labels to facilitate input for assistive technology users (criterion 9.1 of RAAM v1).
- Mandatory form fields in the Trip Planner are not labelled as such (Criterion 9.7 of RAAM v1).
- Input assistance for input errors is not accessible because the error message is not visible near the field and is not recognized by assistive technologies that focus on the affected field (criterion 9.9 of RAAM v1).
- The specification of the input-type (suggestions for data types, formats or expected values) is not observed in the account creation form for the field “email address” (criterion 9.10 of RAAM v1). As the email address is personal data, criterion 9.12 of RAAM v1 cannot be validated.
- Several pages of the app have inconsistent keyboard tab commands (criterion 10.1 of RAAM v1).
- The app does not meet criterion 11.9 of RAAM v1 as the app remains locked in portrait mode and cannot be displayed in landscape mode.
The app does not meet criterion 11.9 of RAAM v1 as the app remains locked in portrait mode and cannot be displayed in landscape mode. The application remains alternatively viewable in portrait mode.
Content is outside of the scope of the law of 28 May 2019
The mapped routes do not belong to the elements that are provided in an accessible format. Alternatively, we suggest the text modules in which the routes are described step by step.
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 21/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.