This statement concerns the accessibility of the OP-mobile app. OP-mobile is a mobile application for OP Financial Group companies. OP Financial Group includes OP Cooperative, its group companies (such as OP Corporate Bank Plc, Pohjola Insurance Ltd, OP Life Assurance Company Ltd and OP-Services Ltd), OP Cooperative's member banks, OVY Insurance Ltd, OP-Eläkesäätiö pension foundation, OP Bank Group Pension Fund and other current and future companies, entities and foundations, in which at least one of the above individually or jointly exercise control.
The accessibility of OP-mobile has been assessed by accessibility experts working on a project basis. In addition, continuous self-assessment has been carried out regarding the accessibility of the app.
Accessibility was assessed on an iOS device using the VoiceOver screen reader and on an Android device using the Talkback screen reader.
Provisions on accessibility requirements are specified in the Act on the Provision of Digital Services.
This Accessibility Statement was created on 15 June 2021 and has been updated regularly since then. The statement was last updated on 31 January 2025.
State of accessibility of OP-mobile
Some accessibility issues remain in OP-mobile, and the application does not fully meet the accessibility requirements. Non-compliance with requirements and the applicable exemptions are listed below. If the device where the problem occurred is not specified in the missing section, the problem occurs when using both iOS and Android devices. Accessibility issues are corrected as soon as possible after they are detected.
OP-mobile has several accessible services and sections that can be used with ease. These services and sections include the Homepage, homepage favourites, My transfer, New payment, My financial balance and card views, including card security limits, card transactions and card settings. Additionally, the homepages of the Investments, Loans and Insurance sections are accessible. In the Investments view, the sections for viewing Assets and holdings are also accessible. In the Insurance view, the sections for viewing insurance information, the Filed claims section and the Insurance cards view are also accessible. In addition, the page for selecting the customer role is accessible.
Inaccessible content
General
OP-mobile has certain accessibility issues that are present in several sections of the service. However, OP-mobile also has some shortcomings in terms of overall accessibility and usability, but which do not violate any of the WCAG criteria. Some of the accessibility shortcomings occur on both iOS and Android devices, while others only appear on another platform.
Some of the PDF files that open from the app have accessibility issues. PDF files that open in the app cannot be adequately zoomed without using two fingers. In certain situations on iOS devices, the reading sequence of PDF files is not defined. On Android devices, the screen reader treats the entire content of PDF files as a single object. In addition to these shortcomings, documents created using old technology also contain other accessibility issues. These documents are also available as paper copies, in which case they are accessible.
The OP-mobile user is logged out automatically when the app is not actively used for 5 minutes (timeout specified by the second Payment Services Directive (PSD2)). However, the user is not given prior warning of this.
The app includes features that use embedded content from the OP website (such as Book a meeting, Online messages, Loss reports). These views do not fully meet accessibility requirements or support the accessibility settings offered by the device, such as resizing text, dark theme and increasing text contrast. Screen reader users may have difficulty in identifying when the device switches to the app’s embedded op.fi content.
- WCAG 1.3.1 Info and Relationships
- WCAG 2.2.1 Timing Adjustable
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.4 Resize Text
- WCAG 4.1.3 Status Messages
- EN 11.5.2.5
Activation and login
The accessibility issues listed in the General section of this statement are also present in the Mobile key and when logging in to OP-mobile. Additionally, there are issues that affect a specific group of users. These users do not have an OP user ID, but do have an OP payment card and use Mobile key to confirm card payments made online.
Accessibility issues affecting a specific user group:
- On Android devices, when entering the PIN for Mobile key, the keyboard does not follow the text input method defined in the settings. Additionally, the instructions for entering the PIN are given only after the field.
- On Android devices, when the user selects the customer role, the screen reader does not state the user's role
- Some of the individual text elements contain several paragraphs of text
- Loading animations are not read by the screen reader
- EN 11.5.2.15
- EN 11.6.2
- WCAG 1.3.1 Info and Relationships
- WCAG 1.3.2 Order Affecting Meaning
- WCAG 2.4.3 Focus Order
- WCAG 2.4.7 Focus Visible
- WCAG 4.1.2 Name, Role, Value
Front page
New payment
The following shortcomings apply to Android devices. The required error messages are not shown in all views, and the due date must be selected from a calendar that the screen reader may find difficult to read. Information about a late payments is not programmatically connected to other payment information, which can be confusing for the screen reader’s user. Some of the information is only presented visually. Some of the buttons have accessible names that may be difficult to understand. Not all of the buttons are programmatically defined, or they are defined incorrectly. Mandatory fields are not indicated.
In addition, there are accessibility issues in payment services, which are described in the General section of this statement.
- WCAG 4.1.2 Name, Role, Value
- WCAG 1.3.1 Info and Relationships
- WCAG 3.2.2 Input
- WCAG 4.1.3 Status Messages
- WCAG 2.4.6 Headings and Labels
- WCAG 4.1.2 Name, Role, Value
- WCAG 3.3.2 Labels or Instructions
International payments
The International payments section is almost accessible. The section includes accessibility issues, which are described in the General section of this statement.
Siirto payment
The section for Siirto payments contains accessibility issues that are listed in the General section of this accessibility statement.
The following accessibility observations concern Android devices. When selecting an account, the selected account is presented only visually and not communicated to the screen reader. Additionally, navigation using an external keyboard may be difficult when selecting the account. Error messages are not automatically read by the screen reader. When adding a new phone number, the number of steps and the current step are presented visually and not indicated for screen reader users.
- WCAG 3.2.1 Focus
- WCAG 3.3.1 Error Identification
- WCAG 1.3.1 Info and Relationships
- EN 11.5.2.5
My transfer
Accessibility issues may occur in the service during My transfers. These issues are described in the General section of this statement.
Payments and e-invoices
Accessibility issues appearing in the Payments and e-invoices section are described in the General section of this document.
Accounts and cards
Accounts and cards can only be reordered by dragging and dropping. The Accounts and cards section also has accessibility deficiencies, which are described in the General section of this accessibility statement.
- WCAG 2.5.7 Dragging movements
- WCAG 2.1.1 Keyboard
Account transactions
Account transactions have accessibility issues, which are described in the General section of this accessibility statement.
Salary details
There are usability and general accessibility issues in the source of salary details, but such issues do not constitute WCAG failures. Following selection of the provider of salary details, the view changes to an external service, whose accessibility OP cannot affect.
Card views
The Card views section is almost accessible. The section includes accessibility issues, which are described in the General section of this statement.
Increasing the credit limit
The assessment has only been carried out on an iOS device with a VoiceOver screen reader. In some situations, links are used for navigating between views where buttons should be used. Some elements are completely hidden from assistive devices. At the start of some views, there is an invisible button that has no text, but which can be focused on with a screen reader.
- WCAG 4.1.2 Name, Role, Value
- WCAG 1.3.1 Info and Relationships
- WCAG 1.3.2 Order Affecting Meaning
My finances
Some of the graphs cannot be accessed with a screen reader, or the information in the graphs is read incorrectly or not at all. Some of the buttons are marked as headings despite not being so.
- WCAG 1.3.1 Info and Relationships
- WCAG 4.1.2 Name, Role, Value
- WCAG 1.1.1 Non-text Content
- WCAG 3.2.4 Consistent Identification
My financial balance
There are accessibility deficiencies in the My financial balance section, which are described in the General section of this statement.
Money Box
The Money Box section also has accessibility issues, which are described in the General section of this statement. In both platforms, some of the error messages are not sufficiently descriptive when read by a screen reader.
On iOS devices, field-specific instructions are placed in the same elements with fields and their labels. In addition, the file type is not read on all buttons that open PDF files. The screen reader sometimes fails to read out the sums shown in connection with card payments, or the sums are read out incorrectly. Focus order is incorrect and contains delays in some of the views and situations. Editing the savings target is difficult with a screen reader. Not all information is read correctly by the screen reader. When using dark mode, some of the elements lack sufficient contrast.
On Android devices, accessing dropdown lists and using some elements are difficult with a screen reader. Error messages are not linked to fields programmatically, and fields with errors are not displayed in any other way. In some of the fields, the additional information is not programmatically linked to the respective field. Some elements are missing from the reading sequence, making their content inaccessible to screen reader users. Some of the elements are marked programmatically incorrectly.
- WCAG 4.1.2 Name, Role, Value
- WCAG 2.4.6 Headings and Labels
- WCAG 1.1.1 Non-text Content
- WCAG 1.3.2 Order Affecting Meaning
- WCAG 2.4.3 Focus Order
- WCAG 4.1.3 Status Messages
- WCAG 3.2.1 Focus
- WCAG 1.3.1 Info and Relationships
- WCAG 3.3.1 Error Identification
- WCAG 3.3.3 Error Suggestion
- WCAG 1.4.11 Non-text Contrast
Your company's financial performance
The section has accessibility issues which are described in the General section of this statement.
Invoicing
The views have accessibility issues, which are described in the General section of this statement.
Corporate customer’s accounting records
The accounting records have accessibility issues which are described in the General section of this statement.
Favourites on homepage
The Favourites on homepage section has accessibility issues, which are described in the General section of this statement.
Loans
The Loans section is nearly fully accessible. The screen reader skips some information, such as the loan interest rate graph. Some of the information in the graph is presented by only using a colour that has insufficient contrast. Lists are not programmatically defined. Screen readers may also have difficulties detecting the sums listed on the Loan information page. There are also accessibility issues in Loans, which are described in the General section of this statement. All of the accessibility issues detected in the Loans section are scheduled to be corrected during 2025.
- WCAG 1.3.1 Info and Relationships
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.11 Non-text Contrast
OP Tailored Consumer Credit application path
The application path for Tailored Consumer Credit contains accessibility issues that are listed in the General section of this statement. Mandatory fields are not indicated, and error messages are not always read by screen readers. The icons of some links and files may be misleading, and file buttons do not indicate that they open a file. Long texts are presented as individual elements. Not all features are usable with the keyboard. Some of the elements are marked programmatically incorrectly or not at all. Some buttons lack accessible names.
On Android devices when focused on a field, the screen reader sometimes read a different message than the one shown below the field. In fields that contain instructions, the screen reader order includes two separate objects, the first of which contains only the field itself, not the help text. Focus is not always logical. Some texts that contain several paragraphs are placed inside the same element, making reading them difficult with a screen reader.
On iOS devices, the reader order includes unnecessary images. Loading animations are not read by the screen reader. Additionally, the date selection does not provide feedback to the screen reader, and focus is confusing when selecting dates. Moving keyboard focus from the dialog to the main content can cause issues: focus disappears and the dialog cannot be closed. Some error messages are not read by the screen reader.
- WCAG 1.3.1 Info and Relationships
- WCAG 3.2.4 Consistent Identification
- WCAG 3.3.2 Labels or Instructions
- WCAG 1.3.2 Order Affecting Meaning
- WCAG 3.1.2 Language of Parts
- WCAG 1.1.1 Non-text Content
- WCAG 3.2.2 Input
- WCAG 2.4.3 Focus Order
- WCAG 2.1.1 Keyboard
- WCAG 2.4.11 Focus not obscured (Visible cursor is not hidden)
- WCAG 4.1.2 Name, Role, Value
- EN 11.5.2.15
Investments
Mutual funds and shares
In the case of buy orders (e.g. shares), when transferring to the selection of a portfolio, the screen reader does not receive information about the portfolio selected. A screen reader user only has the audible tap on screen to tell them that the selection occurred. Accessibility issues also occur during list browsing and the cursor’s location may be unclear to the user of the screen reader. In the stock market country list, the number of listed countries is not indicated, which may make reading through the list difficult for screen reader users. On Android devices, when buying a fund, the screen reader first reads the account and its sum before their significance. On iOS devices, some buttons are missing a clear text alternative. There are also accessibility issues in the section, which are described in the General section of this document.
- WCAG 1.3.1 Info and Relationships
- WCAG 4.1.2 Name, Role, Value
- WCAG 1.1.1 Non-text Content
- WCAG 2.4.6 Headings and Labels
Watchlist
The Watchlist section contains accessibility issues that are listed in the General section of this accessibility statement. Additionally, on Android devices when navigating using a screen reader, the menu is positioned last on the page, even as visually it is positioned before the results. Some of the elements lack sufficient contrast. The label for the switch button on the Watchlist page is not programmatically linked to the button.
- EN 11.5.2.5
- WCAG 1.4.11 Non-text Contrast
Assets and holdings
The Assets and holdings section contains accessibility issues that are listed in the General section of this accessibility statement.
Monthly investment
The Monthly investment section contains accessibility issues that are listed in the General section of this accessibility statement.
OP Investment Partner
The accessibility assessment of OP Investment Partner was only carried out on an iOS device with a VoiceOver screen reader. In addition to the following accessibility deficiencies, the Investment Partner section exhibits accessibility issues which are described in the General section of this statement.
In some situations, not all texts and elements are read at all, or they are not read correctly. Axes are read unnecessarily for some charts, but changed text is not read automatically. Some information in charts is displayed by using only colours. Furthermore, the labels on the switch buttons are not read at all; only the status of the switches is given. Row headings are missing from some tables. The programmatic context of download links does not tell you what to download. In addition, at the start of some views, there is a phase path whose definition is unclear.
Dates must be entered with a calendar element, but the calendar button is not in the tab order. At the beginning and end of each view, there are invisible elements in the focus order. If there are several error messages, only the latter error message is read in some situations, while at other times the only feedback for missing information is a passive Accept button.
- WCAG 1.4.1 Use of Colours
- WCAG 2.1.1 Keyboard
- WCAG 3.3.1 Error Identification
- WCAG 1.3.2 Order Affecting Meaning
- WCAG 1.1.1 Non-text Content
- WCAG 4.1.2 Name, Role, Value
- WCAG 1.3.1 Info and Relationships
- WCAG 2.4.4 Link Purpose (In Context)
- WCAG 3.3.2 Labels or Instructions
- WCAG 4.1.3 Status Messages
Insurance
The Insurance section includes several services that use content from the OP website. The accessibility issues present in these services are described in the General section of this statement.
Loss reports
The Loss reports section is not fully accessible in terms of the additional information for reported losses and the features for reporting additional expenses. On Android devices when reporting a loss, the drop-down menus, pop-up windows, buttons and text fields that open are not programmatically descriptive or aligned with their features. On iOS devices when reporting a loss, the section contains an extra button, and the section is difficult for understand for screen reader users.
- WCAG 1.1.1 Non-text Content
- WCAG 4.1.2 Name, Role, Value
Insurance services for corporate customers
The Insurance services section for corporate customers contains accessibility issues that are listed in the General section of this statement.
Other
Customer info
The Customer info section has accessibility issues that are described in the General section of this statement.
Company’s customer info
The Company's customer info section has accessibility issues that are described in the General section of this statement.