Accessibility statement: Applying for a message exchange authorisation


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 our service Applying for a message exchange authorisation, there are other service alternatives. You can call our Business Information, tel. 0295 5202 Mon–Fri 8 am–4 pm, or send email to

You will find more information about other service alternatives and contact details of customs offices with customer service on the page Instructions for other service alternatives.

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.

  • Headings on the pages
    • The Service is a single-page app, which means that any user operating it using a screen reader will find it difficult to pinpoint their location without re-focusing back to the start of new content. Moving the focus to the main heading of the pages functions on the “Applying for a message authorisation” page, but not on the forms pages. (WCAG 2.4.3)
  • 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 operations using a screen reader can be difficult, as compatible fields are not joined programmatically, and the screen reader is offered no feedback on adding or deleting. (WCAG 3.3.1, 4.1.3)
  • 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. (WCAG 1.3.1, 4.1.2)
  • Field instructions in text format
    • In the testing environment URL field, instructions are inside the field in text format. If the user enters a web address in the wrong format without the ”https://” extension, they are displayed the error notification “the format provided is incorrect”. This does not help the user to correct the erroneous entry. (WCAG 3.3.3)
  • Toolbars
    • The forward icons are unnecessarily indicated with a toolbar role, resulting in surprising behaviour on at least some screen readers. (WCAG 4.1.2)
  • Skip link
    • The service pages contain a skip link. However, the link does not function. (WCAG 2.4.1)
  • Headings
    • There are flaws in the use of HTML heading levels. For example, the heading levels H2 and H3 are missing from many pages. (WCAG 1.3.1)
  • 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. (WCAG 1.3.1)
  • Further information
    • The text field for additional information has no label. (WCAG 3.3.2)
  • Disabled “Submit application” button
    • The “Submit application” button is inactive if the user has not checked the check box for accepting the terms of use. This means that users do not receive any error notifications about what they should do to continue filling the form. (WCAG 2.1.1, 3.3.1)
  • Definition of fields connected to each other
    • Fields connected to each other, such as groups of check buttons and check boxes have not been connected to each other programmatically. This makes it more difficult to understand the meaning of the fields. (WCAG 1.3.1, 3.3.2)
  • Scalability
    • All elements are not scaled on a 320 CSS pixel screen, resulting in some content overlaps and in some heading texts and form field tags remaining hidden (WCAG 1.4.10).
  • Empty lines
    • Line breaks have been used in the layout of some pages, and the screen reader reads these lines as “empty”. (WCAG 1.3.1)

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


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

  • HTML
  • 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. 
  • The statement was last reviewed on 2 December 2021.

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:
  • Customs’ e-services are responsible for the accessibility of the service Applying for a message exchange authorisation 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:

Points to consider

Read more