Accessibility Statement

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 card service

The following parts or functions of the service are not fully accessible to some user groups:

• Use and filtering of the purchase and use history
• Some calendar information cannot be interpreted by screen readers (General accessibility).

City bike service

The new compliant service was launched in spring 2021. The service was designed and planned in accordance with the latest accessibility guidelines. An accessibility audit will be conducted at the beginning of June 2021 and any accessibility issues will be reported on this page.

HSL Mobile App Accessibility Statement

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) 

• In the address input field, a suggested address cannot be selected with the keyboard, because the suggestions are not focusable. (WCAG 2.1.1) 

• The component type for address suggestions is not specified. (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) 

• Tabs are lacking the information of their selected status for screen readers. (WCAG 1.3.1, 4.1.2) 

Tickets 

• In the ticket section, using tab controls is not possible with the keyboard.(WCAG 2.1.1) 

• Penalty fare terms cannot be accepted using the keyboard. (WCAG 2.1.1) 

• Adding a payment method is not possible using the keyboard, because the add buttons are not focusable. (WCAG 2.1.1) 

• Confirming payment is difficult with the keyboard, because the “Confirm payment” button is not focusable. Payment must be confirmed by pressing the space key when the confirmation dialog appears. (WCAG 2.1.1) 

• 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) 

• When navigating to the “Buy a single ticket” view, the focus is automatically moved in the middle of the content. (WCAG 2.4.3) 

Route planner 

• When filtering by modes of transportation, the text alternatives for the icons duplicate the name of the transport. (WCAG 1.1.1) 

• After filling out the route search information, the search is performed automatically. A status message is presented to assistive technologies, but it is cut off when the focus is simultaneously moved to the back button. (WCAG 4.1.3) 

• 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) 

• In the route details view, the accessible names for buttons are not understandable for assistive technology users when the selected language is other than English, because the names are always provided only in English. (WCAG 1.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 heading structure is not always consistent in all views, and headings are not always marked programmatically. (WCAG 1.3.1) 

• Some of the content within the app does not respond to system-level text resizing features, for example in the bottom navigation bar (WCAG 1.4.4) 

• The back button in single article views cannot be accessed using an external keyboard. (WCAG 2.1.1)  

• Links within articles cannot always be selected using external keyboards or assistive technology, and are not announced as links by screen readers. (WCAG 2.1.1, 4.1.2) 

• Some tabs are lacking the information of their selected status for screen readers. (WCAG 1.3.1, 4.1.2) 

• 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) 

• In My information view, the Save button is not marked as a button programmatically. (WCAG 1.3.1) 

Tickets 

• When entering contact information and changing the phone number country code, the focus is moved unexpectedly to the top of the view, to the back button when using a screen reader and to the login link when using the keyboard. (WCAG 2.4.3, 1.3.2) 

• After saving the contact information, the status and change of the view are not communicated clearly to assistive technology users. (WCAG 4.1.3, 1.3.1) 

• When selecting the travel zone with the keyboard, the zone buttons have many focusable elements, and only some of them are functional. (WCAG 2.4.3) 

• Selecting ticket validity time or departure/arrival time in route planner is not possible with the keyboard. (WCAG 2.1.1) 

• The confirm payment modal is not focused when it appears, and the focus is not constrained within the dialog. (WCAG 2.4.3) 

• 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) 

Route planner 

• Real time tracking and travel zone information cannot be accessed using a screen reader. (WCAG 1.3.1) 

• In the route planner view, the size of the search panel over the map cannot be adjusted with the keyboard. (WCAG 2.1.1) 

• Location input field can be used only once with the keyboard. When focusing another component, the text field cannot be focused again. (WCAG 2.1.1) 
• The component type for address suggestions is not specified. (WCAG 4.1.2) 

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

saavutettavuus@traficom.fi
telephone switchboard +358 29 534 5000