Skip to main content

Accessibility statement: Paikkatietohakemisto

This accessibility statement applies to the Paikkatietohakemisto website. NLS specialists have assessed the compliance of the website with accessibility requirements. The statement was revised on 30 May 2023.

The website is not yet fully compliant with accessibility requirements

The accessibility of the website was assessed on 21 December 2021. It was stated that the website does not yet meet all the accessibility requirements. Most of the observed non-conformances only concern logged-in users, and logged-in users are a small percentage of all service users.

The accessibility issues discovered during the assessment are listed below. The findings are based on Web Content Accessibility Guidelines (WCAG) 2.1. The number and link provided after each finding indicates what WCAG section is not fulfilled at the website.

Significant issues in perceivability

  • Some icon buttons lack a descriptive name that describes their purpose. WCAG 1.1.1
  • Some fields are not programmatically linked to a label. WCAG 1.3.1
  • Some field groups have incomplete labels. WCAG 1.3.1
  • The Relations menu displayed in search results can be difficult to understand when using a screen reader. WCAG 1.3.1
  • The tabs in the record editing view can be difficult to understand when using a screen reader. WCAG 1.3.1
  • In the view where directory records are created, a button group has been defined as the header. WCAG 1.3.1
  • Some links do not stand out well enough from the surrounding text. WCAG 1.4.1

Moderate and minor issues in perceivability

  • The top menu can be difficult to understand when using a screen reader. WCAG 1.3.1
  • The list of the latest and most popular metadata displayed on the front page can be difficult to understand when using a screen reader. WCAG 1.3.1
  • The purpose of the input has been incorrectly defined in some of the fields. WCAG 1.3.5
  • The text on some buttons can be difficult to see. WCAG 1.4.3
  • When using a small screen, the user may also have to scroll the content sideways. WCAG 1.4.10
  • It may be difficult to see the difference between some UI components and the background. WCAG 1.4.11
  • The delete button for some fields can be difficult to hide. WCAG 1.4.13

Significant issues in operability

  • Some components in the search view work incorrectly when used with a keyboard alone. WCAG 1.1.2
  • Some components do not receive any keyboard alignment. WCAG 1.1.2
  • The site has some single-character hotkeys that cannot be reconfigured or disabled. WCAG 2.1.4
  • The site warns the user in advance that the session will end but does not provide any simple way to extend the session. WCAG 2.2.1
  • The site does not offer any simple method to bypass the top menu. WCAG 2.4.1
  • All pages have the same page title. WCAG 2.4.2

Moderate and minor issues in operability

  • The order of alignment is illogical in the case of some toolbars. WCAG 2.4.3
  • Some pages may be difficult to find, because they are only referenced from the top menu. WCAG 2.4.5
  • Some of the labels have been poorly translated into Finnish. WCAG 2.4.6
  • Keyboard alignment has been hidden in some components. WCAG 2.4.7

Significant issues in understandability

  • When using a screen reader, it is difficult to notice if an error has occurred when loading an XML file. WCAG 3.3.1
  • Insufficient labels have been used in some field groups. WCAG 3.3.2

Moderate and minor issues in terms of understandability

  • In the language menu, it is impossible to programmatically specify the language of the different options. WCAG 3.1.2

Significant issues in robustness

  • The site includes HTML elements with non-unique IDs. WCAG 1.1.4
  • The site’s DOCTYPE has been incorrectly defined. WCAG 1.1.4
  • The site includes some incorrect HTML element hierarchies. WCAG 1.1.4
  • The name, role and value of some components cannot be programmatically determined. WCAG 4.1.2

Moderate and minor issues in robustness

  • Some notifications, such as those you see when saving data, are difficult to detect when using a screen reader. WCAG 4.1.3

Plan on correcting the website

Most of the aforementioned issues discovered on the website will be corrected as soon as possible, by 31 December 2023 at the latest.

Give feedback on accessibility

You can give feedback on the accessibility of the website or request material on the website in an accessible format using an online form or by sending a request by e-mail to

We will answer your request as soon as possible, but no later than within two weeks. In extensive requests related to accessibility, the National Land Survey has the right to extend the response time with two weeks. If you are not satisfied with our reply or have not received a reply within two weeks, you can send a notification to the Regional State Administrative Agency for Southern Finland (in Finnish).

Problems using the service?