This accessibility statement applies to the website of the Property Transaction Service. NLS specialists have assessed the compliance of the website with accessibility requirements. The statement was revised on 20 January 2022.
The website is not yet fully compliant with accessibility requirements
The accessibility of the website was assessed on 15 October 2021. The assessment found that the website does not yet meet all the accessibility requirements.
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
- The main menu may be difficult to visualize with a screen reader due to the confusing structure. WCAG 1.3.1
- The description of stages in applications may be difficult to visualize with a screen reader due to the confusing structure. WCAG 1.3.1
- It may be difficult to distinguish links from the body text. WCAG 1.4.1
Moderate and minor issues in perceivability
- It may be difficult to understand which properties are being selected for the application with the help of a screen reader. WCAG 1.3.1
- It may be difficult to visualize the field used to indicate an estimate of the parcel’s area on the deed of transfer with the help of a screen reader. WCAG 1.3.1
- The site uses an “optional plural”, which screen readers cannot read sensibly. WCAG 1.3.1
- The column headings in the tables have not been defined an impact area, due to which the screen reader may not be able to associate them with the cells in the tables. WCAG 1.3.1
- Some items have not been presented in a sufficiently structured form, due to which the screen reader reads them to the user without interruption. WCAG 1.3.1
- The status of an application’s signatures may be difficult to understand with a screen reader due to the unclear structure. WCAG 1.3.1
- Some browsers may fail to autocomplete the mailing address if the mailing address contains multiple lines. WCAG 1.3.5
- On small screens, content may need to be scrolled in two directions. WCAG 1.4.10
Significant issues in operability
- The function buttons in the map view of the property cannot be operated with a keypad. WCAG 2.1.1
- There are no view-specific page titles used on the site. WCAG 2.4.2
- The main menu may be difficult to use with a screen reader due to the illogical focus order. WCAG 2.4.3
Moderate and minor issues in operability
- The application’s preview as a PDF file may be difficult to skip using the keyboard alone. WCAG 2.4.1
- The links to the new tab are not expressed clearly. WCAG 2.4.4
- It may be difficult for users to find the form for extinguishing a mortgage. WCAG 2.4.5
- The name tags of some fields are not sufficiently descriptive. WCAG 2.4.6
Significant issues in understandability
- The mandatory nature of all form fields cannot be determined programmatically. WCAG 3.3.2
Moderate and minor issues in terms of understandability
- It may be difficult for the user to perceive that they must pay the registration certificates of the desired property during the application process. WCAG 3.2.2
- When completing applications, the focus of the keyboard may move to an illogical location when the user updates the details of the parties to the application, for example. WCAG 3.2.2
- The navigation buttons of the applications are inconsistent. WCAG 3.2.3, WCAG 3.2.4
- Some fields, such as e-mail addresses, are not consistently marked, even though they ask for the same information. WCAG 3.2.4
- A description of the stages of the applications is not presented in all stages. WCAG 3.2.4
- There are individual error messages on the site that make it difficult for the user to identify the error situation. WCAG 3.3.3
- Correction suggestions for incorrect inputs are not always presented to the user. WCAG 3.3.3
Moderate and minor issues in robustness
- The website code does not fully correspond with the HTML5 standard in terms of invalid element hierarchies and data attributes, for example.
- The property map view’ function buttons are not named. WCAG 4.1.2
- An input error in the “Haku kohdetunnuksella” (Search by site ID) field cannot be identified with a screen reader. WCAG 4.1.2
- The purpose of the Surveypal embedding cannot be identified programmatically. WCAG 4.1.2
Other accessibility issues
Some PDF documents, such as printouts, supplementing requests and decisions are not accessible. For example, documents have not been code-marked or positioned using nested tables, due to which the documents are difficult to review with a screen reader or other assistive technology. WCAG 1.1.1, WCAG 1.3.1, WCAG 2.4.2, WCAG 2.4.3 and WCAG 4.1.2.
In addition, previewing the applications as PDF files is not available for all screen readers, although it has been implemented according to the HTML5 standard.
Correction plan for the website
The aforementioned issues discovered at the website will be corrected as soon as possible, by 2 March 2022 at the latest.