Significant issues in perceivability 

• The hierarchy of headings is incomplete and the relationships between headings of different levels do not visually match the displayed structure. WCAG 1.3.1 
• Significant overlap may emerge in the newsroom content when the text size or spacing is increased. Some of the content requires scrolling in two directions. WCAG 1.4.4, WCAG 1.4.12 
• In the mobile view, the release bar is often left partly hidden by other items. WCAG 1.4.10 
• The caret is not always sufficiently distinguishable from the background on the forms. WCAG 1.4.11 
• Use of the chat may be difficult for perceivability. For instance, the chat status/availability is only indicated with a colour, it is not possible to change the text size or spacing, and not all of the text on the feedback form is relayed to the screen reader. WCAG 1.3.3, WCAG 1.4.1, WCAG 1.4.4, WCAG 1.4.12 

Moderate issues in perceivability 

• The service point visiting address map is missing the descriptive texts for the locations. WCAG 1.1.1 
• Labelling of the tables is confusing. Tables without label cells are unusable in the mobile view. Tables are also used needlessly when simple text would suffice. WCAG 1.3.1, WCAG 1.4.10 
• The feedback survey refers to an uncertain item, through which a visitor can contact customer service. WCAG 1.3.3 
• Not all blue link text parts are sufficiently distinguishable from the rest of the text and the background. WCAG 1.4.1, WCAG 1.4.3 
• The text is not always sufficiently distinguishable from the background in the site navigation and search result page numbering. In the mobile view, text parts on top of images are difficult to see. WCAG 1.4.3 
• It is not possible to resize all the text parts of the feedback form. WCAG 1.4.4 
• Some of the content highlights in the newsroom mobile view are not shown, compared to the regular view. WCAG 1.4.10 
• There are headings on the site that do not fully fit a mobile screen. WCAG 1.4.10 
• Not all the text spacing of the forms’ menus and buttons can be changed. WCAG 1.4.12 

Minor issues in perceivability 

• Some individual images are missing alternate text or are not marked as decorative. WCAG 1.1.1 
• Form input fields are not all consistently named. WCAG 1.3.5  
• The text on a few filter buttons overflows from the button when the text size or spacing is changed. There are other locations in which text overflows from boundaries when text spacing is changed. WCAG 1.4.4, WCAG 1.4.12 
• Some links use a light border to indicate focus instead of underlining. The light border is not sufficiently distinguishable from the background. WCAG 1.4.11 
• The page has empty elements as well as elements with an overlapping ID. WCAG 1.3.1, WCAG 4.1.1 

Significant issues in operability 

• In the mobile view, the top navigation does not open with the keyboard; the focus moves to the menu items one by one. WCAG 2.1, WCAG 2.4, WCAG 3.2.1 
• The order of keyboard focus in the chat is not logical and also picks parts with no interaction. WCAG 2.4.3 
• The displayed name and name given to assistive technologies on the forms’ file attachment button do not match. The price list search field labels are poorly named and an instructive text is marked as a heading. WCAG 2.4.6, WCAG 2.5.3 
• Some search fields and drop-down menus are not labelled. WCAG 2.4.6 
• The keyboard caret is not visible in the newsroom filters, the main pages’ thematic highlights, or all the drop-down menus. WCAG 2.4.7 

Moderate issues in operability 

• The website contains repeated or nearly-repeated page titles, which do not always comprehensively describe the page content. WCAG 2.4.2 
• The focus order of the newsroom items does not match the visible order, when the text size or spacing is changed. WCAG 2.4.3 
• The focus order is un-intuitive in the search function and the list search results. WCAG 2.4.3 
• Some link text shown to assistive technologies include English. WCAG 2.4.4 
• The keyboard caret is not properly visible around the National Land Survey logo and the language menu at the top of the page. WCAG 2.4.7 

Significant issues in understandability 

• When using the Tab key to browse through the filters, selecting an option may move the focus to the start of the filter. Filters that appear separate may have been implemented together, in which case the focus moves to the beginning of the first filter. WCAG 3.2.2 
• One navigation menu is unnamed and opens directly to a sub-page from the Newsroom link in the main navigation pane. In the mobile view, this menu is named “menu”. WCAG 3.2.3 
• The Online Service navigation menu only appears after a presentation page for a service is opened. WCAG 3.2.3 
• Incorrectly completed multiple-choice questions on forms are not always high-lit with the same method as other incorrect parts. WCAG 3.2.4 
• On some forms, the required fields are not shown in text form or required fields are not unambiguously marked. WCAG 3.3.2 
• There are many fields with the same name on forms, due to which error reports do not always unambiguously indicate an incorrectly completed field. WCAG 3.3.3 

Moderate issues in understandability 

• In the mobile view, there are differences between similar pages regarding the presentation and focus orders of page sections. There are also differences in the page order between the mobile view and the desktop view. WCAG 3.2.3, WCAG 2.4.3 
• Derivatives of “search” and “find” are used interchangeably on the website. WCAG 3.2.4 
• Completing the “Other, specify?” may be difficult due to the inconsistent form structure. WCAG 3.3 
• The help text for the apartment ownership service wizard is not shown until the first question. WCAG 3.3.2 
• Form errors may be difficult to read because incorrectly completed fields are listed in a different order from what they are shown on the form. WCAG 3.3.3 

Minor issues in understandability 

• The use of symbols and colours on the Online Service page differs from those on the front page. WCAG 3.2.4 
• The search instructions for the newsroom are not specific, especially in the mobile view, and they rely on vision. WCAG 3.3.2, WCAG 1.3.3