The accessibility of the Payments service, Reference generator and File transfer service has been assessed by accessibility experts working for OP Financial Group on a project basis and by means of self-assessment of web accessibility.
The following systems have been used in the self-assessments:
- Accessibility on desktop computers has been tested using the Chrome web browser and NVDA screen reader software.
- Accessibility on mobile devices has been tested using Apple devices, the Safari web browser (touch gestures).
- Accessibility of the Reference generator has been tested using the Firefox and Safari web browsers. Chrome and IE browsers were also used to check certain details. The WebAIM WAVE browser extension was used to check conformance with criteria. Screen reader software were tested on MacOS using the VoiceOver screen reader and on Windows using the NDVA screen reader.
Provisions on accessibility requirements are specified in the Act on the Provision of Digital Services.
This accessibility statement was created on 11 December 2020 and is last updated on 26th November 2024.
Accessibility status of the digital services
The Payments Service and File transfer service do not conform to requirements.
Reference generator and Exchange rates conforms to requirements.
Payment services inaccessible content
Accessibility issues in the Payments Service include the visible keyboard focus being missing from many elements. This means that the user is not always able to see the position of keyboard focus, and feedback and error messages are inaccessible using a screen reader without moving focus. The service contains sections that cannot be accessed by keyboard users using the tab key. Selection buttons, checkboxes and other interrelated controls are not connected with one another, making them difficult to understand and use with a screen reader. In accordion elements, focus moves automatically to the first available object in the element. In some forms, the tabulator order is unclear and the user may fail to notice skipped content. The table that lists selected payments lacks a descriptive heading. While sighted users can deduce the table’s purpose by looking at its contents, the purpose remains partially unclear for screen reader users. Notifications and warnings are grouped visually into boxes, but the contents of the various messages are not stated in the text or programmatically determined. The number of unapproved payments is presented as only an isolated number, making it potentially difficult to understand for screen reader users. The dialogue box for the payment template includes the option to filter templates. Writing in the text field updates the contents of the table below, but this is not indicated to screen reader users. There are issues in the contrast between the application’s text and the background. These issues are listed in more detail below.
WCAG 1.1.1 Non-text Content
WCAG 1.3.1 Info and Relationships
WCAG 1.3.2 Meaningful Sequence
WCAG 1.3.3 Sensory Characteristics
WCAG 2.1.1 Keyboard
WCAG 2.4.3 Focus Order
WCAG 2.4.7 Focus Visible
WCAG 3.3.2 Labels or Instructions
WCAG 4.1.1 Parsing
WCAG 4.1.2 Name, Role, Value
WCAG 4.1.3 Status Messages
File transfer service inaccessible content
Due to the lack of a file to send, only the inactive Continue button works. The user does not get a textual explanation as to why they cannot proceed. There is some confusion on the service regarding which elements are links and which are buttons, which makes it difficult to understand the logic of the service. The page does not scale sufficiently. The document downloads are represented as link elements. However, due to incomplete implementation, the links do not work with a keyboard, meaning keyboard users cannot open the documents at all. There are several navigation buttons that are disabled by default. These buttons do not provide users with textual guidance on what they need to do to proceed. The user can download files either in electronic format or as a compressed file. However, the selection options appear only after the "Download" button, which is too late for a screen reader user, as they may have already initiated the download by that point. In archive filtering, both fields have the same programmatic label. This can make it particularly difficult for blind users to understand which date should be entered in which field. Screen reader users do not receive feedback after pressing the "Hide filter" button. In the “Send file" view, there are several elements in need of programmatic association. There are deficiencies in focus management. When a user uploads an attachment, the focus returns to the file upload section. However, the screen reader still announces "Loading" even though the file has already been uploaded. The user can mark reply as read. If a screen reader user does this directly from the table, they receive no feedback. In the reply details, there are two headings, which may not be very clear for screen reader users because they are not programmatically marked as headings. These issues are listed in more detail below.
-
WCAG 1.3.1 Info and Relationships
-
WCAG 1.3.2 Meaningful Sequence
-
WCAG 1.4.10 Reflow
-
WCAG 2.1.1 Keyboard
-
WCAG 2.4.3 Focus Order
-
WCAG 2.4.6 Headings and Labels
-
WCAG 2.4.11 Focus Not Obscured
-
WCAG 3.3.1 Error Identification
-
WCAG 4.1.2 Name, Role, Value
-
WCAG 4.1.3 Status Messages