Accessibility Status for eBank

The service is not yet fully compliant with the accessibility requirements; the following gaps have been identified:

• 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 (content that is not text).
• 1.3.1 Info and Relationships (A): Screen readers and other assistive technologies can miss some relevant information regarding the structure of the content, including headers, pictures, texts, lists or tables, reasoning is that the technical name for fields are not defined properly.
• 1.3.2 Meaningful Sequence (A): Screen readers and keyboard navigation might jump incorrectly through some screens/documents.
• 1.3.4 Orientation (AA): Some screens are locked in Horizontal display mode, while for tablets it will work in both Horizontal and Landscape mode. The user could miss the function.
• 1.3.5 Identify Input Purpose (AA): Automatic fill might not work in some relevant fields; the user will have to enter information manually.
• 1.4.1 Use of Color (A): Use of colour can occur inappropriately, e.g., if visuals are expressed only by colours. People with colour deficiency might struggle capture the information.
• 1.4.10 Reflow (AA): Some pages offer scrolling in two dimensions. This can make it difficult to view and understand displayed content if used.
• 1.4.3 Contrast (Minimum) (AA): Contrast is not sufficient in some instances.
• 1.4.4 Resize Text (AA): Some screens are limited scalable, when a user zooms to 200% or more, some functionality or text might be lost.
• 2.1.1 Keyboard (A): Not all functions can be accessed or executed by using a keyboard.
• 2.4.1 Bypass Blocks (A): The website sometimes lacks mechanisms to bypass repetitive blocks of content, which creates difficulties for users navigating with keyboards or assistive technologies.
• 2.4.2 Page Titled (A): Some screens/documents does not have titles that describe topic or purpose sufficiently.
• 2.4.3 Focus Order (A): Keyboard users might experience the navigation sequence in an illogical order.
• 2.4.5 Multiple Ways (AA): The page does not always offer at least two ways for users to locate it within a set of web pages.
• 2.4.6 Headings and Labels (AA): Not all fields and headings clearly describe the subject or purpose.
• 2.4.7 Focus Visible (AA): Input fields might be missing "outlines", which shows the curser position/ focus.
• 2.5.3 Label in Name (A): The technical name of a field or button sometimes does not match the actual field purpose.
• 3.1.1 Language of Page (A): Screens and documents might lack a correct language setting. Assistive technologies, like screen readers, might not be able to automatically detect the language of the screen/document.
• 3.2.2 On Input (A): In some cases, a new window can pop-up unannounced after filling out a form or when selecting.
• 3.3.1 Error Identification (A): In some cases, errors are not clearly identified and described in text to guide users in correcting them.
• 3.3.2 Labels or Instructions (A): Some input fields can miss a supporting explanation (like date format).
• 3.3.3 Error Suggestion (AA): In some cases, guidance or suggestions for correcting errors in form fields are not provided to assist users in resolving the issues.
• 4.1.2 Name, Role, Value (A): Definitions of fields are sometimes missing correct set-up - which can result in partly missing functionality of assistive technologies.
• 4.1.3 Status Messages (AA): The cursor position/focus might be disconnected to a status messages. The user will have to move the correct field.

Documents

Users may find that PDFs linked to this service are partly compliant. We are working to resolve identified gaps, which may cause screen reader errors, such as incorrect reading order, undefined link purposes, low contrast, and missing alternative text.