Accessibility of the web service

This accessibility statement explains how well the web service complies with the Act on the Provision of Digital Services, what shortcomings there are in the accessibility of the website and how you can give us feedback on accessibility problems.

HSY (Helsinki Region Environmental Services Authority municipal federation) is responsible for this web service. We want as many users as possible to be able to access our digital services. We take accessibility into account in the development of digital services.

How accessible is the website?

This web service partly meets the A and AA level accessibility criteria required by law (WCAG criteria 2.1). The web service has some shortcomings in accessibility, which are described in more detail below.

Did you notice any shortcomings in accessibility?

We are constantly striving to improve the accessibility of the web service. If you observe any issues that are not described on this page, please let us know and we will do our best to fix any shortcomings. We will respond within 14 days.

You can contact us using the online form

Accessibility monitoring

The Regional State Administrative Agency for Southern Finland monitors the implementation of accessibility requirements. If you are not satisfied with the response you have received or you do not receive a response at all within two weeks, you can give feedback to the Regional State Administrative Agency for Southern Finland. The website of the Regional State Administrative Agency for Southern Finland provides detailed information on how to file a complaint and how the matter will be processed.

Regional State Administrative Agency for Southern Finland
Accessibility Monitoring Unit
telephone (switchboard) +358 295 016 000

More detailed information on technical accessibility

The web service is not yet fully accessible.

Content or features that are not yet accessible

Structure and ways of presentation

  • Landmarks have been used in the service but they have not always been used according to the best practices. There is content in the service that has not been placed inside any landmark. (WCAG 1.3.1)
  • Icons and colors have been used inconsistently in some buttons and links, which may mislead users. (WCAG 3.2.4)
  • The web service has some inaccurate link texts. (WCAG 2.4.4)
  • There are some links in the service that the screen reader reads in the wrong language. (WCAG 3.1.2)
  • Some links have ingress texts that have been hidden from screen readers and are therefore omitted. (WCAG 1.3.1)
  • There are some links that do not have any underline and can only be recognized as links by color. (WCAG 1.4.1)
  • The keyboard focus indicator is not visible or is very poorly visible around some elements. (WCAG 2.4.7 and 1.4.11)
  • Colour combinations that do not provide sufficient contrast have been used in many situations. These include for example certain navigation links, buttons, some text content as well as metatexts of releases, announcements and events. (WCAG 1.4.3, 1.4.11)
  • There are some individual pages and files that have indescriptive titles. (WCAG 2.4.2)
  • There are some shortcomings in the use of headings. Some heading levels have been skipped and items that are not headings have been marked as headings. There are also headings that have not been marked programmatically as headings. Some headings also have empty lines inside them. (WCAG 1.3.1)
  • Some headings in the service are not descriptive enough. (WCAG 2.4.6)
  • There are some important announcements in which colour has been used as the only means of drawing the user’s attention. (WCAG 1.4.1)
  • There are some shortcomings in presenting information to screen readers. Some tables do not have header cells. There are also tables that the screen reader does not interpret as tables at all. There are also some numbered lists that have not been semantically marked as lists. In addition, the screen reader reads some content without spaces between words. (WCAG 1.3.1)
  • There are some images and icons on the website with no text equivalents, and they have not been hidden from screen readers. There are also some relevant images such as infographics, the alt text of which is not descriptive enough. (WCAG 1.1.1)
  • Some form fields and their labels have not been programmatically associated. Some menus do not have any visible label. (WCAG 1.3.1 and 3.3.2)
  • There are required form fields in which the screen reader does not inform the user about the required state. (WCAG 3.3.2)
  • There are embedded videos and maps inside iframes that do not have any accessible title. (WCAG 4.1.2)
  • There are some videos in the service that do not present all the relevant information audibly. These videos require complementary audio description. Captions are also missing from some videos. (WCAG 1.2.2, 1.2.3 and 1.2.5)
  • The service contains some documents (such as PDF) that are not fully accessible. Their semantic structure and reading order has not been marked, their titles are not descriptive, the images in the documents do not have a text alternative, and the contrasts are not sufficient. (WCAG 1.1.1, 1.3.1, 1.3.2, 1.4.3, 2.4.2)

Using the service

  • In some situations, screen reader users are not informed enough about changes that occur on a page or success of actions. (WCAG 4.1.3)
  • The visible and programmatical name of some links do not match each other. This may cause problems to users of speech recognition technology. (WCAG 2.5.3)
  • The filters of the search function have accessibility problems. The state of the filters is not announced to the screen reader. In addition, selection of a filter causes the page to reload. (WCAG 3.2.2 and 4.1.2)
  • Using some functions with a screen reader or by keyboard commands is challenging and in some cases impossible. (WCAG 2.1.1)
  • There are dropdown menus in the service that open already when they receive keyboard focus. The fields are not read properly by screen reader. The accessible name of the fields is indescriptive and in a wrong language. (WCAG 3.2.1, 1.3.1 and 2.4.6)
  • There are many user interface elements in the service that do not have any role or value. Some accordion elements do not also have any name. (WCAG 4.1.2)
  • There are some situations in which the user’s keyboard focus is moved to a new location without warning. (WCAG 3.2.2)
  • There are diagrams in the service that do not adapt properly to enlargenings or mobile displays. (WCAG 1.4.10)

Correction of Shortcomings in Accessibility

We are constantly working on correcting the shortcomings in accessibility that we have identified. The listed issues are aimed to be corrected by January 1, 2024.

Accessibility requirements do not apply to certain types of content

The web service contains videos that are not accessible. They lack captions and audio description, and there are problems with their keyboard use. According to law, multimedia content published before 23 September 2020 need not be made accessible retroactively or removed from the website.

The web service includes third-party map services that are not accessible. However, the law allows an exception for map content: maps and map services do not have to meet accessibility requirements.

How have we tested accessibility?

The observations in this accessibility statement are based on a third-party assessment of whether the online service meets legal requirements.

The web service was published on 11 June 2020.
This statement was prepared on 11 June 2020.
The statement was last updated on 30 August 2023.

Act on the Provision of Digital Services (306/2019)

Accessibility Requirements website