Accessibility statement of the Disturbance Management System (Häriönhallintajärjestelmä, HHJ)

Content with insufficient accessibility has been specified below.

Non-compliance with the Act on the Provision of Digital Services 306/2019

Visual shortcomings

• The contrast of the edges of error text and entry fields, for example, is poor and the fields may be difficult to see. (WCAG 1.4.3, 1.4.11)
• Links have only been separated from the text body with the use of colour, and they may be difficult to discern. (WCAG 1.4.1)
• The service is not responsive. (WCAG 1.4.10)
• If the user enlarges the text only, the main menu will only be partially visible. (WCAG 1.4.4)
• The keyboard focus indicator is not visible on all elements. (WCAG 2.4.7)

General shortcomings in the programmatic structure

• The service language is determined as English, which may make using the service with a screenreader difficult. (WCAG 3.1.1)
• There are shortcomings in the conveyance of the structures of the page for screenreader users, e.g. the various sections or headings on the page have not been conveyed programmatically at all. The service also lacks anchor links, meaning that recurring sections of the webpage cannot be bypassed using assistive technologies. (WCAG 1.3.1, 2.4.1)
• The service contains some icons with no text alternatives. (WCAG 1.1.1)

Shortcomings in navigation

• The main menu of the page has not been programmatically determined as a navigation element. The current page is also not conveyed programmatically. (WCAG 1.3.1, 4.1.2)
• The webpage does not contain alternative ways of locating pages, e.g. search field or sitemap. (WCAG 2.4.5)
• All of the pages have the same title (Traficom e-services – HHJ), which makes it difficult to tell the pages apart. (WCAG 2.4.2)
• The screenreader does not indicate clearly when views are loading. The contrast of the loading graphic is also weak, making it difficult to see. (WCAG 4.1.3, 1.4.11)
• The instructions concerning the Notifications to be followed page mention tabs, even though the service does not have programmed tabs; instead, tabs refer to the links at the top of the page. (WCAG 1.3.1)

Shortcomings related to different components

• The New messages and Tasks links after the main menu open lists when the user hovers their mouse over the link. The lists cannot, however, be closed without moving focus. Opening lists with the keyboard is unreliable, and lists are impossible to open using a screenreader. (WCAG 1.4.13, 2.1.1)
• Some of the heading texts can be activated to open and close content. This is not clear to users using a screenreader, and the texts are inaccessible using a keyboard (WCAG 2.1.1, 4.1.2)

Shortcomings related to tables

• The page uses table structures liberally even when not conveying tables of data; instead, tables have been used for formatting, which distracts screenreader users. (WCAG 1.3.1)
• The tables have been paged at the beginning of the table as a nested table without a clear heading or programmatic indication of which page is selected (WCAG 1.3.1)
• The tables are updated automatically at certain intervals, causing the keyboard focus to jump back to the beginning while the user is navigating the table. (WCAG 2.4.3, 2.1.1)
• The ordering functions of the columns are cumbersome when used with assistive technologies, e.g. columns may only be ordered by dragging. (WCAG 2.1.1)
• The table on the Notifications to be followed page has a filtering function with shortcomings. The filtering fields do not e.g. have any name labels and the filter button does not have alternative text or a programmatic indication that the button opens a menu. The filtering occurs when focus is removed from the filtering field. (WCAG 1.1.1, 3.3.2, 3.2.1, 4.1.2)

Shortcomings related to forms

• Some form fields are missing labels entirely. Most fields have labels, but they have not been connected to the fields programmatically, resulting in the screenreader having difficulties in perceiving which information is required in which field. Neither has the grouping of the form fields been conveyed programmatically. (WCAG 3.3.2, 1.3.1)
• Mandatory fields have been marked with asterisks with low contrast, and the significance of the asterisk has not been explained. There are no programmatic instructions indicating that the fields are mandatory. (1.4.3, 3.3.2)
• Many of the forms have been implemented in tables, making them difficult to use with a screenreader. In some cases, the reading sequence is incorrect, because the name labels on one row are read first, followed by the fields on the following row. (WCAG 1.3.1, 1.3.2)
• Any errors in completing the form are only displayed at the top of the form. Focus is not moved up after pressing the button for moving forward, making it difficult for the user to discern why they are unable to move forward on the form. When forming an area, the error message is provided immediately, but the message is only displayed for a short period of time and it will not be read by the screenreader without separately moving focus. (WCAG 1.3.2, 4.1.3)
• When creating a new password, the password requirements are only displayed when the password does not meet the requirements. (WCAG 3.3.2)
• Clicking the ‘i’ icon on the form will display more instructions on how to complete the field. However, the icon does not have a text alternative, and it cannot be accessed using the keyboard or assistive technologies. Furthermore, the instructions cannot be closed without moving the focus of the mouse. (WCAG 1.1.1, 2.1.1, 1.4.13)
• The forms use two methods of adding attachments. In the other, the text on the button reads Browse, but its accessible label is Select file. (WCAG 2.5.3, 3.2.4)
• There is no autocomplete feature for the User ID and Password fields. (WCAG 1.3.5)
• When reporting a disruption, the Which communications service is affected field will open a quite complicated drop-down menu. The headings in the menu are links that select the check boxes below them, which is not apparent to the user. When a field is opened, focus is moved to the first check box, which may result in screenreader users missing the Select all and Deselect all options provided above the first check box. (WCAG 1.3.2, 4.1.2)

Applicable law does not cover the content in question

When reporting and browsing maps, the service has faults and a separate disturbance map view. These maps are not completely accessible.