Web accessibility statement

This accessibility statement applies to the website nordea.com. The website is subject to the Finnish Act on the Provision of Digital Services, which requires that digital services provided by a credit institution must be accessible. 

This accessibility statement was published on 6 July 2021. The accessibility of the service has been assessed by Inklusio ApS.

Compliance status  

The nordea.com website is partially compliant with the accessibility requirements.  

Non-accessible content  

The website is not yet fully accessible in the following identified areas. The goal is to have the identified gaps fixed during 2021, unless otherwise stated below. The following content and/or functions do not yet meet the accessibility requirements: 

Keyboard navigation

There are situations where it is not clearly visible which element in the content currently has keyboard focus, and content can in some instances be accessed by keyboard even though it is visually hidden.

Specific types of content have interactive elements that are not accessible by keyboard, e.g. additional content in Soundcloud podcasts, and content from Euroland.com.

This relates to the WCAG success criteria 2.1.1 Keyboard and 2.4.7 Focus Visible.

If possible, we recommend using the desktop layout of the website since this version currently works better with keyboard navigation than the layout for smaller screens.

Keyboard trap in expanded content

In expandable content, like sub menus, keyboard navigation will be contained within the expanded content, and it is not possible to use the “Tab” key to get away. The expanded content can easily be closed by with the “Escape” key, and keyboard navigation to the rest of the page can continue.

This is technically not a WCAG 2.1 issue, since “Escape” releases the keyboard focus again.

Menu is not logical to screen reader users

The main navigation has several levels that expands into each other, but to a screen reader, the different levels of the menu are communicated as separate menus. The roles “menu” and “menu bar” are currently used on menus on the website which indicates to a screen reader user that the interaction pattern is like in an application. However, the menus are just lists of links, whereof some are expandable.

This relates to the WCAG success criteria 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.

Color contrast

A few types of text content has too low contrast to the background, especially on image backgrounds, and a few graphics and interactive elements have to low contrast to surrounding colors as well.

This relates to the WCAG success criteria 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.

Text alternatives for images

Not all alternative texts for images and icons are descriptive.

Complex images like graphs and diagrams do in some cases not present equivalent information in an accessible way.

This relates to the WCAG success criteria 1.1.1 Non-Text Content.

Heading structure

The visual heading hierarchy is not always reflected in the code. In a few places, visual headings might not be marked up in a way, that they will be picked up as headings by a screen reader, and sometimes the visual hierarchy and the semantic hierarchy diverges. Empty headings might appear in the code in certain content types. We are working on fixing this, but as long as the headings are completely empty, they will be ignored by screen readers. This relates to the WCAG success criteria 1.3.1 Info and Relationships and 2.4.6 Headings and Labels.


In some tables, the table headers are not marked up correctly as such, which makes it more difficult to make sense of the table when using a screen reader.

This relates to the WCAG success criteria 1.3.1 Info and Relationships.

Non-specific links

Some pages that contain lists of content have “Read more” or “See all” links. We are working on making these links more specific. This relates to the WCAG success criterion 2.4.4 Link purpose (In Context). We are working on making these links more specific. 


Some forms might be missing visible labels, text description of errors, and markup of status messages in a way to make assistive technologies recognize them as such. For input fields that collect information about the user, autocomplete might not be used in all cases where it could potentially help the user fill out form.

This relates to the WCAG success criteria 1.3.5 Identify Input Purpose, 3.3.1 Error Identification, 3.3.2 Labels or Instructions, 3.3.3 Error Suggestion, and 4.1.3 Status Messages.

Missing language definitions on parts of content

The links for choosing different language versions of the website (English, Dansk, Norsk, Suomi, Svenska) will be read out in the language in which the website is currently shown, because they are missing a language attribute to communicate which language they are in. The same applies to e.g. titles of reports in Swedish. This relates to the WCAG success criterion 3.1.2 Language of Parts.


At 400% zoom on a desktop computer, the mobile menu and search functionality currently does not work well. This relates to the WCAG success criterion 1.4.10 Reflow.


Currently there is no transcript or text alternative for our podcasts.

This relates to the WCAG success criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Video content

Video content might lack subtitles, and in some cases also audio descriptions of the visual content in the video.

This relates to the WCAG success criteria 1.2.2 Captions (Prerecorded), 1.2.4 Audio Description or Media Alternative (Prerecorded) and 1.2.5 Audio Description (Prerecorded).

PDF documents

We are currently in the process of making all PDF documents compliant with the accessibility requirements. We have identified gaps relating to PDFs and disclosed them. Our goal is, however, that all PDFs published on our website after 23 September 2018 comply with the accessibility requirements by the end of year 2021. The remaining issues in PDFs are mostly related to 1.1.1 Non-Text Content and 1.3.1 Info and Relationships.  

Content for which we invoke a disproportionate burden 

The current website has recently been released, and we are working on fixing remaining accessibility issues in collaboration with external consultants. 

Content not within the scope of the applicable legislation 

The applicable legislation (the Finnish Act on the Provision of Digital Services (306/2019)) does not apply to the following content, which may not be fully accessible: 

  • Office software files (for example doc, pdf and odt) published before 23 September 2018.
  • Online content archived before 23 September 2019.
  • Video or audio recordings released before 23 September 2020. 

Feedback and contact information 

Accessibility feedback  

Did you find accessibility difficulties on our website? If you did not find an answer in our accessibility statement regarding the website, please send us feedback.   

We have updated and fixed all PDF documents on Nordea.com (uploaded after September 2018). We have used Siteimprove to scan for accessibility issues and then used Adobe Pro DC to solve the issues. If you however still find accessibility issues in uploaded PDFs on Nordea.com please notify us using the webform. We will then fix anything that may still be missing. Give feedback on accessibility    

Supervisory authority  

If you notice accessibility issues with the site, first provide feedback to us, the site administrator. It may take up to two weeks for us to respond. If you are not satisfied with the answer you have received or do not receive a reply at all within two weeks, you can report it to the Regional State Administrative Agency of Southern Finland. The website of the Regional State Administrative Agency of Southern Finland explains in detail how the notification can be made and how the matter is handled.  

Contact details of the supervisory authority    

Regional State Administrative Agency of Southern Finland   Accessibility Control Unit   telephone number exchange 0295 016 000 saavutettavuus [at] avi.fi www.saavutettavuusvaatimukset.fi Opens new window