Danske Bank Digital Business Services Accessibility Statement

This accessibility statement applies to Danske Bank's services targeted at businesses and was updated on January 15, 2025. The service is subject to the law on the provision of digital services, which requires that online services provided by public sector and financial industry entities be accessible. We have independently evaluated the accessibility of these services.

Accessibility Status of the Services

The services are not yet fully compliant with all requirements and only partially meet the accessibility standards. Some of the services' content and functionalities are not easily readable by screen readers or usable without a mouse. Below is a detailed list of the most significant issues we have identified. If you notice any other accessibility problems in our services, please provide feedback at accessibility@danskebank.dk.

The Auditor Portal meets the accessibility requirements.

Non-Accessible Content:

• 1.1.1 Non-text Content (A): Some images are missing a text option. If so, a screen reader will not be able to explain the image content. As well, the text option can be missing in tables and other non-text content.
• 1.2.2 Captions (Prerecorded) (A): Some videos are missing captions, which will prevent the user from reading.
• 1.3.1 Info and Relationships (A): Screen readers and other assistive technologies can miss out on relevant information about the content structure, including headers, pictures, texts, lists, or tables because the technical names for fields are not defined properly.
• 1.3.2 Meaningful Sequence (A): Screen readers might jump incorrectly through some screens/documents, also affecting keyboard navigation.
• 1.3.5 Identify Input Purpose (AA): Automatic fill does not work in some relevant fields, requiring the user to enter information manually.
• 1.4.1 Use of Colour (A): Use of colour can be inappropriate, e.g., if visuals are expressed only by colours. People with colour deficiency might struggle to capture the information.
• 1.4.10 Reflow (AA): Some pages offer scrolling in two dimensions, making it difficult to view and understand displayed content if used.
• 1.4.11 Non-text Contrast (AA): Some visuals, like buttons, might lack sufficient contrast, making it more difficult to read the content.
• 1.4.13 Content on Hover or Focus (AA): Information text on input fields is not shown when moving the cursor/focus on a field. The user will have to figure out what to enter without any supportive information.
• 1.4.3 Contrast (Minimum) (AA): Contrast is not sufficient in some instances, making it harder for people with sight deficiency to read the content.
• 1.4.4 Resize Text (AA): Some screens are scalable, but when a user zooms to 200%, some functionality or text might be lost. Settings on users' devices will not result in expected outcomes.
• 2.1.1 Keyboard (A): Not all functions can be accessed or executed using a keyboard.
• 2.1.2 No Keyboard Trap (A): Keyboard users might find themselves locked in a field, unable to move back or forth, unless switching to a device like a mouse.
• 2.4.3 Focus Order (A): Keyboard users might experience the navigation sequence in an illogical order.
• 2.4.4 Link Purpose (In Context) (A): Some links can have ambiguous explanations and/or are missing a text alternative used by screen readers. Users can find it difficult to understand exactly where the link leads.
• 2.4.6 Headings and Labels (AA): Not all fields and headings are descriptive enough, which makes it harder to understand.
• 2.4.7 Focus Visible (AA): Input fields might be missing "outlines" that show the cursor’s position/focus. Keyboard users might struggle to find the cursor’s position.
• 2.5.1 Pointer Gestures (A): Not all functionality that can be operated through a motion gesture is operable by user interface components.
• 2.5.3 Label in Name (A): The technical name of a field or button sometimes does not match the actual field purpose, possibly confusing users relying on screen readers.
• 2.5.8 Target Size (Minimum) (AA): Targets for pointer inputs are not spaced sufficiently to ensure ease of use.
• 3.1.1 Language of Page (A): Screens/documents might lack a correct language setting. Assistive technologies, like screen readers, might not automatically detect the language, resulting in less satisfactory read-aloud outcomes.
• 3.1.2 Language of Parts (AA): Screens/documents might lack a correct language setting on parts where language changes from the main part. Assistive technologies might not detect these changes automatically.
• 3.2.2 On Input (A): In some cases, a new window can pop up unannounced after completing a form or making a selection, which can confuse the user.
• 3.3.2 Labels or Instructions (A): Some input fields can lack a supporting explanation (like date format), causing users to struggle with getting the input accepted by the system.
• 4.1.1 Parsing (A): The technical structure behind the screens can fail when using assistive technologies; for example, read aloud might lack information on the count of items in a list, or table column and row headers.
• 4.1.2 Name, Role, Value (A): Definitions of fields are sometimes missing proper setup, leading to partial functionality loss of assistive technologies.
• 4.1.3 Status Messages (AA): The cursor/focus might be disconnected from status messages, requiring the user to move to the correct field.

Non-Accessible Content in Corporate Identification and Document Delivery

• Functionality and links are not fully machine-readable: (WCAG 1.3.1: Information and Relationships, WCAG 2.4.4 Link Purpose (In Context))
• Contrast and text delivery are not always sufficient: (WCAG 1.4.3: Contrast (Minimum), WCAG 1.4.12: Text Spacing)
• Focus order is sometimes illogical, and focus visibility is not always clear: (WCAG 2.4.3: Focus Order, WCAG 2.4.7: Focus Visible)
• Page language is not machine-readable: (WCAG 3.1.1 Page Language, WCAG 3.1.2 Part Language)
• Not all mandatory form fields are marked as required: (WCAG 3.3.2 Labels and Instructions)
• Service HTML code does not fully comply with standards: (WCAG 4.1.1: Parsing)