Front Page: Web accessibility
Front Page: Web accessibility
Menu

The Finnish Transport and Communications Agency Traficom strives to guarantee the accessibility of its website in compliance with the Act on the provision of digital services.

This accessibility statement applies to the website saavutettavuusvaatimukset.fi.

See the accessibility statement for the accessibility statement tool here.

Website accessibility status

This website partly fulfils the requirements of the Finnish Act on the provision of digital services 306/2019 (External link). However, it meets the critical A and AA requirements of the WCAG criteria. Please see below for a list of non-conformities and exceptions applicable to the criteria.

Non-accessible content

The content discussed below is non-accessible for the specified reasons:

Non-compliance with the Act on the provision of digital services 306/2019 (External link)

The following content and/or functionalities do not yet meet the requirements:

The website does not fully adapt to the screen when the content width is 320 CSS pixels

In responsive view, the logo link in the header overlaps with the search button.

Accessibility criterion that is not met: WCAG Success Criterion 1.4.10 Reflow

Content cannot be hidden

The main navigation elements of the website open when the mouse pointer hovers over them. However, the appearing content cannot be hidden without moving the pointer.

Accessibility criterion that is not met: WCAG Success Criterion 1.4.13 Content on Hover or Focus

The heading levels do not fully follow the content hierarchy of the page

On the Finnish pages "Uutisia saavutettavuudesta" and "Kanteluiden päätöslyhennelmät", H2 subheadings are used. The headings that follow these are also programmatically marked as H2, even though they are hierarchically subordinate to the preceding subheading. Thus, the heading levels do not correspond to the content hierarchy of the page.

Accessibility criterion that is not met: WCAG Success Criterion 1.3.1 Info and Relationships

The updated number of search results is not automatically announced to the screen reader

When the number of search results changes on the search results page, the screen reader does not provide any feedback about the updated number of results without receiving focus.

Accessibility criterion that is not met: WCAG Success Criterion 4.1.3 Status Messages

The structure and relationships of the content for the option buttons cannot be programmatically determinable

The “Limit search results” option button group on the search results page is not defined as a form group, nor is the group’s heading linked to the group. Thus, the structure and relationship of the option buttons cannot be programmatically determined, for example, by a screen reader.

Accessibility criterion that is not met: WCAG Success Criterion 1.3.1 Info and Relationships

Accessibility issues related to forms

The user interface component lacks a name that describes its purpose

Info buttons on the forms, which open additional information, are missing a name that describes their purpose. Some buttons do not have any accessible name, causing the screen reader to announce only “button.” For some buttons, the accessible name consists of a text snippet that does not describe the purpose of the button but rather indicates the content that will appear when the button is activated.

Accessibility criterion that is not met: WCAG Success Criterion 1.1.1 Non-text Content

The label is not programmatically associated with the form field

On the accessibility complaint and clarification request form, for the input field "Have you submitted a complaint to another authority? ", the label is not programmatically associated with the corresponding input field. Two input fields share the same ID attribute id="json-textarea".

As a result, the screen reader does not read the help text for the "Have you submitted a complaint to another authority?" field, but instead incorrectly presents it in connection with the previous input field.

Accessibility criterion that is not met: WCAG Success Criterion 1.3.1 Info and Relationships 
Accessibility criterion that is not met: WCAG Success Criterion 4.1.1 Parsing

The purpose of input fields intended for collecting user information cannot be determined programmatically

The forms are used to collect user information:  Name, Email, Street address, Postal code, Town/City, and Phone. The purpose of these fields has not been defined using the corresponding values of the autocomplete attribute, and therefore the purpose of these input fields cannot be determined programmatically.

Accessibility criterion that is not met: WCAG Success Criterion 1.3.5 Identify Input Purpose

The contrast between text and background is insufficient

In the error summary displayed at the top of the form pages, the red text does not have sufficient contrast against the white background. The contrast ratio between the red error text and the white background is 3.76:1.

Accessibility criterion that is not met: WCAG Success Criterion 1.4.3 Contrast (Minimum)

The accessibility issues identified on the website will be fixed during 2025.

Accessibility statement preparation

This statement was prepared on 17th of December 2024.  

The statement is based on an evaluation carried out by an external expert organisation  on whether the accessibility statement tool meets the requirements of the Act on the Provision of Digital Services 306/2019 (External link) (External link).

The statement was updated on 19th of June 2025.

Feedback and contact details

Did you notice an accessibility problem on our website? Let us know about it, and we will do our best to offer the information and content in an accessible format as soon as possible! You can contact us either by using our online form or by email.

Use this online form to give feedback on accessibility

Email address for providing feedback: saavutettavuus(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 Finnish Transport and Communications Agency Traficom Digital Accessibility Supervision Unit. Traficom’s accessibility requirements website (saavutettavuusvaatimukset.fi) explains how you can lodge a complaint and how the matter will be processed.

Supervisory authority’s contact details

Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision

  • www.saavutettavuusvaatimukset.fi
  • saavutettavuus(at)traficom.fi
  • Telephone +358 29 534 5000 (exchange) 

 

Updated