The user can access the OP API Admin site at address https://valtuutus.op.fi/corporate-api-admin/. OP API solutions for Corporate Banking and OP API Admin website are provided by OP cooperative banks and OP Corporate Bank. The provisions on accessibility are included in the Act on the Provision of Digital Services.
This accessibility statement was created on 22 December 2020.
Accessibility of the digital service
The OP API Admin site does not meet all accessibility requirements. However, the identified issues do not prevent using the service for its primary purpose of managing OP API solutions for Corporate Banking related contracts and managing user permissions to the OP API Admin site. Accessibility issues in the service include the following: the site’s colour contrasts do not fully meet accessibility requirements, the site is not fully compatible with all assistive technology, such as screen readers, and there are issues in keyboard use. These issues will be corrected approximately by the end of 2021.
Website accessibility has been assessed by accessibility experts working for OP on a project basis.
Non-accessible content in the digital service (based on WCAG criteria)
Non-accessible content and issues
WCAG 1.1.1, 3.3.2 General, text labels, name tags and instructions: Issues with icon and image descriptions and their translations. Issues with form field name tags and instructions. Alternative texts for calendar and closing buttons are missing. Radio buttons and radio button groups are missing name tags and they don’t include programmatic instructions.
WCAG 4.1.2 General, attention callout boxes, links: The attention callout box on the front page is read each time when it’s visible. Most page links have been implemented as event handlers instead of native HTML links, which prevents most screen readers from working.
WCAG 1.4.4, 2.4.3 General, text size increase, focusing to working area and elements: When increasing the text size to 200%, the page layout is broken and site usage is prevented. When opening the working area, the focus is kept on the element opening it. Focus in general is not moved to the correct position when navigating between modal dialogs or when moving between phases in a dialog.
WCAG 1.3.1, 1.3.2, 2.1.1, 2.4.3, 4.1.2 General, mobile menu: all sections of the mobile menu cannot be used with a keyboard. The state of the menu is not displayed.
WCAG 1.1.1, 1.3.1 Agreements: ”Begin activation” texts are hidden in a mobile layout and their ”!” icons are only kept visible. The icons have been hidden from assistive readers, so a user with a screen reader is not able to get any information from the state of an agreement.
WCAG 2.1.1 Agreements, change agreement name icon: The change agreement name icon is not included in tab order and it has been hidden from assistive devices. Therefore keyboard and screen reader users are not able to change the agreement name.
WCAG 1.1.1, 1.3.1, 1.3.2, 2.4.2 Agreements, PDF files: PDF files have not been annotated so they are missing reading order, heading, alternative text and file name definitions.
WCAG 1.3.2, 4.1.2 Create new agreement, guided procedure phase element: When creating a new agreement, the displayed guided procedure phase element is missing the programmatic name, state and role. A user with an assistive device is thus not able get information on what element is in question, which phases are done and what is the current phase.
WCAG 4.1.2 Create new agreement, debit account for service charges: The account dropdown list does not show account names to screen readers; the account number is only visible.
WCAG 4.1.3 Create new agreement, error messages: Screen readers are not able to read error messages.
WCAG 1.1.1, 2.1.1, 2.4.3, 2.4.7, 4.1.3 Create MTLS certificate, file attachments: When managing file attachments, the keyboard focus is not shown in the file attachment addition element. Screen readers do not receive feedback when a file has been added or removed. The user can’t access the file removal with tab buttons and the removal does not work with all screen readers.
WCAG 2.1.1, 2.4.3, 4.1.2 Create new user, period of validity selection: The dates ”from” and ”until” need to be entered by using a calendar element, which is not accessible and does not support language translations.