The accessibility of the Payments service and Reference calculator 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 calculator 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 30 April 2024.
Accessibility status of the digital service
The Payments Service and Reference Calculator do not conform to requirements. Please see below for a list of non-conformities and exceptions applicable to the requirements.
Inaccessible content in the service
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
Accessibility issues in the Reference calculator include problems with keyboard use and tabulator order as well as in error messages and info texts. These issues are listed in more detail below.
Non-accessible content and issues
WCAG 1.1.1 Non-text Content
WCAG 1.3.1 Info and Relationships
WCAG 1.4.3 Contrast (minimum)
WCAG 1.4.11 Non-text Contrast
WCAG 1.4.13 Content on Hover or Focus
WCAG 2.4.3 Focus Order
WCAG 2.4.7 Focus Visible
WCAG 3.3.1 Error Identification
WCAG 3.3.3 Error Suggestion
WCAG 4.1.3 Status Messages
Content which is inaccessible on the basis of disproportionate burden
The application for the Payments service and Reference Calculator are planned for redesign in 2024. For this reason, accessibility changes will not be made for the current application, and any accessibility issues will be corrected when the application is redesigned. The corrections will be carried out 2024.
File transfer service
Inaccessible content in the service
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.These issues are listed in more detail below.
- WCAG 3.3.1 Error Identification
- WCAG 4.1.2 Name, Role, Value