This statement concerns the accessibility of the Pivo mobile app. The Pivo app is provided by Pivo Wallet Oy, part of OP Financial Group. Pivo was removed from use on 4 September 2024. The app can no longer be used or updated.
The accessibility statement contains only the provisions on payments provided by Retail Banking to which the Act on the Provision of Digital Services is applied.
The accessibility of Pivo 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:
- The mobile device accessibility was tested on an iPhone with a VoiceOver screen reader, and on an Android phone with a TalkBack screen reader.
Digital accessibility is regulated by the Finnish Act on the Provision of Digital Services.
This accessibility statement was created on 9 June 2021 and last updated on 5 September 2024.
Accessibility of the digital service
There are issues with the accessibility of the Pivo application, and it does not fulfil all the requirements.
Non-accessible content
Both application versions (iOS and Android) have issues with accessibility, such as:
- Some buttons, elements, text fields and headings have not been defined correctly or they lack a text alternative, making the screen reader unable to recognise them properly.
- The application’s colour contrasts do not fulfil accessibility requirements.
- Focus does not automatically move to the dialogue opening over a view, making it significantly harder to use the app with a screen reader.
- Focus does not always move to the correct spot when the view is refreshed, or it skips elements when browsing a page. This makes it harder to use a screen reader.
- Some views are not scaled properly when using 200% text enlargement on a phone. Such views include the confirmation dialogue for different functions that opens at the top part of the application, in which the buttons are hidden by other content when enlarged. Some of the content does not become larger even with the setting enabled on the phone.
The detected accessibility issues will be fixed in the upcoming application updates. These issues are listed in more detail below.
1.1 Text alternatives
WCAG 1.1.1 – Non-text Content (iOS, Android)
- The types of payment transactions are presented with icons that have no text alternatives.
- There is no feedback on adding a cost picture, and the picture cannot be detected with a screen reader.
1.3 Adaptable
WCAG 1.3.1– Info and Relationships (iOS, Android)
- The headings have not been programmatically determined.
WCAG 1.3.2 Order affecting meaning (iOS, Android)
- In some views (such as supplementary payment information), the focus does not proceed in a logical order.
WCAG 1.3.4 – Position (iOS, Android)
- The application can only be used in a vertical position.
1.4 Distinguishable
WCAG 1.4.4 – Resize Text (iOS, Android)
- The application does not fully follow the text enlargement determined in the phone’s settings.
- In some parts, increasing the font size by 200% will hide so much text that it will be harder to use the app.
2.2 Enough time
WCAG 2.2.1 – Timing Adjustable (iOS, Android)
- The user is logged out automatically after they have not used the application for a set period of time. There is no advance notification of the automatic sign out.
2.4 Navigable
WCAG 2.4.3 – Focus Order (iOS, Android)
- Focus does not automatically move to different dialogue windows.
- In some views, the focus does not proceed in a logical order, skipping some fields.
3.2 Predictable
WCAG 3.2.2 – Input (iOS, Android)
- When announcing a cost’s sum, the focus jumps back to the sum field after entering or deleting any number, which hampers the use of a screen reader.
- The keyboard does not follow the phone’s text input settings with a screen reader.
3.3 Input assistance
WCAG 3.3.2 – Labels or Instructions (iOS)
- Some fields have no programmatic labels.
4.1 Compatible
WCAG 4.1.2 – Name, Role, Value (iOS, Android)
- The application contains buttons that have not been defined as such.
- Some buttons have no accessible name, so the screen reader is unable to determine what they do.
- The expansion element in the Services section has no accessible name, and its role has not been determined programmatically.
- Some elements have no headings that are necessary for the screen reader, making it difficult to interpret the element’s content.
Issues with the EN standard
EN standard C.11.5.2.15
EN standard C.11.6.2
Content that is not within the scope of digital accessibility standards
The accessibility statement contains only the provisions on payments provided by Retail Banking to which the Act on the Provision of Digital Services is applied.