Skip to content
PrivateCorporate customersService points
PassengersParcelsFrequently asked questionsCustomer service
Log in

Accessibility statement: Paketit app

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.

PrivateCorporate customers

Passengers

TimetablesTravel ticketsTrips and Tickets appMost popular routesJourney PlannerKamppiPrices and discountsInstructions and terms of use

Social media