Accessibility Statement

This accessibility statement applies to the digital services of Helsinki Region Transport (HSL), including hsl.fi, HSL Journey Planner and HSL app. This statement was prepared on 27 October 2020 and updated on 17 Aprilr 2026. The accessibility of the services has been evaluated by an external expert organization, which helps us to continuously improve service accessibility.

Accessibility of services

HSL.fi

HSL.fi Compliance Status

HSL.fi is partly compliant with the accessibility requirements.

Non-accessible content

The content below is not accessible in accordance with WCAG criteria for the following reasons:

General website content

Video content does not have subtitling and/or audio description. WCAG 1.2.1, 1.2.2
There are flaws in alternative texts of visual elements, and they are hidden from users of screen readers. WCAG 1.1.1.

HSL Mobile App

HSL Mobile App Accessibility Statement, April 2026

The HSL mobile app is partly compliant with the accessibility requirements. Fixing the accessibility issues is in progress.

Non-accessible content

The content listed below is not compliant with the regulations.

iPhone application

General

The application does not adapt to device orientation. This can be enabled in the settings, but it is not on by default. (WCAG 1.3.4)
Some of the content within the app does not respond to system-level text resizing features, for example in the bottom navigation bar, news, disruptions, accessibility statement, and terms of service. (WCAG 1.4.4)
When using the app in Finnish or Swedish, the component type and state is announced in English in some components. (WCAG 4.1.2)
The content and links in a news article cannot be accessed when using a screen reader without touching the content first. (WCAG 2.4.3)

Tickets

The keyboard focus indicator is not clearly perceivable in blue action buttons. (WCAG 2.4.7)
When expanding an expanding section, screen reader focus is moved to the expand button after a short timeout. (WCAG 2.4.3, 1.3.2)

Journey planner

When filtering by modes of transportation, the text alternatives for the icons duplicate the name of the transport. (WCAG 1.1.1)
When opening the detailed view of a route, the functionalities are not initially focusable for a keyboard user. They will become focusable after scrolling the view. (WCAG 2.1.1)
Real time tracking and travel zone information cannot be accessed using a screen reader. (WCAG 1.3.1)

Android application

General

View headings have not been marked as headings (WCAG 1.3.1)
The back button in single article views cannot be accessed using an external keyboard. (WCAG 2.1.1)
The application does not adapt to device orientation. This can be enabled in the settings, but it is not on by default. (WCAG 1.3.4)
Some views cannot be closed with the keyboard, because the buttons in the top bar (Close, Done, etc.) are not focusable. (WCAG 2.1.1)
Most text input fields cannot be used with the keyboard, because they are not focusable. (WCAG 2.1.1)

Tickets

Selecting ticket validity time or departure/arrival time in journey planner is not possible with the keyboard. (WCAG 2.1.1)
When opening the ticket validity area dialog, the focus is not constrained withing the dialog, and after closing the dialog, the focus is not placed to the button which opened the dialog. (WCAG 2.4.3)

Journey planner

Real time tracking and travel zone information cannot be accessed using a screen reader. (WCAG 1.3.1)
In the journey planner view, the size of the search panel over the map cannot be adjusted with the keyboard. (WCAG 2.1.1)

HSL Ticket Store

Updated 7.2.2025

Login

The user may find it difficult to change the page language if they are using a screen reader or keyboard, as the language links reside unexpectedly at the very end of the page. WCAG 2.4.3 Focus Order

The user cannot return to the previous page or navigate away from this page without being able to log in successfully first. Not a WCAG violation.

Screen reader users are not automatically notified if a log-in attempt fails. Instead, they must find any input error messages from the page on their own after clicking the log-in button. WCAG 4.1.3 Status Messages.

The language links fail to describe to screen reader users, which language is currently selected, as the selection is indicated only visually. WCAG 1.3.1 Information and Relationships

Other

The button that displays user information is described to screen readers as an accordion type button, even though it actually opens a modal type dialog. WCAG 1.3.1 Information and Relationships.

Feedback and contact details

We provide telephone support for users for whom our digital services are not fully accessible. Please contact our customer service at +358 (0)9 4766 4000 (mobile call charge or local call rate).

Did you notice an accessibility defect in our services? Let us know, and we’ll do our best to fix it. We will respond to all feedback with contact details within 14 days. We cannot respond to feedback without contact details, but the feedback will still be processed.

Send us your feedback on accessibility with our feedback form.

Filing an accessibility complaint or a request for clarification

If you are dissatisfied with the response you receive, or you do not receive a response within two weeks, you can file a complaint to Traficom. Traficom monitors the implementation of accessibility requirements in Finland.

Contact details:

Finnish Transport and Communications Agency Traficom

Digital Accessibility Supervision Unit

www.webaccessibility.fi

[email protected]
telephone switchboard +358 29 534 5000