Accessibility statement – Customs Clearance Service

Finnish Customs is committed to making its websites and online services accessible in accordance with the Act on the Provision of Digital Services (306/2019).

This accessibility statement concerns the Customs Clearance Service.

Other service alternatives

If you are not able to use the Customs Clearance Service, there are other alternatives for transactions with Customs. You can authorise someone else to declare the goods on your behalf via the service or you can buy the declaration as a service from a forwarding company.

You can also visit a customs office that provides customer service to give us your feedback. On our website, you will find the map locations of the customs offices with customer service and their opening hours.

Help regarding alternative transactions is available from the Customs Information Service, tel. 0295 5201.

See Customs’ instructions for other service alternatives.

The accessibility of the service

Current accessibility of the content of the service: partly meets the requirements laid down in the Finnish Act on the Provision of Digital Services.

The known problems with accessibility

The service still has some usability problems. The recognised problems with accessibility are described below. If you notice a problem in the service that is not included in the list, please contact us.  

The following content does not meet the requirements laid down in the Act on the Provision of Digital Services and will be fixed as soon as possible.

The page “Choose the type of a new declaration”

  • The check button structure has flaws that make the page difficult to use with a screen reader. (WCAG 1.3.1 and 4.1.2)
  • The page has unnecessary messages in English, which disturb screen reader users. (WCAG 4.1.3)
  • The field for tracking ID has been marked as mandatory, although it is optional. The field does not have a programmatic label. (WCAG 4.1.2)
  • Inactive alternatives are read by screen readers as active. (WCAG 4.1.2)

The Add functions

  • The service uses several different structures for similar Add functions, which makes it more difficult to learn to use the function with a screen reader. (WCAG 1.3.1 and 3.2.4)
  • Some of the Add functions have a multiple-choice implementation based on check boxes, which is complicated to use with a screen reader. (WCAG 1.3.1 and 4.1.2)
  • When a screen reader user clicks on Add, they aren’t in all cases informed that new fields have been added to the view. Sometimes the fields are added in the code before the button, so they can be difficult to notice. (WCAG 2.4.3 and 4.1.3)
  • The table row form fields added using the Add function don’t have programmatic labels. (WCAG 1.3.1 and 4.1.2)

Input fields

  • The relationship between alternative fields isn’t always clearly indicated, and their operation may be unexpected for the user. (WCAG 1.3.1, 3.3.2 and 2.4.6)
  • Some of the blank inactive fields are indicated as mandatory. (WCAG 3.3.2)
  • After the user’s input, some of the optional fields suddenly become mandatory and vice versa. (WCAG 1.3.1, 3.2.2)
  • The automatic retrieval of information when focus moves may be unexpected for the user, when fields suddenly become inactive. (WCAG 3.2.1, 3.3.2 and 4.1.2)
  • Among the commodity code search results, there are names of chapters that can be selected with keyboard commands as well as with the screen reader, although they shouldn’t be selectable. (WCAG 1.3.1 and 4.1.2)
  • The placeholder value of the drop-down menus is one of the selectable alternatives. (WCAG 1.3.1)
  • Screen readers read menus consisting of a text field and a search result list (e.g. country selection) incorrectly. The role of the menus has not been programmatically marked correctly. (WCAG 4.1.2)
  • Some of the drop-down menus have been programmatically marked using an incorrect role. (WCAG 4.1.2)
  • An inaccessible calendar menu opens automatically when focus moves to date fields, and it can’t be closed without moving away from the field. Some of these fields incorrectly tell screen reader users to select the date from the calendar menu. (WCAG 1.4.13)
  • The field values are often checked first when the user moves away from the field. This leads to situations where a field that has been filled in correctly may still be shown as incorrect or the user doesn’t know how to proceed. (WCAG 3.3.1 and 4.1.2)

