Accessibility statement – Safety and Security Declaration Service (AREX)

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 Safety and Security Declaration Service (AREX).

Alternative service channels

If you are unable to use AREX, you can submit your declaration by emailing spake.arex@tulli.fi.

You can also complete an entry or exit 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.

See the instructions for other service alternatives (in Finnish).

You can also authorise an agent, such as a forwarding company, or another person to submit an entry or exit declaration on your behalf.

Accessibility of the service

The accessibility of the service 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 following content does not fulfil the requirements laid down in the Act on the Provision of Digital Services. These accessibility issues will be corrected. If you identify any issue in the use of the service that is not listed below, please contact us.

  • Keyboard focus is not clearly visible in some essential user interface components. In addition, keyboard focus disappears occasionally in the hidden button element at the beginning of the form. (WCAG 2.4.7)
  • It is nearly impossible to focus keyboard commands on field-specific help texts, as the help texts change depending on the field. (WCAG 2.1.1)
  • Some field groups are hidden by default, and users of keyboards and screen readers cannot open these hidden groups. (WCAG 2.1.1)
  • The programmatic name of “Country” fields is unclear. The value of the “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. Users of screen readers cannot obtain clear information about the type of the field. Other fields implemented in the same way have similar issues. (WCAG 4.1.2)
  • Help texts are very difficult to identify or use with a screen reader. Help texts are not read automatically together with related fields. (WCAG 1.3.1)
  • The CAPTCHA code presented to users who have not logged in is not accessible when using a screen reader. This means that users of screen readers cannot use the service without logging in. (WCAG 1.1.1 and 4.1.2)
  • 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. (WCAG 2.2.1)
  • 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. (WCAG 2.4.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 refer to fields in previous phases. (WCAG 4.1.3 and 3.3.1)
  • Screen readers read visually hidden repetitive buttons, which may be confusing for users. (WCAG 1.3.1)
  • 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). (WCAG 1.3.1 and 3.3.2)
  • The labels of checkboxes have not been connected to form fields. (WCAG 4.1.2)
  • The purpose/function of the “Add line” and “Delete” buttons can easily be misunderstood, because the button text does not provide any sufficient context and there can be several buttons per page. (WCAG 1.3.1 and 4.1.2)

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 by 2024.

  • Contrast
    • There are flaws in contrasts between the text and the background. (WCAG 1.4.3)
    • There are flaws in contrasts between user interface components and graphic elements. (WCAG 1.4.11)
  • Help texts
    • Field-specific help texts may be difficult to identify when enlarging the content because they are presented in a floating help text element. (WCAG 1.4.4, 1.4.10)
    • Some help texts are unclear. (WCAG 3.3.2)
  • “Instructions on how to use the service” page
    • The title attribute, language and sub-headers of the “Instructions on how to use the service” page have not been defined so that a screen reader can read this information correctly. (WCAG 1.3.1, 2.4.2, 3.1.1)
    • The file type of file links is not part of the link text. (WCAG 2.4.4)
  • The service does not include any hyperlinks to the main content. (WCAG 2.4.1)
  • As the language of language version links has not been defined, a screen reader may mispronounce them using rules of an incorrect language. (WCAG 3.1.2)
  • As not all links opening in a new browser tab or window have been marked, users obtain no advance information about this function. (WCAG 2.4.4)
  • As the service is not responsive, the page must also be scrolled horizontally after zooming in. (WCAG 1.4.4 and 1.4.10)
  • There are flaws in alternative texts of visual elements. (WCAG 1.1.1)
  • There are structural flaws in the HTML code. (WCAG 4.1.1)
  • In-page navigation
    • In-page navigation is presented in the form of links, for which no explanation is provided. (WCAG 1.3.1)
    • The selected stage is only indicated by the background colour, which does not fulfil contrast requirements. (WCAG 2.4.4, 4.1.2 and 1.4.11)
  • No autocomplete feature is offered for input fields. (WCAG 1.3.5)
  • The calendar element cannot be used with a keyboard. However, the date can be entered. (WCAG 2.1.1)
  • The title attribute of the “Hide Help/Show Help” button is always “Hide Help”, also when the text is “Show Help”. (WCAG 4.1.2)
  • The “Help”, “System info” and “Call center” texts and the bold sub-headers on the front page have not been defined as HTML headers. There are flaws in table headers. (WCAG 1.3.1)
  • The service’s main menu has not been marked programmatically as a header. (WCAG 1.3.1)
  • The declaration type is not indicated for users after saving the declaration. (WCAG 3.3.2)
  • Users of screen readers do not obtain any information about the order of search results. (WCAG 4.1.2)
  • Users of screen readers do not receive any feedback on successful functions without moving the focus indicator. (WCAG 4.1.3)
  • It is difficult to add and edit table rows when using a screen reader. (WCAG 1.3.1, 2.4.3 and 2.4.6)

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 February 2019.
  • The statement was prepared on 22 September 2020.   
  • The statement was last reviewed on 22 September 2020.

Feedback

We are happy to receive feedback on the accessibility of this service. 

  • Please send feedback on accessibility to Finnish Customs by emailing asiakaspalautteet@tulli.fi.
  • The declaration department of Finnish Customs is responsible for the accessibility of the AREX 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 (saavutettavuus@avi.fi).