Accessibility statement: Authorisation 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 Authorisation Service https://asiointi.tulli.fi/asiointipalvelu/permits.

Other service alternatives

If you cannot use the Authorisation Service, you can contact the Authorisation Centre by email, [email protected], or by post, Customs’ Authorisation Centre, PO Box 56, 90401 Oulu.

You can find the application forms for authorisations on the Customs website. For advice in matters involving authorisations, you can contact our Business Information by email or by telephone 0295 5202.

The accessibility of the service

The current accessibility of the content of the service: 

  • WCAG 2.1, level AA
  • For the most part, meets the requirements.

The known problems with accessibility in the Authorisation Service

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:

Moving to another page 

  • The service has been created with single page application technology, where focus moves to the main heading of the page when the user moves to another page. The service has, however, some individual pages where focus moves to the main heading but the screen reader does not read the main headings. (WCAG 2.4.3)

Calendar element of the date

  • The calendar element is the only possible way to enter the date in the date fields. The element is automatically displayed when the user moves the cursor to the date field.
  • Keyboard focus moves suddenly from selection of month and year directly to the day that corresponds to the current day. (WCAG 3.2.2) 
  • The element covers part of the content, and it cannot be closed using keyboard commands. (WCAG 1.4.13)
  • The labels of month arrows are only in English. (WCAG 4.1.2)

Connection timeout 

  • If the service has not been used for a certain period of time, the connection times out without warning. (WCAG 2.2.1)

Modal windows 

  • There may be problems with movement of focus to individual modal windows, when windows are opened. (WCAG 2.4.3)
  • Moving focus to the first incorrect field does not work in modal windows. This means that screen reader users do not get any feedback if they e.g. have left a field empty. (WCAG 4.1.3)

Headings 

  • There are flaws in the use of HTML heading levels. For example, on pages with subheadings, the headings skip entirely over the heading level H3. (WCAG 1.3.1)

Tabs 

  • The tabs have been marked programmatically incorrectly, which is why the screen reader cannot read the number of tabs. (WCAG 4.1.2)

Tables 

  • There are problems with the heading cells in tables, which is why a screen reader does not get any information about them when browsing cells in a table. (WCAG 1.3.1)
  • The tables do not have any programmatic headings that would indicate what information the tables show. (WCAG 1.3.1)
  • The table rows do not have individual anchor elements. Instead, all cells in a row have been programmatically determined as buttons. (WCAG 1.3.1, 4.1.2)
  • Sorting of tables according to headings in descending or ascending order is not programmatically indicated. (WCAG 4.1.2 and 4.1.3)

Side navigation 

  • The side navigation is presented as links and not as stages, so its purpose is not clear for a screen reader user. (WCAG 1.3.1, 4.1.2)
  • In the different stages it is not indicated which stage has been chosen. (WCAG 1.3.1, 4.1.2)

Contrasts 

  • The contrasts are not sufficient in error messages, in placeholder texts in input fields and in the edges of input fields. (WCAG 1.4.3, 1.4.11)

Expandable sections 

  • In the expandable section (“The person in charge of the applicant company or who exercises control over its management”), there are problems with the accordion menu structure. The accordions can be opened with keyboard commands, but they open and close also with focus, which makes it difficult to use the entity. (WCAG 2.1.1)

Multiple-choice fields

  • Some multiple-choice fields may have no labels, which makes it more difficult to understand their content when the service is used with a screen reader. (WCAG 3.3.2)
  • The choices for the multiple-choice fields are displayed under the fields, but the screen reader does not get any feedback on the choices. (WCAG 4.1.2, 4.1.3)
  • The label for the button used for deleting a choice does not indicate what the button deletes. (WCAG 2.4.4)

Definition of fields connected to each other 

  • Fields connected to each other, such as groups of check buttons or first-stage address data fields, have not been connected to each other programmatically, which makes it  difficult for the screen reader to perceive them as connected. (WCAG 1.3.1)

Missing information 

  • Information not completed by the customer is presented using two hyphens (”--”), which the screen reader may not read. (WCAG 1.3.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.

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, 4/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]
  • The Authorisation Centre is responsible for the accessibility of the Authorisation Service 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]