Applying for an EORI number

URL-address: https://asiointi.tulli.fi/asiointipalvelu/forms/eori

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 service, you can also apply for an EORI number by sending an application in pdf format to Customs.

EORI forms

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 on these pages 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.

  • Navigating with the tab key
    • It is not possible to reach all the user interface elements with the tab key (e.g. field tooltips).
  • Insufficient visibility of focus
    • The chosen user interface element is not visible enough, the focus indicator of the elements is too unnoticeable.
  • Headings on the pages
    • The service is a so-called single-page app, so it is difficult for screen reader users to know where they are in the service: by default, screen readers only notice page loads, so without support measures, screen reader users are not told when the app view changes.
  • Text equivalents
    • There are flaws in the text equivalents of visual elements, which means that screen reader users do not receive any information on them.
  • Responses and status details
    • There are system responses (error and success messages) that the screen reader does not detect, at least not without moving the focus.
  • Error messages
    • Error messages displayed in connection with form fields are too vague for a screen reader user to understand which field they concern.
  • Adding and deleting form field rows
    • Form field rows are added and deleted dynamically using the buttons shown in the images. Understanding these fields and their functions can be difficult for screen reader users.
  • Mandatory fields
    • All the fields in the service are by default mandatory, apart from the fields specifically marked as optional. However, the users are not informed of this in the service. Also, the mandatory fields have not been defined for screen reader users.
  • Anchor links
    • The anchor links are presented simply as links without any explanations. A screen reader user may thing they are a list of normal links.
  • Field instructions in text format
    • In some form fields, the instructions are presented in text format, which may be confusing for screen reader users.
  • Page language
    • The language of the pages has not been defined, so the screen reader may pronounce the text on the page according to the rules of a wrong language.
  • Toolbars
    • Buttons have often been placed in the toolbar, which means that the screen reader gets insufficient text to read.
  • Skip links
    • The pages in the service have skip links to skip past the navigation and to the main content. However, the skip links are invisible, so the sighted keyboard users cannot use them.
  • Headings
    • There are flaws in the use of HTML heading levels. For example, the heading levels H2 and H3 are missing from many pages.
  • Contrasts:
    • The contrasts are not sufficient in error messages, in placeholder texts in input fields and in the edges of input fields.
  • Connection timeout
    • The connection to the service times out without warning.
  • Missing information
    • The missing information is presented using a hyphen (”-”). As a rule, screen readers do not read characters like this.
  • Combo boxes
  • The combo boxes in the service have no labels. This means that a screen reader user does not know what each element is used for.

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 assesses 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, 6/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 service for applying for an EORI number 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