Accessibility statement for the data collection system for transport services

This accessibility statement applies to the Data collection system for transport services.

Accessibility status

The web service partially meets the Level AA requirements of the Web Content Accessibility Guidelines (WCAG) 2.1. Non-compliances with the requirements are mentioned below.

Non-accessible content

The content mentioned below is not accessible for the following reasons: Non-compliance with the Act on the Provision of Digital Services 306/2019

Visuals

• Contrasts: The contrast between text and background is insufficient, among other places, in failed transmissions within the table on the home page. There are also some deficiencies in the contrasts of user interface components. In some interactive elements, the contrast is insufficient, for example, during mouse focus. (WCAG 1.4.3, 1.4.11)
• Scalability: The header, part of the forms in the main content, and opening dialogs do not scale properly on a screen that is 320 CSS pixels wide. (WCAG 1.4.10)

Structure

• Text alternatives: There are deficiencies in the text alternatives for visual elements. Some icons lack a text alternative, or it is not descriptive. (WCAG 1.1.1, 4.1.2)
• Headings: The hierarchy of headings does not always correspond to the hierarchy of the page content. Some pages contain empty heading markings. (WCAG 1.3.1)
• Tables: There are occasionally deficiencies in the programmatic markings and structure of tables. There are accessibility issues in tables that can be sorted and filtered. The state or status has not been programmatically defined for an expandable table row. (WCAG 1.3.1, 2.1.1, 2.4.3, 2.4.6, 3.3.2)
• Correspondence between programmatic and visual implementation: Heading-value pairs are not programmatically presented. (WCAG 1.3.1)
• Programmatic implementation of elements: Some elements have not been programmatically implemented correctly, which means they cannot be used with a screen reader and/or a keyboard, and their meaning is not clarified by a screen reader. (WCAG 1.3.1, 4.1.2)
• Highlighting the active item: The selected item in the main and side menus has not been programmatically marked. (WCAG 1.3.1)
• Website language: The language of the website and text deviating from the website language have not been defined in the OTP login. (WCAG 3.1.1, 3.1.2)
• HTML code quality: There are some deficiencies in the quality of the HTML code. (WCAG 4.1.1)

Navigation

• Programmatic marking of page structure: Not all different areas of the pages (e.g., header, main content, and navigation menus) are programmatically marked. (WCAG 1.3.1)
• Focus order: The focus order does not always proceed in a logical sequence. (WCAG 2.4.3)
• Page titles: The page title does not describe the purpose of the page, but is identical on every page. (WCAG 2.4.2)
• Page changes: After a page change, the name of the new page cannot be determined via a screen reader. (WCAG 2.4.2, 2.4.3)
• Screen reader feedback: No feedback is given via screen reader regarding the success of some actions. (WCAG 4.1.3)
• Purpose of links: The text alternative for the logo link does not contain visible text. (WCAG 2.5.3)
  Multiple routes: It is only possible to reach different pages and forms via a single route. (WCAG 2.4.5)

Logging out

• Login time limit: The service session is valid only for a certain period. The user is not warned in advance about the expiration, nor given a simple way to continue. (WCAG 2.2.1)

Form elements

• Purpose of fields: Autocomplete is not offered in fields requesting the user's own data. (WCAG 1.3.5)
  Unexpected changes: After selecting certain form elements (such as a checkbox), the page reloads and the focus unexpectedly moves to the beginning of the page. (WCAG 3.2.2)
• Labels for form fields: Form field labels have not been programmatically connected to the form fields. (WCAG 1.3.1)
• Mandatory fields: Mandatory form fields are marked with an asterisk, but the meaning of the asterisk is not explained at the beginning of the form. (WCAG 3.3.2)
• Field-specific instructions: Instructions related to fields are provided only after the field and have not been programmatically connected to the fields. (WCAG 1.3.2, 3.3.2)
• Error messages: Detecting error messages and incorrect fields via a screen reader is challenging in places. Error messages are not always automatically read by a screen reader. (WCAG 3.3.1, 4.1.3)

Element-specific observations

• Language menu: The language menu has not been programmatically marked or named descriptively. The languages of the language links have not been programmatically defined. (WCAG 1.3.1, 4.1.2, 2.5.3, 3.1.2)
• Monthly monitoring of dispatch centers for taxi trips: Adding files is not possible when using assistive technology, as the required files are not accessible. (WCAG 1.3.1)

Files

• PDF files: There are deficiencies in the markings of the files. (WCAG 1.3.1, 2.4.2, 2.4.5)

Preparation of this accessibility statement

This statement was prepared on October 31, 2024

The statement was last reviewed on December 12, 2025

The Finnish Transport and Communications Agency Traficom is responsible for the accessibility of the data collection system for transport services and for the processing of feedback.

Enforcement procedure

If you notice accessibility problems on the website, first give feedback to the website administrator. It may take up to 14 days to receive a reply. If you are not satisfied with the response you receive or if you do not receive a response at all within two weeks, you can submit a complaint to the supervisory authority. The Accessibilityrequirements.fi website explains how to make a complaint and how the matter is handled.

Contact information of the supervisory authority

Finnish Transport and Communications Agency Traficom

P.O. Box 320, FI-00059 TRAFICOM

kirjaamo@traficom.fi