Accessibility statement: Trips and Tickets app

This accessibility statement explains how the Trips and Tickets app complies with the Act on the Provision of Digital Services, and outlines the current accessibility shortcomings. The service was published on 1 March 2020.
This statement was prepared on 30 April 2025. The observations in this accessibility statement are based on an evaluation conducted by a third party to assess whether the app meets the requirements set by law.

How accessible is the service?

This mobile application partially meets the accessibility criteria required by law at levels A and AA (WCAG 2.1 and 2.2). There are some accessibility shortcomings that are described in more detail below.

• Not all headings are programmatically marked. (WCAG 1.3.1)

• Some links are presented as web addresses. (WCAG 2.4.4)

• The application contains some foreign language texts. (WCAG 3.1.2)

Visibility and adaptability

• The service contains some poorly distinguishable texts. (WCAG 1.4.3)

• The 'Search trips and tickets' button is difficult to identify as a button. (WCAG 3.2.4)

• The application cannot be used on a horizontal screen. (WCAG 1.3.4)

• Enlarging the text to 200% causes some information clipping. (WCAG 1.4.4)

• Pages cannot be found in multiple ways. (WCAG 2.4.5)

• The purchased ticket is accompanied by an animation that cannot be stopped or paused. (WCAG 2.2.2)

Usage with screen reader or external keyboard

• The reading and focus order returns to the beginning of the view when editing their information in the settings. (WCAG 1.3.2, 2.4.3)

• The reading and focus orders do not move to the beginning of the opened view. (WCAG 1.3.2, 2.4.3)

Usage with screen readers

• Some buttons are missing text alternatives. (WCAG 1.1.1, 1.3.1, 2.4.4)

• The reading order skips content in some views. (WCAG 1.3.2)

• Route information is read incorrectly by the screen reader. (WCAG 1.3.1)

• Labels are not always associated with the toggle switches. (WCAG 1.3.1)

• Visible selections are not always announced by the screen reader. (WCAG 1.3.1, 4.1.2)

• Changes in visible value or state are not always communicated. (WCAG 4.1.2)

• Suggestions related to input fields are not automatically read aloud by the screen reader. (WCAG 4.1.3)

• The screen reader does not read all content. (WCAG 1.3.2)

• There are a few instances of illogical reading order. (WCAG 1.3.2)

• The screen reader provides incorrect information about the number of assistive devices being added and the visibility of the virtual keyboard. (WCAG 4.1.2)

• Sometimes the text read by the screen reader is hidden under cookie text or the top banner. (WCAG 1.3.2)

Usage with an external keyboard

• Not all functions can be used with an external keyboard. (WCAG 2.1.1)

• The focus and the focusable element sometimes remain behind other content. (WCAG 2.4.11)

• In a few places, the focus order is illogical. (WCAG 2.4.3)

The shortcomings listed here are intended to be corrected by 31.08.2025.