Accessibility statement for the form service

This accessibility statement applies to the Form service.

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

• Scalability: Not all content of the service scales readably on a screen that is 320 CSS pixels wide. (WCAG 1.4.10)
• Visible keyboard focus: Some buttons lack a visible keyboard focus indicator. (WCAG 2.4.7)

Structure

• Headings: Some headings are not programmatically marked as headings. Some views contain empty heading markings. (WCAG 1.3.1)
• Lists: There are deficiencies in the programmatic marking of some lists. (WCAG 1.3.1)
• Accessible names: The accessible names of some buttons do not match the language of the specific language version. (WCAG 2.4.6)

Form elements

• Labels for form fields: The visible labels of some form elements do not match their programmatic labels, which may complicate the use of voice commands. (WCAG 2.5.3)
• Field-specific instructions: Instructions located below some form fields have not been programmatically connected to the fields. (WCAG 1.3.1)
• Drop-down menus: The additional information buttons in some drop-down menus cannot be accessed with a screen reader. In some drop-down menus, options can be searched using a search field, but the search results are not announced by a screen reader. (WCAG 1.3.1, 4.1.3, 1.3.2)
• Form groups: Not all form groups are programmatically marked or named. (WCAG 1.3.1)
• Mandatory fields: There are deficiencies in the markings of mandatory fields. (WCAG 3.3.2)
• Error summary: The error summary lacks a programmatic heading level and a list element. In some cases, programmatic focus does not transfer to the beginning of the error summary. (WCAG 1.3.1, 2.4.3, 1.3.2)
• Date entry: When focusing on the date field, the calendar element opens automatically and assistive technology users are forced to navigate through it, even though the calendar element is not accessible. The visible label of the date entry fields and the accessible name do not always match. (WCAG 2.5.3, 3.2.2, 1.3.1, 4.1.2)
• Adding and removing fields: In some cases, fields can be added and removed. However, no announcement is made via a screen reader regarding a successful addition or removal. The names of the Add and Delete buttons do not clarify via a screen reader what they are removing. (WCAG 4.1.3, 1.3.2, 2.4.3, 2.4.6)
• Captcha verification: Some forms feature a Captcha verification that requires a cognitive function test. The user can change the verification text themselves, but the change of text is not announced via a screen reader. (WCAG 3.3.8, 4.1.3)

Element-specific deficiencies

• Header: There is an unnecessary navigation element in the header. Links opening in a new tab within the header have not been programmatically marked. (WCAG 1.3.1, 4.1.2)
• Header mobile view: The menu buttons lack programmatic information about their state (open/closed). When the menus open, the accessible name of the menu buttons disappears. In addition, when opening the menus, screen reader and keyboard focus automatically transfer to the first button in the menu. Furthermore, keyboard focus becomes trapped inside the drop-down menus. (WCAG 4.1.2, 2.4.3, 1.3.2, 2.1.2)
• Language menu: The language menu region has not been programmatically marked or named descriptively. When opening the menu, screen reader and keyboard focus automatically transfer to the first button in the menu. In addition, keyboard focus becomes trapped inside the drop-down menus. The selected language has not been programmatically marked. The language of the language links has not been programmatically defined. (WCAG 1.3.1, 4.1.3, 1.3.2, 2.4.3, 3.1.2)
• Footer: The text alternative for the footer logo is not descriptive. The Back to top button does not transfer programmatic focus; instead, it remains on the button. (WCAG 1.1.1, 1.3.2, 2.4.3)
• Adding attachments: Adding or removing attachments is not announced in any way via a screen reader. (WCAG 1.3.2, 4.1.3)
   

Preparation of this accessibility statement

This statement was prepared on March 5, 2026.
The statement was last updated on March 5, 2026.

The Finnish Transport and Communications Agency Traficom is responsible for the accessibility of the Accessibility statement for the form service and 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 Digital Accessibility Supervisory Unit

www.accessibilityrequirements.fi 

e-mail: accessibility@traficom.fi 

Telephone switchboard: 029 534 5000