Accessibility of the avoindata.fi online service
This accessibility statement explains how well the avoindata.fi online 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.
The Digital and Population Data Services Agency is responsible for this online 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 online service mostly meets the A and AA level accessibility criteria required by law (WCAG criteria 2.1). The online service has some shortcomings in accessibility, which are described in more detail below.
Did you notice any gaps in accessibility?
We are constantly striving to improve the accessibility of the online 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 to requests and comments as soon as possible, but no later than within two weeks.
You can contact us by sending an email to saavutettavuus(at)dvv.fi.
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
Accessibility Requirements online service
Telephone (switchboard) +358 295 016 000
More detailed information on technical accessibility
The online service is not yet fully accessible. The features listed below are not yet completely accessible.
Navigating the website using a screen reader or keyboard
- The internal structure and navigation of the website is not completely accessible. For example, it is not possible to skip the Twitter feed on the front page. (WCAG 2.4.5, 3.2.3)
- Some pages on the website do not use descriptive headings and the semantic relationships are not indicated properly. There are shortcomings in the use of heading levels on some pages. Some heading levels have been skipped and not all headings have been programmed as headings. There are multiple level one headings on the front page. (WCAG 1.3.1, 2.4.6, 4.1.1, 4.1.2)
- Some link texts are not descriptive. Some pages use the same link text multiple times with different links. Some link texts do not describe the content of the link sufficiently. On some pages, the same link is repeated twice for no reason. (WCAG 2.4.4)
- On some pages, the websites elements, such as elements used to control the website or forms, have not been programmed to be connected. Due to this, some pages do not follow a logical order when used with a screen reader. (WCAG 1.3.5, 2.4.5, 2.5.3, 3.3.2, 4.1.3)
- Some of the forms are not completely accessible. Using the forms with a screen reader or keyboard is difficult and, in some cases, impossible (e.g. the date picker). (WCAG 2.1.4, 3.2.4, 3.3.1, 3.3.2, 3.3.3)
- On some pages, the reading sequence is not logical. Similarly, on some pages, the focus order is not logical. (WCAG 1.3.2, 2.4.3) For example, using the advanced search function with a screen reader has proved to be very challenging.
- The contrast ratio on some elements is not adequate. (WCAG 1.4.3, 1.4.11)
- Some of the images on the website do not have a text alternative. This concerns especially the producers’ logos and showcase images, as it is currently not possible for the user to add text alternatives to them. (WCAG 1.1.1)
- The keyboard focus indicator is not visible in all components and it is not possible to use all features with a keyboard. (WCAG 2.1.1., 2.1.2, 2.4.7)
- The column headings of some tables in the user guides have not been programmatically defined. (WCAG 1.3.1)
- There are shortcomings in the Swedish translations of the user interface texts. The missing translations have not been programmatically determined to be in a different language. (WCAG 3.1.1, 3.1.2)
- The previews of APIs following the OpenAPI architecture are presented using the Swagger UI component developed and maintained by SmartBear Software. Some of the headings in the component are not descriptive and heading levels are not used logically. (WCAG 2.4.6) Some of the Swagger UI components and their relationships with each other have not been programmatically determined. (WCAG 1.3.5, 2.4.5, 2.5.3, 3.3.2, 4.1.3)
An effort will be made to correct the shortcomings listed in this statement during 2021.
Accessibility requirements do not apply to certain content
The main content on avoindata.fi are the datasets produced and added by different organisations. These datasets are considered third-party content, and the service provider is not able to make them accessible. The service provider can, however, instruct the users to produce accessible content. You can request the data in an accessible format by contacting the dataset maintainer directly. Each dataset’s information includes the contact information for the maintainer.
Not all organisations have published information about themselves or their datasets in Swedish or in English. These descriptions are considered third-party content, and the service provider is not able to make them accessible.
Some of the organisations on avoindata.fi have added previews to their data, for instance map data in the WMS and WFS formats or data in the CSV format. These previews are not accessible. The previews are considered third-party content, and the service provider is not able to make them accessible.
How have we tested accessibility?
The observations in this accessibility statement are based on an assessment by Avaava Oy on whether the online service meets legal requirements.
The online service was published on 15 September 2014.
This statement was prepared on 21 August 2020.
The statement was last updated on 21 August 2020.