Accessibility statement: Applying for an EORI number
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 service EORI number.
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.
The accessibility of the service
The accessibility 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 problems with accessibility. The known 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 list will be updated 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.
- Adding and deleting form field rows
- Form field rows are added and deleted dynamically using buttons. This functionality has flaws in the management of focus from both keyboard and screen reader users’ point of view. (WCAG 2.4.3, 4.1.3)
- Anchor links
- The anchor links are presented as simple links whose purpose is not clear from the surrounding context. (WCAG 2.4.4)
- Some of the buttons have been placed in toolbars, which does not necessarily convey a correct idea of the functionalities. (WCAG 4.1.2)
- Skip links
- The skip link, however, does not work on the application page for keyboard users nor screen reader users. (WCAG 2.4.3)
- The titles of various pages of the service are not always descriptive enough. (WCAG 2.4.6)
- Title attributes
- The title attributes of various pages of the service are not always descriptive enough and, consequently, screen reader users do not always get sufficient feedback on the change of the view. (WCAG 2.4.2, 4.1.3)
- Management of focus
- The service has some functionalities after which the focus of a keyboard or screen reader user is not moved to a logical location. (WCAG 2.4.3, 4.1.3)
- Connection timeout
- The user is warned of the connection timeout and is given the opportunity to request additional time. However, for data security reasons the user must be logged out after 12 hours, which means that the accessibility requirements concerning time limits aren’t completely fulfilled. (WCAG 2.2.1)
Customer experience questionnaire
The customer experience questionnaire is answered in a separate Webropol form after logging out from the service. The observations below concern this form. The pages have been assessed by an external party (Eficode, 4/2020) that has not been involved in the design or development of the pages.
Radio buttons for the question “How satisfied are you with the services you used?”
- The radio buttons for each evaluation number give the faulty information ”1/1” to the screen reader, when they should be indicating which evaluation number out of how many alternatives is in question.This makes it more difficult to choose the right number when using a screen reader. In the beginning of the questionnaire, there is informationstating that the assessment scale ranges from 1 to 5.
- The radio buttons are placed on the side in a table, and the settings of the table are read by the screen readerunnecessarily.This may be cause problems for screen reader users.
- In the section “Was there anything particularly good about our performance? Please specify below” the selected elements cause the screen readers to read the headings two times
- The last page of the questionnaire is only visible for a short while before the browser moves the user to a separate page with a compilation of the answers. It is not possible to return to the last page of the questionnaire by using the browser’s back button.
- The buttons Next, Previous and Send tell the screen reader that they are buttons, although they are links. For a screen reader user, this faulty information may cause problems choosing the right button.
- All questionnaires created with Webropol have the automatic heading ”Questionnaire created with Webropol”; Customs cannot change this. Thus, based on the heading, it is impossible to separate this questionnaire from other questionnaires or feedback forms created by Customs. The user must check the form to find out the right heading of the questionnaire.
Customs has assessed the accessibility of this service as follows:
- 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 accessibility of the services is also continuously assessed by self-assessment.
- The statement was last reviewed on 14 November 2022.
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@example.com.
- 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: firstname.lastname@example.org.