Accessibility of Online banking

This section explains how Handelsbanken Luxembourg's online banking service for private customers complies with accessibility legislation.

Found an accessibility issue?

Share your feedback

We are always working to improve the accessibility of our digital services. If you notice any problems that are not mentioned on this page, or if you believe we are not meeting the legal requirements, please let us know so we can address the issue.

Supervision

OSAPS is Luxembourg's surveillance authority for the accessibility of products and services under the Accessibility Act. 

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)

Older framework

We are in the process of replacing an older framework with a more modern one that will improve accessibility and user experience.

Some banking services and functions in the online bank are still not ready and therefore still have a number of accessibility issues.