Accessibility of Luxembourg's Online banking

Handelsbanken is responsible for Luxembourg's logged-in online banking service for private customers.  

Here we explain how the service complies with accessibility legislation.

How accessible is the online banking service?

On this page, we describe how the online bank meets the requirements of the European Accessibility Act. We also explain any known accessibility issues and how you can report them to us if you encounter other problems, so that we can fix them.

How we have tested the online banking service

To ensure our digital services are accessible to everyone, we use both automated tests and manual checks.

Manual checks are carried out by experts using a checklist based on standards and guidelines relevant to the new law. We aim to follow all relevant requirements in the European standard EN 301 549 v3.2.1, as well as additional requirements at level A and AA found in WCAG 2.2 Opens in a new window. Another requirement is that we use clear and understandable language when describing our banking services.

Our experts check things like code quality, keyboard navigation, contrast, zoom, and text size. We also test with screen readers to understand how the services work for users with visual impairments.

Latest Assessment

The most recent assessment was carried out before 28 June 2025.

This statement was last updated on 27 June 2025.

Content that is not accessible

Technical Framework

Luxembourg's online banking service is currently built using an older framework that does not meet accessibility requirements. It will be replaced with a new framework that is fully accessible.

For parts of the service, the following accessibility issues may exist.

  • Alternative text may sometimes be missing on some images (Describe all non-text content – WCAG 1.1.1)
  • Code structure may need improvement for screen reader compatibility (Convey structure and relationships in code – WCAG 1.3.1)
  • Reading order may not always be logical (Present content in a meaningful order – WCAG 1.3.2)
  • Layout may break when zooming (Create responsive layout – WCAG 1.4.10)
  • Contrast in components and graphics may be insufficient (Ensure contrast in UI elements – WCAG 1.4.11)
  • Some functionality may not be keyboard accessible (Ensure keyboard accessibility – WCAG 2.1.1)
  • Time limits may be too short (Allow adjustment of time limits – WCAG 2.2.1)
  • Focus order may be inconsistent (Ensure logical focus order – WCAG 2.4.3)
  • Navigation may be limited to one method (Provide multiple navigation methods – WCAG 2.4.5)
  • Headings and labels may sometimes be unclear (Use descriptive headings and labels – WCAG 2.4.6)
  • Focus visibility may be unclear (Ensure visible focus – WCAG 2.4.7)
  • Clickable areas may be too small (Ensure sufficient target size – WCAG 2.5.8)
  • Language attributes may be incorrect (Indicate language changes in code – WCAG 3.1.2)
  • Component naming may be inconsistent (Use consistent naming – WCAG 3.2.4)
  • Markup for assistive technologies may be missing or incorrect (Ensure compatibility with assistive technologies – WCAG 4.1.2)
  • Status messages may not be clearly conveyed (Ensure assistive technologies can present status messages – WCAG 4.1.3)
  • Dark mode may not be supported (Respect user settings like dark mode – WCAG 11.7)