Accessibility of Matkahuolto’s digital services

This accessibility statement describes how the Matkahuolto website, matkahuolto.fi, complies with the Act on the Provision of Digital Services and outlines the accessibility shortcomings of the service. The service was published on 12 November 2019. This statement was prepared on 4 February 2025.

The observations in this accessibility statement are based on a joint evaluation by Matkahuolto and the accessibility expert of the website’s technical supplier. The accessibility of the site was assessed by an expert in December 2023. Identified issues were addressed at the end of 2024 and in January 2025.

How accessible is the service?

This website partially meets the accessibility requirements at levels A and AA, as defined in the Web Content Accessibility Guidelines (WCAG) 2.1. The service contains some accessibility deficiencies, which are described in more detail below.

Detailed information on technical accessibility

The website is not yet fully accessible in all respects.

Content or functionalities that are not yet accessible

Content

• When a user interface component has a label containing text or an image of text, the name of the component should include the visually presented text.

  • On the Additional Services page, the textual label does not match the button text. (WCAG 2.5.3)

• Non-text content presented to the user should have a text alternative that serves the equivalent purpose.

  • On the Additional Services page, the textual label is inconsistent with the button label. (WCAG 1.1.1)

• Color should not be used as the only visual means of conveying information.

  • The privacy policy link does not stand out clearly from the surrounding text. (WCAG 1.4.1)

Perceivability and adaptability

• The contrast between text and background is insufficient in some places.

  • Button labels (“Search timetables”, “Send a parcel”), headings, and ticket prices on the selected route. (WCAG 1.4.3)

• Content presented on hover or focus is missing.

  • The parcel purchase page lacks a textual explanation. (WCAG 1.4.13)

• The focus indicator is not clearly distinguishable from buttons.

  • The homepage banner button and the "Buy" button in the ticket shop. (WCAG 2.4.11)

Use with a screen reader or external keyboard

Use with a screen reader

• Information, structure, and relationships should be conveyed programmatically.

  • After using the “Skip to content” feature, the screen reader incorrectly identifies an empty group, but navigation remains possible. (WCAG 1.3.1)

  • The screen reader misreads the “Log in” link and menu headings for logged-in users. (WCAG 1.3.1)

  • The screen reader does not recognize the “Change direction” button. (WCAG 1.3.1)

• Elements are misread or components are not recognized.

  • “Banner” is unnecessarily announced in the mobile version near the “Log in” section. (WCAG 1.3.1)

  • Buttons are not programmatically recognized or are missing labels. (WCAG 4.1.2)

Use with an external keyboard

• All functionality should be operable via a keyboard interface without timing-dependent keystrokes.

  • The “Skip to content” function skips the service point search on the confirmation page. (WCAG 2.1.1)

  • The “Add to calendar” element in the ticket shop is not reachable using the Tab key. (WCAG 2.1.1)

• The tab focus is not clearly visible.

  • The “Continue” button focus in the ticket shop is not distinguishable. (WCAG 1.4.13)

• The name and role of user interface components are not always programmatically determinable.

  • The “When do we deliver” page lacks a toggle switch. (WCAG 4.1.2)

These issues are scheduled to be fixed by 31 October 2025.

This accessibility statement explains how the Paketit app complies with the Act on the Provision of Digital Services, and outlines the current accessibility shortcomings. The service was published on 15 November 2021.
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. 

Detailed information on technical accessibility

The mobile application is not yet fully accessible in all respects.

Content or functions that are not yet accessible: 

Content 

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

• The screen reader does not recognize all links. (WCAG 1.3.1, 4.1.2) 

• Many links are marked as buttons. (WCAG 4.1.2) 

• The Swedish and English versions of the application have incomplete language labels. (WCAG 3.1.1) 

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

• Unselected toggle switches are poorly distinguishable. (WCAG 1.4.11) 

• Enlarging the text to 200% causes slight overlap and information clipping. (WCAG 1.4.4) 

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

Forms 

• The label is not always associated with the input field, check box or toggle switch. (WCAG 1.3.1) 

• Instructions are often presented only after the input field or toggle switch. (WCAG 1.3.1, 3.3.2) 

• Mandatory fields are not programmatically marked. Only some are marked visually. (WCAG 3.3.2) 

• Error and status messages are not automatically read by screen readers. (WCAG 3.3.1, 4.1.3) 

• The input purpose is not identified in input fields collecting information about the user. (WCAG 1.3.5)  

• The phone number is requested in several places and is not offered as a pre-filled option. (WCAG 3.3.7) 

Usage with screen reader or external keyboard 

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

• Focus and reading are limited to the visible view. A user using an external keyboard must scroll the screen with the arrow keys. (WCAG 1.3.2, 2.4.3)  

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

Usage with screen readers 

• The status of toggle switches is not communicated automatically when the state changes. (WCAG 4.1.2)  

• The selected option for home delivery method and time is not communicated. (WCAG 4.1.2)  

• The application has some buttons and icons whose meaning is not recognized by the screen reader. (WCAG 1.1.1, 4.1.2)  

• The Matkahuolto logo does not have a text alternative. (WCAG 1.1.1)  

• It is difficult to close the virtual keyboard. The user must activate an area outside the keyboard to close it. (WCAG 2.1.2) 

• The screen reader reads some items misleadingly or one word at a time. (WCAG 1.3.1) 

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

• In a few places, the reading order is illogical. (WCAG 1.3.2) 

Usage with an external keyboard 

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

• Redundant elements are linked to the focus order in a few places. (WCAG 2.4.3) 

The shortcomings listed here are intended to be corrected by October 31, 2025. 

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. 

The Matkahuolto Journey Planner service is operated by Digitransit. You can read the service’s accessibility statement here.