This statement concerns the accessibility of the Payments service at op.fi. The service is part of op.fi, which is the website for OP Financial Group companies.
Accessibility observations concerning file transfers can be found in the file transfer accessibility statement.
Accessibility observations concerning the SEPA direct debit permission are available in the SEPA direct debit accessibility statement.
The accessibility of the Payments 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).
The provisions on accessibility are included in the Act on the Provision of Digital Services.
This accessibility statement was drawn up on 11 December 2020 and last updated on 22 January 2024.
Accessibility of the digital service
The Payments service at op.fi meets the requirements in part. The consent to SEPA direct debit meets the requirements in all respects. The service 'Transfer to own account' meets the requirements in all respects.
You can make payments through the OP Accessible online service, which meets the accessibility requirements.
Inaccessible content in the service
New payment, Payment templates, Unconfirmed payments and Confirmed payments meet the requirements in part. The pages indicated above include the following accessibility issues: page colour contrasts do not meet accessibility requirements, the pages do not fully support the use of assisting technologies, such as screen readers, and there are problems in reading their content when using assisting technologies. Page accessibility issues are listed in more detail below.
The issues are currently being fixed and the statement will be updated as the fixes are completed.
New payment, Payment templates, Unconfirmed payments, Confirmed payments
1.1.1 Non-text Content
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.3.3 Sensory Characteristics
1.3.5 Identify Input Purpose
1.4.1 Use of Colour
1.4.3 Contrast (minimum)
1.4.4 Resize Text
1.4.10 Reflow
1.4.11 Non-text Contrast
1.4.12 Text Spacing
1.4.13 Content on Hover or Focus
2.1.1 Keyboard
2.1.2 No Keyboard Trap
2.1.4 Character Key Shortcuts
2.2.1 Timing Adjustable
2.4.1 Bypass Blocks
2.4.2 Page Titles
2.4.3 Focus Order
2.4.4 Link Purpose (In Context)
2.4.5 Multiple Ways
2.4.6 Headings and Labels
2.4.7 Focus Visible
2.5.1 Pointer Gestures
2.5.2 Pointer Cancellation
2.5.3 Label in Name
2.5.4 Motion Actuation
3.1.1 Page Language
3.1.2 Language of Parts
3.2.1 Focus
3.2.2 Input
3.2.3 Consistent Navigation
3.2.4 Consistent Identification
3.3.1 Error Identification
3.3.2 Labels or Instructions
3.3.3 Error Suggestion
3.3.4 Error Prevention (Legal, Financial, Data)
4.1.1 Parsing
4.1.2 Name, Role, Value
4.1.3 Status Messages
Accessibility of the e-invoicing service
The e-invoicing service meets the requirements in part. The service has multiple separate functions:
- Manage e-invoices, fully accessible
- Order e-invoices, fully accessible
- Change direct payment into e-invoice, fully accessible
- Proposed e-invoices, fully accessible
- Arrived e-invoices, fully accessible
- Original invoice and invoice itemisation, partly accessible
Function-specific requirements are discussed in more detail below.
Non-accessible content
In the e-invoicing service, the image of the original invoice is provided by the invoicer. As such, OP cannot ensure that the image of the original invoice meets accessibility requirements. The invoice specification is based on the commonly used Finvoice standard. The invoicer provides the content of the invoice. The invoice specification is not entirely accessible.
Accessibility issues in the application slow down or disrupt use, in some cases preventing it entirely for users who use assistive technology such as a screen reader. These issues are listed in more detail below.
- WCAG 1.3.1 Info and Relationships
- WCAG 1.3.2 Order affecting meaning
- WCAG 1.4.1 Use of Colours
- WCAG 1.4.4 Resize Text
- WCAG 1.4.10 Reflow
- WCAG 1.4.12 Text Spacing
- WCAG 2.1.1 Keyboard
- WCAG 2.4.3 Focus Order
- WCAG 2.4.4 Link Purpose
- WCAG 2.4.6 Headings and Labels
- WCAG 2.4.7 Focus Visible
Accessibility issues that would be a disproportionate burden to fix
For many invoicers, the contents of the invoice specification are not accessible because there is no way to create a separate summary template for each invoicer, and such templates would also be impossible to manage.
Content that is not within the scope of digital accessibility standards
The original invoice sent by the payee, the accessibility of which is the responsibility of the payee.
State of accessibility of the service for redeeming a money transfer
The service for redeeming a money transfer partly meets the requirements. Non-compliance with the requirements and the applicable exemptions are listed below.
Non-accessible content
Accessibility issues in the application slow down or disrupt use, in some cases preventing it entirely for users who use assistive technology such as a screen reader. These issues are listed in more detail below.
The level H1 main heading, Redeeming a money transfer, is imported from another system/environment. In general, the colours and contrasts of icons, button texts and other graphic objects do not meet accessibility requirements.
Keyboard users have problems navigating the service – for example, when moving forwards or backwards from the Input field.
Redeeming a money order/money transfer is also possible via the telephone service and at bank branches.
Accessibility issues:
1.4.1 Use of Colour
1.4.3 Contrast (icon and button text colour contrast)
2.1.1 Keyboard (cannot be used to move back from the Input field, for example)
2.4.3 Focus Order
2.4.7 Focus Visible