Front Page: Traficom
Front Page: Traficom
Menu

Accessibility statement

Traficom strives to guarantee the accessibility of their e-services in compliance with the Act on the Provision of Digital Services (306/2019).

Website accessibility status

The service is partially compliant with the requirements of the Web Content Accessibility Guidelines (WCAG) 2.1 level AA. Failure to comply with the requirements is mentioned below.

Non-accessible content

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

Visuality

  • Contrast: The contrast between the text and background is insufficient, e.g. in the failed sending of the table on the front page. There are also some flaws in the contrasts of the user interface components. (WCAG 1.4.3, 1.4.11)
  • Scaling: The header, some of the forms in the main content, as well as the dialogues that open, do not scale to a screen that is 320 CSS pixels wide. (WCAG 1.4.10)
  • Visible alignment: A few elements do not have a visible keyboard alignment indicator. (WCAG 2.4.7)

Structure

  • Text alternatives: Text alternatives missing for visual elements. The text equivalent of some icons is missing or is not descriptive. (WCAG 1.1.1, 4.1.2)
  • Titles: The hierarchy of titles does not always correspond to the hierarchy of web page contents. (WCAG 1.3.1)
  • Tables: There are some gaps in the programmatic labelling and structure of the tables. There are shortcomings in the accessibility of tables that are arranged and filtered. There is no programmatically defined space for the line in the table that opens. (WCAG 1.3.1, 2.1.1, 2.4.3, 2.4.6, 3.3.2)
  • Equivalence of programmatic and visual implementation: The title-value pairs are not programmatically represented. (WCAG 1.3.1)
  • Highlighting the active object: The selected item in the main and side menus is not programmatically marked. (WCAG 1.3.1)
  • Language of the site: The language of the site and the text that differs from the language of the site are not specified in the OTP login. (WCAG 3.1.1, 3.1.2)
  • HTML code quality: There are some deficiencies in the HTML code. (WCAG 4.1.1)

Navigation

  • Additional information (i): It is not possible to move the pointer to additional information without losing the content. Additional content does not receive keyboard focus. Through a screen reader, additional content is read only occasionally. (WCAG 1.3.1, 1.4.13, 2.1.1)
  • The programmatic labelling of the page structure: Not all the different areas of the pages (e.g. header, main content, and navigation menus) are programmatically marked. (WCAG 1.3.1)
  • Alignment order: The alignment order does not always proceed in a logical order. (WCAG 2.4.3)
  • Titles of web pages: The page name (title) does not describe the purpose of the page, but is identical to each page. (WCAG 2.4.2)
  • Changing pages: After the page has been changed, the screen reader will not know the name of the new page. (WCAG 2.4.2, 2.4.3)
  • Purpose of links: The text alternative for the logo link does not include visible text. (WCAG 2.5.3)
  • More than one route: It is only possible to access different pages and forms by a single route. (WCAG 2.4.5)

Logging out

  • Time limit for login: The service session is only valid for a certain period of time. There is no advance warning of time out to the user or a simple way to proceed. (WCAG 2.1.2)

Form elements

  • Purpose of the field: The fields that ask for the user's own information do not provide automatic completion. (WCAG 1.3.5)
  • Surprising changes: After selecting some form elements (such as the checkbox), the page loads again and the focus suddenly moves to the top of the page. (WCAG 3.2.2)
  • Form field labels: Form field labels have not been programmatically connected with form fields. (WCAG 1.3.1)
  • Mandatory fields: The mandatory form fields are marked with an asterisk, but the meaning of the star is not explained at the beginning of the form. (WCAG 3.3.2)
  • Field-specific instructions: The instructions related to the fields have only been provided after the field and are not programmatically linked 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 some places. Error messages are not automatically always read by a screen reader. (WCAG 1.3.3, 4.1.3)

Element-specific notes

  • Language menu: There are shortcomings in the programmatic implementation of the language menu. The status of the menu button (opened/closed) is not indicated when using a screen reader. (WCAG 1.3.1, 4.1.2)
  • Monthly tracking of taxi journey dispatch and brokerage centres: It is not possible to add a file in use of assistive devices as the required files are not accessible. (WCAG 1.3.1)

Files

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

Accessibility statement preparation

This statement was prepared on 2 November 2020 and updated 21 August 2024. 

The statement is based on an assessment of whether or not the data collection system meets the requirements of the Act on the Provision of Digital Services (306/2019) (External link). The assessment was carried out by a third-party expert organisation (Eficode Oy).

Feedback and contact details

You can give feedback on the accessibility of the data collection system of transport services with this online form or via email. 

Use this online form to give feedback on accessibility (External link)

Email address for providing feedback: lipatiedonkeruu(at)traficom.fi

Implementation procedure

If you notice accessibility issues on the website, first give feedback to the website administrator. Receiving a response may take 14 days. If you are not satisfied with the response or you receive no response within two weeks, you can provide feedback to the Regional State Administrative Agency for Southern Finland. 

Supervisory authority’s contact details

Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit 

Updated