The Import Declaration Service for private persons

URL address: https://asiointi.tulli.fi/asiointipalvelu/import

Finnish Customs is committed to making this service digitally accessible to all its customers. We are continually improving the user experience and we apply the accessibility standards required by law.

Other service alternatives

If you are not able to use the Import Declaration Service for private persons, you can authorise another person 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 declare your goods at any customs office that handles customs clearances. Instructions on other service alternatives on the Customs website. For information on declaring goods and using the service, please contact the customer services, tel. 0295 5206, Mondays to Fridays 8.00–18.00 or the Customs Information Service

The accessibility of the service

The current accessibility standard of the pages:

  • WCAG 2.1, level AA

The current accessibility of the content:

  • For the most part, meets the requirements.

The known problems with accessibility

Users may still encounter some accessibility problems in the service, and we apologise for that. If you notice a problem in the service that is not included in the list below, please contact us.
The list will be updated in the coming months as and when we are able to fix these accessibility problems.

  • Mobile menu
    • The screen reader does not receive any information on whether the menu is open or closed.
    • The keyboard focus does not stay inside the menu.
    • WCAG 2.4.3, 2.4.4., 2.4.7, 4.1.2
  • The contrasts are not sufficient regarding the following:
    • the edges of input fields
    • light grey texts against dark grey and light background, white text on a read button
    • orange buttons of the instruction side navigation against light background
    • WCAG 1.4.3, 1.4.11
  • Combinations of form fields
    • All form fields have not been programmatically connected to each other.
    • Some form fields have no labels.
    • The button with the question mark is between fields in the navigation order.
    • WCAG 1.3.1, 2.4.3, 3.3.2
  • The field-specific error messages have been linked to wrong fields.
    • WCAG 3.3.1, 4.1.3
  • The screen reader will not get any information on error messages when one clicks “Next”.
    • WCAG 3.3.1, 4.1.3
  • The error messages are not entirely consistent.
    • WCAG 3.3.3
  • HTML heading levels
    • On some pages, the different heading levels are not used systematically. For example, the headings on level H1 levels are missing from many pages, and on some pages the headings skip over levels H2 and H3 to level H4.
    • WCAG 1.3.1
  • All elements don’t have a visual keyboard focus indicator (varies between browsers).
    • WCAG 1.4.1, 2.4.7
  • All pages have the same title element (“Customs e-service”).
    • Site history cannot be used.
    • WCAG 2.4.2
  • The screen reader doesn’t receive any information on movement from one page to another.
    • WCAG 2.4.3
  • Feedback on uploading of data and loading animations cannot be detected with a screen reader.
    • WCAG 4.1.3
  • Text equivalents of visual elements
    • For example, the text equivalent of field tooltip buttons is often “undefined ohje”.
    • WCAG 1.1.1.
  • The links opening in a new window have been determined visually but not programmatically.
    • WCAG 2.4.4
  • The messages at the top of the page are unclear to the screen reader.
    • For example, these messages have been created with an alert attribute, which means that the screen reader starts to read them as soon as they appear and interrupt whatever the user is doing.
    • WCAG 4.1.3
  • The decision documents in pdf format created by the system are not accessible.
    • WCAG 1.1.1., 1.3.1, 1.3.2
  • Connection timeout without warning
    • WCAG 2.2.1
  • The language version links have no language definitions.
    • WCAG 3.1.2
  • Side navigation
    • The side navigations are link lists, but they have not been programmatically determined as side navigations.
    • The screen reader doesn’t receive any information on which stage of the side navigation has been chosen.
    • WCAG 1.3.1, 2.4.4, 4.1.2
  • The button “Add to declaration basket” is inactive when the form has errors or flaws.
    • The screen reader doesn’t receive any information on the inactive button.
    • WCAG 2.1.1, 3.3.3.
  • The goods search “Find the type of goods”
    • There are flaws in the role, name and status definitions of the goods search as well as in movements with the keyboard.
    • If there are no search results, the error message is not accessible.
    • WCAG 2.1.1, 3.2.2, 4.1.2, 4.1.3
  • Date fields in the service
    • The dates cannot be entered manually, they must be chosen in the calendar element.
  • Calendar element
    • The element is not accessible with arrow keys.
    • The element cannot be closed without movement of focus.
    • The screen reader doesn’t read the labels of the date fields.
    • WCAG 1.1.1, 1.4.13, 2.1.1, 2.4.3, 2.4.4, 2.4.7, 3.2.2, 3.3.2
  • The mandatory fields have not been determined, because all fields are mandatory in principle.
    • WCAG 3.3.2.
  • There are flaws in the ARIA attributes of the help text dialogs, and the help text button can only be activated using the space key.
    • WCAG 1.3.2, 2.4.3, 4.1.2
  • The error messages disappear within 20 seconds, and there is no way to extend that time.
    • WCAG 2.2.1
  • The field “Commodity code”
    • When the user starts entering the commodity code in the search field, the service starts searching for results, which keeps changing the page content, but the screen reader doesn’t receive any information on the changes.
    • The calculator in the field heading keeps changing as the user starts entering the digits of the commodity code, but the screen reader doesn’t receive any information on the changes.
    • WCAG 3.2.2, 4.1.3
  • The heading (“Reference number”) of the page with declaration details is unclear.
    • WCAG 2.4.6
  • Messages sent by the customs clearance team
    • The accordion elements used in the messages don’t tell the screen reader whether the element is open or closed. (WCAG 4.1.2)
    • The keyboard focus does not stay in the element. (WCAG 2.4.3)
    • The keyboard focus does not stay in the dialog. (WCAG 2.4.3)
    • The user may unnecessarily aim a keyboard command at the dark background of the element. The screen reader doesn’t receive any information on the purpose of the element. (WCAG 2.4.3)
    • In mobile size, the element covers the “Next” button. (WCAG 1.4.10)
  • The page “Awaiting additional information from you”
    • The button “Upload the attachment here” cannot be used with keyboard commands. (WCAG 2.1.1)
    • The label of the drop-down menu “Attachment type” has not been marked up accessibly. (WCAG 4.1.2)
    • The screen reader doesn’t automatically read notifications warning the user that the file type of the attachment is invalid. (WCAG 3.3.1, 4.1.3)
    • It is difficult to detect inactive buttons with the screen reader. (WCAG 1.3.1, 3.3.1)
    • The role and status of the accordion element “You may enter additional information” are not programmatically determined. (WCAG 4.1.2)
    • When an attachment has been added, the keyboard focus stays in the body element. (WCAG 2.4.3)
  • The instructions concerning the dialog “Are you sure you want to cancel?” are unclear, and it is difficult to understand the difference between the buttons.
    • WCAG 3.3.2

Compatibility with browsers and assisting technologies

The pages are designed to be compatible with the following browsers:

  • Firefox & Chrome

The pages are designed to be compatible with the following assisting technologies:

  • NVDA screen reader 2019.1.1
  • WebAIM Color Contrast checker

Technologies

The accessibility of these pages depends on the functioning of the following technologies:

  • HTML
  • WAI-ARIA
  • CSS
  • Javascript

Assessment methods

Customs has assessed the accessibility of these pages with the following methods:

  • Self-assessment: the company or the organisation has assessed the pages internally.
  • External assessment: the pages have been assessed by an external party (Eficode, 11/2019) that has not been involved in the design or development of the pages.

Feedback process

We are happy to receive feedback on the accessibility of these pages You can contact us in the following ways:

  • Give feedback on accessibility: [email protected].
  • Customs’ e-services are responsible for the accessibility of the Import Declaration Service for private persons and will also respond to feedback on accessibility.
  • We aim to respond to feedback within five working days.
  • If you are not satisfied with the response you have received from Customs, you can also give feedback on accessibility to the Regional State Administrative Agencies: [email protected].

We want to improve our website together with our customers. You can give us feedback by clicking “Send feedback”.

Send feedback