Accessibility of the public webpages about Luxembourg

Handelsbanken is responsible for the public website www.handelsbanken.com. 

Here we explain how the webpages about Handelsbanken's services for private customers in Luxembourg comply with accessibility legislation.

How accessible are the webpages about services in Luxembourg?

On this page, we describe how the sections of the website that are covered by the the European Accessibility Act, meet the requirements. 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 public website

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 follow the European standard EN 301 549 v3.2.1, which is aligned with WCAG 2.2 Opens in a new window, levels A and AA. 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 March 2026.

Found an accessibility issue?Contact information

Content that is not accessible

  • For users who are blind
    • Alternative text may sometimes be missing on some images (Provide text alternatives for non-text content – WCAG 1.1.1)
    • Alternatives to audio-only or video-only recordings may be missing (Provide alternatives for audio-only or video-only content – WCAG 1.2.1)
    • Audio descriptions may be missing (Provide audio descriptions or alternatives for video – WCAG 1.2.3, 1.2.5)
    • Some parts of the code may need restructuring to work well with screen readers (Convey structure and relationships in code – WCAG 1.3.1)
    • The reading order of content may not always be logical (Present content in a meaningful order – WCAG 1.3.2)
    • Focus order may not always be consistent or logical (Ensure logical focus order – WCAG 2.4.3)
    • The purpose of some links may not be clear (Use descriptive link text – WCAG 2.4.4)
    • Some headings and labels may not be descriptive enough (Use descriptive headings and labels – WCAG 2.4.6)
    • Contact options such as support, chatbot, or FAQs may not be placed consistently (Provide consistent help – WCAG 3.2.6)
    • You may need to enter the same information more than once during a process (Avoid repeated input – WCAG 3.3.7)
    • Markup for assistive technologies may be incorrect or missing (Ensure compatibility with assistive technologies – WCAG 4.1.2)
    • Status messages may not be clearly conveyed via screen reader (Ensure assistive technologies can present status messages – WCAG 4.1.3)
  • For users with low vision
    • Alternative text may sometimes be missing on some images (Provide text alternatives for all non-text content – WCAG 1.1.1)
    • Alternatives to audio-only or video-only recordings may sometimes be missing (Provide alternatives for audio-only or video-only content – WCAG 1.2.1)
    • Audio descriptions may sometimes be missing (Provide audio descriptions or alternatives for video content – WCAG 1.2.3, 1.2.5)
    • Some parts of the code still need to be restructured to ensure proper screen reader support (Convey information, structure, and relationships in code – WCAG 1.3.1)
    • The reading order of content may sometimes not be meaningful (Present content in a meaningful order – WCAG 1.3.2)
    • The contrast between text and background may sometimes be insufficient (Ensure sufficient contrast between text and background – WCAG 1.4.3)
    • Contrast in certain components and graphics may not be adequate (Ensure sufficient contrast in components and graphics – WCAG 1.4.11)
    • It may not be possible to adjust spacing between characters, lines, paragraphs, and words in some areas (Allow adjustment of spacing between characters, lines, paragraphs, and words – WCAG 1.4.12)
    • Focus order may sometimes be confusing (Ensure a logical focus order – WCAG 2.4.3)
    • The purpose of some links may not be clearly stated (Use clear and descriptive link text – WCAG 2.4.4)
    • Some labels and headings may not be descriptive enough (Use descriptive headings and labels – WCAG 2.4.6)
    • Certain pages may not clearly indicate what is in focus (Make it visible what is currently in focus – WCAG 2.4.7)
    • Some buttons, links, and other clickable areas may not be large enough (Ensure sufficient size for buttons, links, and other interactive elements – WCAG 2.5.8)
    • Markup for assistive technologies may sometimes be incorrect or missing (Ensure components work with assistive technologies – WCAG 4.1.2)
    • Status messages may sometimes be unclear for screen reader users (Ensure assistive technologies can present messages that are not in focus – WCAG 4.1.3)
    • Dark mode settings may not be supported (Respect user preferences such as dark mode – WCAG 11.7)
  • For users with colour vision deficiency
    • The contrast between text and background may sometimes be insufficient (Ensure sufficient contrast between text and background – WCAG 1.4.3)
    • Contrast in certain components and graphics may not be adequate (Ensure sufficient contrast in components and graphics – WCAG 1.4.11)
    • Sometimes the element in focus may be hidden behind another element or placed off-screen (Focus not obscured – WCAG 2.4.11)
    • Status messages may sometimes be unclear for screen reader users (Ensure assistive technologies can present messages that are not in focus – WCAG 4.1.3)
    • Some controls may not be designed in a way that everyone can use them (Design any controls so that everyone can use them – EN 5.5+)
    • Dark mode settings may not be supported (Respect user preferences such as dark mode – EN 11.7)
  • For users who are deaf
    • Alternative text may sometimes be missing on some images (Provide text alternatives for all non-text content – WCAG 1.1.1)
    • Alternatives to audio-only recordings may sometimes be missing (Provide alternatives for audio-only or video-only content – WCAG 1.2.1)
    • Subtitles may sometimes be missing on pre-recorded audio segments (Add captions to recorded audio – WCAG 1.2.2)
    • Sensory cues may sometimes be required (Do not rely solely on sensory characteristics – WCAG 1.3.3)
    • Some labels and headings may not be descriptive enough (Use descriptive headings and labels – WCAG 2.4.6)
    • Status messages may sometimes be unclear, either for screen reader users or visually (Ensure assistive technologies can present messages that are not in focus – WCAG 4.1.3)
  • For users with hearing loss
    • Alternative text may sometimes be missing on some images (Provide text alternatives for all non-text content – WCAG 1.1.1)
    • Alternatives to video-only recordings may sometimes be missing (Provide alternatives for audio-only or video-only content – WCAG 1.2.1)
    • Subtitles may sometimes be missing on pre-recorded audio segments (Add captions to recorded audio – WCAG 1.2.2)
    • Status messages may sometimes be unclear, either for screen reader users or visually (Ensure assistive technologies can present messages that are not in focus – WCAG 4.1.3)
  • For users without speech
    • The purpose of some links may not be clearly stated (Use clear and descriptive link text – WCAG 2.4.4)
    • Some labels and headings may not be descriptive enough in context (Use descriptive headings and labels – WCAG 2.4.6)
    • Certain pages may not clearly indicate what is in focus (Make it visible what is currently in focus – WCAG 2.4.7)
  • For users with limited mobility
    • Content may not always adapt to screen orientation (Ensure content adapts to screen orientation – WCAG 1.3.4)
    • Some functionality may not be usable with a keyboard (All functionality must be operable via keyboard – WCAG 2.1.1)
    • Keyboard focus may sometimes get stuck (No keyboard trap – WCAG 2.1.2)
    • The time allowed to complete a task may sometimes be too short (Allow users to adjust time limits – WCAG 2.2.1)
    • It may not be possible to pause or stop motion (Allow users to pause or stop motion – WCAG 2.2.2)
    • It may not be possible to skip repeated content (Allow users to skip repeated content – WCAG 2.4.1)
    • The page title may not always describe the topic or purpose (Use descriptive page titles – WCAG 2.4.2)
    • Focus order may sometimes be confusing (Ensure a logical focus order – WCAG 2.4.3)
    • The purpose of some links may not be clear (Use clear and descriptive link text – WCAG 2.4.4)
    • Navigation may not be possible in more than one way (Provide multiple ways to navigate – WCAG 2.4.5)
    • Some labels and headings may not be descriptive enough (Use descriptive headings and labels – WCAG 2.4.6)
    • Certain pages may not clearly indicate what is in focus (Make it visible what is currently in focus – WCAG 2.4.7)
    • Sometimes the element in focus may be hidden behind another element or placed off-screen (Focus not obscured – WCAG 2.4.11)
    • No alternatives may be available for complex gestures (Provide alternatives to complex gestures – WCAG 2.5.1)
    • It may not be possible to undo a click (Allow users to undo clicks – WCAG 2.5.2)
    • Button or control labels may not match what is read by screen readers (Ensure visible labels match programmatic names – WCAG 2.5.3)
    • Some buttons, links, and other clickable areas may not be large enough (Ensure sufficient size for buttons, links, and other targets – WCAG 2.5.8)
    • Some headings and labels may not be descriptive enough (Use descriptive headings and labels – WCAG 3.2.1)
    • Input may cause unexpected changes in context (Avoid unexpected changes on input – WCAG 3.2.2)
    • Contact options such as support, chatbot, or FAQs may not be placed consistently (Consistent help – WCAG 3.2.6)
    • You may need to enter the same information more than once during a process (Redundant entry – WCAG 3.3.7)
    • You may need to remember complex passwords to log in (Accessible authentication – WCAG 3.3.8)
    • Markup for assistive technologies may sometimes be incorrect or missing (Ensure components work with assistive technologies – WCAG 4.1.2)
    • Some controls may not be designed in a way that everyone can use them (Design any controls so that everyone can use them – EN 5.5+)
  • For users with reduced mobility
    • Some buttons, links, and other clickable areas may not be large enough (Ensure sufficient size for buttons, links, and other interactive elements – WCAG 2.5.8)
  • For users with cognitive impairments
    • Alternative text may sometimes be missing on some images (Provide text alternatives for all non-text content – WCAG 1.1.1)
    • Alternatives to audio-only or video-only recordings may sometimes be missing (Provide alternatives for audio-only or video-only content – WCAG 1.2.1)
    • Subtitles may sometimes be missing on pre-recorded audio segments (Add captions to recorded audio – WCAG 1.2.2)
    • Audio descriptions may sometimes be missing (Provide audio descriptions or alternatives for video content – WCAG 1.2.3, 1.2.5)
    • Some parts of the code still need to be restructured to ensure proper screen reader support (Convey information, structure, and relationships in code – WCAG 1.3.1)
    • The reading order of content may sometimes not be meaningful (Present content in a meaningful order – WCAG 1.3.2)
    • The contrast between text and background may sometimes be insufficient (Ensure sufficient contrast between text and background – WCAG 1.4.3)
    • Contrast in certain components and graphics may not be adequate (Ensure sufficient contrast in components and graphics – WCAG 1.4.11)
    • It may not be possible to adjust spacing between characters, lines, paragraphs, and words in some areas (Allow adjustment of spacing between characters, lines, paragraphs, and words – WCAG 1.4.12)
    • Focus order may sometimes be confusing (Ensure a logical focus order – WCAG 2.4.3)
    • The purpose of some links may not be clearly stated (Use clear and descriptive link text – WCAG 2.4.4)
    • Some labels and headings may not be descriptive enough (Use descriptive headings and labels – WCAG 2.4.6)
    • Certain pages may not clearly indicate what is in focus (Make it visible what is currently in focus – WCAG 2.4.7)
    • Markup for assistive technologies may sometimes be incorrect or missing (Ensure components work with assistive technologies – WCAG 4.1.2)
    • Status messages may sometimes be unclear, either for screen reader users or visually (Ensure assistive technologies can present messages that are not in focus – WCAG 4.1.3)
    • Dark mode settings may not be supported (Respect user preferences such as dark mode – WCAG 11.7)

Other accessibility issues

PDF documents

PDF documents available in our services and on our public website may have some accessibility issues.

For example, the structure of the document – such as so-called tags – may be missing. These tags are necessary for screen readers to work properly.

This can also affect navigation and may result in some information not being read aloud by a screen reader. One example is missing alternative text for images.

Woman sitting at a table looking at a computer.

Language level

The new law requires that information about banking services must be clear, concrete, and relevant. The language must not exceed level B2 according to the Common European Framework of Reference for Languages (CEFR). This corresponds to an upper-intermediate level of language understanding.

We are aware that some parts of our digital services may currently use language that goes beyond this level. We are continuously working to improve the language in our services to ensure they are accessible to as many people as possible.

An open laptop on a desk. A pair of glasses are lying next to the laptop.