This description concerns the identification and Manage user ID functions in OP Financial Group’s services. These services are common to both OP cooperative banks and OP Corporate Bank. Their accessibility has been evaluated on a project-specific basis by experts working for OP. Digital accessibility is regulated by the Finnish Act on the Provision of Digital Services.
This accessibility statement was created on 30 November 2024 and updatet 27.5.2024
Inaccessible content and functions in the service
Logging into the op.fi service
Providing a further confirmation number
- WCAG 1.1.1 Non-text Content
- WCAG 1.3.2 Order affecting meaning
- WCAG 1.3.5 Identify Input Purpose
- WCAG 3.3.1 Error identification
- WCAG 3.3.2 Labels or Instructions
- WCAG 4.1.3 Status Messages
Selecting customer role
This is an accessibility statement related to customer role selection for private and corporate customers at op.fi. Customer role selection fully meets the accessibility requirements and customers are able to use the service. However, the service has several accessibility issues that are described below. The search function for the corporate customer role does not inform the user, via screen reader, that the search result listing is changing. Setting up a default customer role is unavailable when 400% enlargement with a narrow page width is in use. When using a screen reader, the user cannot directly navigate to the content with a separate link. The name and role of all interface components cannot be programmatically determined
- WCAG 3.2.2 Input (Level A)
- WCAG 1.4.10 Reflow (Level AA)
- WCAG 2.4.1 Bypass Blocks (Level A)
- WCAG 4.1.2 Name, Role, Value (Level A)
Content that is not within the scope of digital accessibility standards
Customers can use Mobile key or a key code list to obtain the code required for identification and logging in. Mobile key is one of OP’s mobile applications. Accessibility observations related to it can be found in the mobile application accessibility statements.
Manage your user ID
Private customer’s user ID
Accessibility issues affect the functions for requesting and changing key code lists, changing a password and deactivating user IDs. Among other issues, the functionalities in the Security section in My profile have insufficient colour contrasts, and the functionalities do not yet fully support the use of assistive technologies such as screen readers or keyboard use. The website also lacks, for example, text alternatives for elements.
Replace key code list:
- 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 2.1.1 Keyboard
- WCAG 2.4.3 Focus Order
- WCAG 2.4.4 Link Purpose (In Context)
- WCAG 3.3.2 Labels or Instructions
- WCAG 4.1.2 Name, Role, Value
Request key code list:
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.4.4 Link Purpose (In Context)
Deactivate key code list:
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.4.4 Link Purpose (In Context)
- WCAG 4.1.3 Status Messages
Change password:
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.4.4 Link Purpose (In Context)
- WCAG 3.3.2 Labels or Instructions
- WCAG 4.1.3 Status Messages
Deactivate user IDs:
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
OP Corporate User ID
The Manage user ID page in op.fi meets the requirements in part. Three accessibility issues were observed during the review. One of the issues was classified as major or critical in severity, concerning difficulty in using a feature alongside assistive technology such as a screen reader. The accessibility observations concerned keyboard focus (WCAG 2.4.7), contrasts (WCAG 1.4.3) and headings (WCAG 1.3.1). Accessibility issues that would be a disproportionate burden to fix. Services for corporate customers logged into the service include content whose modification would cause a disproportionate burden. These deficiencies are listed in more detail below.
Replacing the key code list
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.1.1 Keyboard
- WCAG 2.4.3 Focus Order
- WCAG 2.4.4 Link Purpose (In Context)
- WCAG 3.3.2 Labels or Instructions
- WCAG 4.1.2 Name, Role, Value
Changing of password
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.4.4 Link Purpose (In Context)
- WCAG 3.3.2 Labels or Instructions
Ordering a new key code list
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.4.4 Link Purpose (In Context)
Deactivating user IDs
- WCAG 1.1.1 Non-text Content
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.4.4 Link Purpose (In Context)
Checking and indicating number for further confirmation
- WCAG 1.1.1 Non-text Content
- WCAG 1.3.5 Identify Input Purpose
- WCAG 1.4.3 Contrast (minimum)
- WCAG 1.4.11 Non-text Contrast
- WCAG 2.4.4 Link Purpose (In Context)
- WCAG 3.3.2 Labels or Instructions
My devices and Mobile key
- WCAG 1.3.1 Info and Relationships
- WCAG 1.3.2 Order affecting meaning
- WCAG 1.4.3 Contrast (minimum)
- WCAG 2.1.1 Keyboard
- WCAG 2.4.3 Focus Order
- WCAG 2.4.7 Focus Visible
- WCAG 4.1.2 Name, Role, Value