Structure

 

  • There are flaws in the use of the programmatic heading levels. Heading levels have been skipped and there are several H1 level headings. (WCAG 1.3.1)
  • The main heading of every page is simply the name of the service. The headings don’t indicate the contents of the individual pages, and screen reader users can’t skip directly to the main content. (WCAG 1.3.1)
  • The table structure used for uploading and presenting attachments is complicated, especially for screen reader users. (WCAG 1.3.1 and 4.1.2)
  • There are flaws in the structure of the left side navigation. The side navigation has been created using buttons instead of links, and the navigation menu landmark is only read in English. (WCAG 1.3.1)
  • The form controls at the bottom of the page are not contained in any landmark. (WCAG 1.3.1)
  • There are some flaws in the programmatic structure of the start page tab structure. (WCAG 4.1.2)
  • In the code, the declaration menu is not directly after the button that opens it, and it may be difficult to access the menu content when using the keyboard. (WCAG 2.4.3)
  • The first object to which the keyboard focus moves is the HTML element that corresponds to the whole page instead of the first object of the page. (WCAG 2.4.3 and 1.3.1)
  • After the visual table structure under Values and prices, there is a partly hidden table structure which may cause problems when assistive technology is used. (WCAG 1.3.1)

Messages and tooltips

  • The error messages are sometimes unclear, and screen readers may read several different error messages one after another, which makes the interpretation even more difficult. (WCAG 3.3.1, 3.3.3 and 4.1.3)
  • On the summary page, the structure of the error table and the error messages are unclear. (WCAG 1.3.1, 3.3.1 and 3.3.3)
  • The screen reader doesn’t automatically read all interface messages. (WCAG 4.1.3)
  • Screen reader users are not notified that they are moving to a new page e.g. when clicking the buttons Next or Previous. Sometimes the focus remains on buttons hidden in the user interface. (WCAG 2.4.3)
  • The title of the service doesn’t change at all when the user moves from one page to another and it doesn’t specify the different declaration types. (WCAG 2.4.2)
  • On the start page, the texts on the sorting buttons for the declaration table don’t explain the functioning of the buttons, and a screen reader user doesn’t receive any information of changes in the sorting. (WCAG 4.1.2 and 4.1.3)
  • The field tooltips are read immediately when focus is moved to the field, and they are the only programmatic labels of the fields. This increases unnecessary noise for screen reader users. When screen reader users click on a tooltip button, they aren’t informed that the tooltip has opened. (WCAG 1.3.1, 4.1.2 and 4.1.3)
  • Several tooltips don’t contain any additional information, they only repeat the field label. (WCAG 3.3.2)

Other

  • The link related to the click function of the table rows is not visually distinguishable as a link and in some cases, it is completely visually hidden. Also, its programmatic name is an unclear character string. (WCAG 1.4.11, 2.4.4 and 4.1.2)
  • The HTML code of the service is partly not compliant with the standards. Some of the role attributes have been used incorrectly. Incorrect code may cause problems when assistive technology is used. (WCAG 4.1.1 and 4.1.2)
  • All text content does not meet the contrast requirements. (WCAG 1.4.3)
  • Keyboard focus is not visible in all user interface components. (WCAG 2.4.7)
  • The input fields don’t meet the contrast requirements when not in focus. (WCAG 1.4.11)
  • There are flaws in the programmatic structure of the logo link, and the link text doesn’t clearly indicate where the link goes. (WCAG 4.1.2 and 2.4.4)
  • The link for notices that goes to an external website has not been marked as such. (WCAG 3.2.2 and 2.4.4)
  • The service doesn’t scale to the highest required zoom levels. Instead, using the service at these levels requires scrolling in two dimensions. (WCAG 1.4.10)

Drafting of the statement

Customs has assessed the accessibility of this service as follows:

  • The assessment was conducted by an external operator.
  • The service was assessed in 11/2020.
  • The statement was drafted on 12 February 2021.
  • The statement was last reviewed on 12 February 2021.

Feedback

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

  • Give feedback on accessibility to Customs by email: asiakaspalautteet@tulli.fi.
  • The Customs Clearance Unit of Finnish Customs is responsible for the accessibility of the Customs Clearance Service and will also respond to feedback on accessibility.
  • We aim to respond to feedback within five working days.
  • If you aren’t satisfied with the response you have received from Customs, you can also give feedback on accessibility to the Regional State Administrative Agencies: saavutettavuus@avi.fi.