Accessibility statement: Maintenance of apartment information for housing companies

This accessibility statement applies to the Maintenance of apartment information for housing companies online service.

Specialists from the National Land Survey of Finland have assessed compliance with accessibility requirements. The statement was last updated on 1 December 2025. 

The website is not fully compliant with accessibility requirements  

The accessibility of the website was assessed on 17 November 2025. The assessment result was that the website did not yet meet all accessibility requirements.

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

The links on this statement are to the English version of WCAG 2.2. 

Significant perceivability issues

  • Information shown in lists of maintenance charges and loans is not transmitted to assistive technologies. However, the information can be accessed by opening the maintenance charge or loan page. WCAG 1.3.1
  • The project form has dropdown menus with subheadings. Subheadings are not transmitted to assistive technologies. In addition, subheadings are included in the number of options transmitted to assistive technologies. WCAG 1.3.1
  • The field of the maintenance charge form in which the euro amount of the maintenance charge is entered has no name. WCAG 1.3.1, 4.1.2
  • When navigating in the dropdown menus and calendar, the keyboard focus is displayed against a background colour that is poorly visible. WCAG 1.4.1, WCAG 2.4.7
  • The outlines of the input fields and dropdown menus are not sufficiently distinguishable from the background of the page. WCAG 1.4.11 

Moderate issues in perceivability 

  • Selection buttons are used on the website to select which objects to display. Selection buttons are missing a fieldset. WCAG 1.3.1
  • The content of the footer can be difficult to perceive with assistive technology. The footer has not been defined at the main level and there is no header structure in the footer. WCAG 1.3.1
  • File uploads related to owner apartments visually form a three-card entity. This structure is not transmitted programmatically. WCAG 1.3.1
  • The website uses turquoise text colour, which may not stand out well from the background. In some places, poorly visible turquoise is also used in showing key focus. Poorly visible shades of grey are used in the dropdown menu subheadings. WCAG 1.4.3, WCAG 1.4.11
  • In the mobile view, some of the content is broken at the end of the line by a few letters. The calendar also falls partially outside the view, but the date can also be entered manually. WCAG 1.4.10 

Minor perceivability issues 

  • Information on footer links taking the user to another website is not transmitted to assistive technologies. WCAG 1.1.1
  • There are ambiguities in some of the labels transmitted to assistive technologies. On the project pre-selection page, the fieldset lacks a description, and the VAT section of the maintenance charge form has two labels. WCAG 1.3.1, WCAG 3.3.2 

Critical issues in operability 

  • There are dropdown menus on the project form and possibly elsewhere that cannot be scrolled using the keyboard. WCAG 2.1.1 

Significant operability issues 

  • The page title does not always change when the user navigates to sub-pages. Forms do not have a unique page title, for example. WCAG 2.4.2, WCAG 3.2.4
  • Some pages on the main level can only be accessed through one channel (menu). WCAG 2.4.5
  • Opened information boxes remain open, even if the keyboard focus is moved away from them. WCAG 2.4.11
  • Scrolling the view does not always work properly. Therefore, when browsing using the keyboard, the target area may be hidden under the top or bottom bar. WCAG 2.4.11 

Moderate issues in operability 

  • There are a few tables on the website with hidden organising functionality. The functionality cannot be accessed using the keyboard. There is no visual tip about the function, but clicking will bring it up. The functionality can be found using the screen reader and it can also be used with the reader. However, the screen reader user is not told what happens with the buttons. Nothing always happens, even if the buttons exist. WCAG 1, WCAG 1.3.1, WCAG 2.1.1, WCAG 3.2, WCAG 3.2.4
  • There is a menu from in connection with the tables from which the number of objects to be displayed is selected. The visible text of the menu (e.g. "Show 20") and the name of the menu ("Open") do not match. WCAG 2.4.6, WCAG 2.5.3 

Minor issues in controllability 

  • If the user decides to add a party using the project form, two points will open to be filled in. The keyboard focus automatically moves to the latter position. WCAG 2.4.3, WCAG 3.2.2 

Significant issues in understandability 

  • Forms have search fields to make it easier to find suitable options in the dropdown menu. They work unpredictably on the keyboard. Sometimes, after typing a search term, pressing the tab key will not move the focus to the next object, but will select the first search result. If no results are found for the search term and the user presses enter in the search field, the search term will be cleared. When the "Clear selections" button in connection with the search field receives a focus, the search term is immediately cleared. WCAG 3.2, WCAG 3.2.1, WCAG 3.2.2, WCAG 3.3.7
  • Selecting the stage of the measure on the project form affects whether the start or end year is mandatory information. However, the choices are made in such an order that mandatoriness may change retrospectively. The user may inadvertently fail to fill in the section that has become mandatory. WCAG 3.2.2
  • Information about mandatory fields is not always transmitted to assistive technologies. Mandatory fields are also indicated interchangeably by the *symbol on the label or by a programmatic specification. WCAG 3.2.4, WCAG 3.3.2 

Moderate issues in understandability 

  • Contents transmitted from the calendar to assistive technologies are in English. WCAG 3.1
  • In forms and views for saved data, the keyboard focus sometimes moves to the beginning of the page if, for example, the user has edited the data in a pop-up window or cancelled a function. WCAG 3.2.2
  • Presses of button by the user or hovering the cursor over the object do not consistently produce a visual equivalent: sometimes there is no change, sometimes there is. WCAG 3.2.4
  • In connection with the confirmation of notifications, the user is not offered the opportunity to check the information before sending the confirmation. WCAG 3.3.4 

Minor issues in understandability 

  • There are inconsistencies in the individual positions. The words "find" and "search" are used interchangeably. Some menus are missing a tip text, although most have one. WCAG 3.2.4
  • The notification confirmation page has a fieldset with no description. However, the fieldset is preceded by an understandable label. WCAG 3.3.2 

Significant robustness issues 

  • When the form has fields filled in incorrectly, the assistive technology user will be notified of this. When the user corrects only some of the errors, the error message is not retransmitted even if saving is not successful. WCAG 4.1.3 

Moderate and minor issues in robustness

  • In the search functions of project listings, the assistive technology user is not told whether the search yielded any results at all and, if so, how many. WCAG 4.1.3
  • Forms have dropdown menus where the user can select multiple options. The aria-labelledby associated with the opened menu refers to an object that does not exist. The list is therefore unnamed. WCAG 1.3.1, WCAG 4.1.2 

Other accessibility issues 

PDF share lists downloaded from the service are not fully accessible. For example, documents have not been code-marked which means that understanding their content and structure using assistive technologies such as screen readers may be difficult. Furthermore, no language has been set for files, in which case screen readers may not necessarily be able to read everything correctly. WCAG 1.1.1, WCAG 1.3.1, WCAG 2.4.2, WCAG 2.4.6, WCAG 3.1.1, WCAG 4.1.2

The shareholder contact information downloaded from the service in Excel format is not fully accessible either. Among others, table headings are not defined as headings, empty cells appear in the table and the layout is compact. In addition, there is no heading or language specified for the file. WCAG 1.3.1, WCAG 2.4.2, WCAG 3.1.1 

Website correction plan 

The aforementioned issues discovered in the website will be corrected as soon as possible, by 1 June 2026 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 kirjaamo@maanmittauslaitos.fi.

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 Finnish Transport and Communications Agency Traficom.

Problems using the service?

Contact our technical support.