Accessibility statement – Import Declaration Service
Finnish Customs aims to guarantee the accessibility of its websites and online services in accordance with the Act on the Provision of Digital Services (306/2019).
This accessibility statement applies to the import declaration service.
Alternative service channels
If you are unable to use the import declaration service, send your declaration by post to the registry office (email@example.com) of Finnish Customs. You can also complete an import declaration in a customer service location of Finnish Customs. At the websites of Finnish Customs, you can view customer service locations on a map and the opening hours of customs offices. If necessary, customs officials will help you free of charge.
For help in using alternative services, please contact the customs information service, tel. +358 295 5201.
You can also authorise an agent, such as a forwarding company, or another person to submit an import declaration on your behalf.
Accessibility of the service
The accessibility of the service content does not fulfil the requirements laid down in the Act on the Provision of Digital Services.
Accessibility was tested on the basis of the Web Content Accessibility Guidelines (WCAG).
Identified accessibility issues
The recognised problems with accessability concerning the service are described below. If you identify any issue in the use of the service that is not listed below, please contact us.
The following content does not fulfil the requirements laid down in the Act on the Provision of Digital Services. These accessibility issues will be corrected.
- Keyboard focus is not clearly visible in some essential user interface components. This makes the use of the service much more difficult, as keyboard focus moves to the top of the page after each stage and after making changes to certain individual settings. There are issues, in particular, in increasing and decreasing the font size and in the “Etusivu” (Front page), “Haku” (Search) and “Ilmoitus” (Declaration) tabs. In addition, keyboard focus disappears occasionally in the hidden button element at the beginning of the form. Furthermore, the “Yksityishenkilö” (Private person) login button has no focus style, and focus disappears in a hidden button before the “Yritysasiakas” (Corporate customer) button.
- It is nearly impossible to focus keyboard commands on field-specific help texts, as the help texts change depending on the field. This makes it much more difficult to complete the form for users who cannot use a mouse or other similar pointer.
- If the declaration is not processed within a specific time, the system stops the processing without giving any separate warning. As a result, information may be misplaced and users may become frustrated.
- The programmatic name of “Maa” (Country) fields is unclear. The value of the “Maa” (Country) fields cannot be entered by simply typing the name of the country; instead, the country must be selected from a list, even if the list only included one option. As a result, it is possible that the country is selected incorrectly. Users of screen readers cannot obtain clear information about the type of the field (combobox). This issue also concerns other similar fields, such as “Aktiivisen kuljetusvälineen kansallisuus” (Nationality of active means of transport) and “Menettelykoodi (EU)” (Processing code (EU)).
- Help texts are very difficult to identify or use with a screen reader. In addition, they are difficult to identify without any visual context. Help texts are not read automatically together with related fields.
- All pages have the same header. This may confuse users of screen readers, as the service loads several pages that always move focus to the top of the page.
- The purpose/function of the “Lisää seuraava” (Add next) button can easily be misunderstood, because the button text does not provide any sufficient context and there can be a large number of buttons.
- The selection of the “Manner-Suomi/Ahvenanmaa” (Mainland Finland/Åland Islands) radiobuttons is difficult to understand because both buttons have an identical name: “Valitse Manner-Suomeen / Ahvenanmaalle radio button checked 2 of 2”.
- Users of screen readers obtain no information about any errors in the form without moving the focus indicator. Error messages presented when submitting a declaration are related to fields in previous phases. When correcting errors, users need to remember the error message and the field it is related to. This is particularly challenging for users of screen readers.
- Screen readers read visually hidden repetitive buttons, which may be confusing for users.
- There is only a slight difference in marking mandatory fields (asterisk) and absolutely mandatory fields (asterisk in brackets). These are practically impossible to separate from one another when using a screen reader (but also visually).
Making the following content accessible presents an unreasonable burden for the service provider because the service will be replaced by a new service in stages during 2020 and 2021.
- There are flaws in contrasts between the text and background and between user interface components and graphic elements. A weak contrast causes problems for older users and users with a poor vision, in particular. (WCAG 1.4.3, 1.4.11)
- As the service is not responsive, the page must also be scrolled horizontally after zooming in. (WCAG 1.4.4, 1.4.10)
- There are flaws in alternative texts of visual elements, such as the Finnish Customs logo, due to which users of screen readers obtain no information about them. (WCAG 1.1.1)
- Function buttons of tables are located in columns that have no column headers. As a result, users of screen readers need to listen to blank header cells. Furthermore, tables do not have any defined row headers, which makes it more difficult to understand different function buttons. (WCAG 1.3.1)
- The main menu of the service has not been marked programmatically as a menu, and users of screen readers cannot identify the content as a menu. (WCAG 4.1.2)
- Links that open in a new browser tab or window have not been marked. Furthermore, file links have not been marked. (WCAG 2.4.4)
- There are structural flaws in the HTML code that may affect the accessibility of the service. The XHTML 1.0 StrictDOCTYPE specification has been used in the service. It sets strict rules for the structure of HTML documents. However, the service’s HTML code does not adhere to these rules. (WCAG 4.1.1)
- As the language of language version links has not been defined, a screen reader usually mispronounces them using rules of an incorrect language. (WCAG 3.1.2)
- Title attributes have been used in all service elements. This results in unnecessary repetitions for users of screen readers.
- There are flaws in the labels of form fields; labels of combination boxes (combobox) have not been connected to form fields. Selections of the selection button group have not been connected programmatically, and the header of the group has not been marked using the <fieldset> tag. In addition, the “Saapumistunnus” (Arrival code) and “Saapumispäivä” (Arrival date) fields have not been marked as mandatory. (WCAG 1.3.1, 3.3.2)
- No purposes have been defined for form fields, such as the “Nimi” (Name) and “Yhteystieto” (Contact information) fields, on the basis of which browsers would know how to autocomplete the fields or offer the correct keyboard. (WCAG 1.3.5)
- In some situations, the system requires users to enter information, which the system already knows, such as the personal identity code or business ID. This information needs to be re-entered manually in the form, and the system displays an error message if the code or ID differs from the code or ID transmitted by the identification service used to log in to the service. (WCAG 1.3.5)
- In some places, default buttons have been highlighted by moving them above the form’s function button row. Changing the form’s HTML code structure in this way may make it more difficult for users of screen readers to perceive the form, considering that the location of buttons changes during the process. (WCAG 1.3.1, 3.2.2)
- Items can only be selected from the list of common items using a mouse. (WCAG 1.3.1, 1.4.13, 2.1.1)
- Users of screen readers do not receive any feedback on the completion of functions without moving the focus indicator. These functions include adding table rows, saving drafts and searches. (WCAG 4.1.3)
- The service has two separate in-page navigation trails with a different content. As the purpose or current stage of the trails is not indicated, the situation may be difficult to understand when using a screen reader. (WCAG 1.3.1)
- It may be difficult to notice and use adding and editing fields on table rows when using a screen reader. In addition, focus is difficult to control, and focus does not move to correct fields when editing. (WCAG 1.3.1, 2.4.3, 2.4.6)
- Drop-down menus sometimes request the user to select an item from the menu. Currently, this request seems like a default value, which is why users may ignore the relevant field.
- Users of screen readers do not obtain any information about the column, according to which search results have been arranged. (WCAG 4.1.2)
- The “Käyttöohjeet” (Instructions) page has flaws, for example, in DOCTYPE definitions, languages and header levels. (WCAG 1.3.1, 2.4.4, 3.1.1, 4.1.1)
Preparing the statement
Finnish Customs has tested the accessibility of the service as follows:
- Accessibility was tested by Eficode, an external party.
- The service was tested in April 2019.
- The statement was prepared on 18 September 2020.
- The statement was last reviewed on 18 September 2020.
We are happy to receive feedback on the accessibility of this service.
- Please send feedback on accessibility to Finnish Customs by emailing firstname.lastname@example.org.
- The declaration department of Finnish Customs is responsible for the accessibility of the import declaration service, and it also responds to feedback given on accessibility.
- We aim to respond to feedback in five working days.
- If you are dissatisfied with the response received from Finnish Customs, you can also send feedback on the accessibility of the service to the Regional State Administrative Agency (email@example.com).