This accessibility statement refers to the accessibility of the Financing for Corporate Customers service at op.fi. The accessibility of the Financing for Corporate Customers 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 Financing for Corporate Customers service at op.fi includes alternative customer service channels that we provide in addition to our telephone service, chat, messaging through our website or apps or visiting our branches.
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) and the VoiceOver screen reader app.
The provisions on accessibility are included in the Act on the Provision of Digital Services.
This accessibility statement was created on 9 December 2020 and was last updated on 18 December 2023.
Accessibility status
Financing for Corporate Customers at op.fi meets the accessibility requirements in part, unless otherwise specified for the service. Non-conformities are described below for each service separately. Our aim is to correct accessibility issues by the end of 2024.
Issues in the Loan details and Payment scheme service
WCAG 1.3.2, 2.1.1, 2.1.2, 3.2.2, 3.3.2 Labels are missing from the dropdown lists, so screen readers do not get information about which dropdown list is accessed. There are deficiencies in the operation of the dropdown lists, for example in using tabulator keys in navigation and in the sequence of reading the list elements. Choosing an option from the drop list automatically causes a new page to be downloaded.
WCAG 1.3.1 Negative figures are shown using a hyphen, which causes difficulties for screen readers.
WCAG 1.3.1 Heading levels have been used incorrectly and some row headings are missing from some tables. The headings in some tables have not been implemented as HTML headings.
WCAG 1.4.3, 1.4.11 There are issues in the contrast between the text and the background.
WCAG 1.1.1, 1.3.2, 2.1.1, 1.4.12, 1.4.13 Screen readers cannot access the payment scheme chart information. The exact information shown by focusing the pointer cannot be displayed by using the keyboard, and the additional information cannot be hidden without moving the focus. In the mobile layout, the information below the chart is incompletely presented and the scroll element is not included in the tabulator order. The user’s own CSS file may lead to the overlapping of texts.
WCAG 1.3.1 Row headings are missing from the payment scheme tables, which makes it difficult for the screen reader to read the tables. The accordion headings containing tables are not HTML headings, which makes it difficult to understand the page hierarchy.
WCAG 1.3.1, WCAG 1.3.2 In the instalment information for the payment scheme, the information on the instalments is presented in successive lists on the page, which makes the page longer and makes it more difficult for the user to find the total amount at the end of the page. Screen readers read part of the information twice.
WCAG 1.1.1, 1.3.1, 1.3.2, 2.4.7 In the My Loans element, the table heading is not defined as a HTML heading. Row headings have not been defined and there are two rows for column headings, which causes problems for the screen reader, as do the links within the rows in the table. There are also empty columns in the rows. It is difficult to see the keyboard focus, and there are shortcomings in the reading sequence and text responses.
Unreasonable burden
Modifying certain content in the Loan and Payment scheme information would be an unreasonable burden. Our objective is to update the service by the end of 2025.
Issues in the credit balance confirmation service
The implementation and usability of the page have accessibility issues. Semantic markings are missing from the PDF file of the service and contrasts are not sufficient. The results table is imprecisely implemented. These issues are listed in more detail below.
WCAG 2.5.3, 4.1.2, usability The dropdown list implementation elements are not accessible.
WCAG 1.3.1, 1.3.2, 2.4.2 3.1.1 Semantic markings are missing from the PDF file, which makes it difficult to interpret the reading sequence. Headings and the language have not been defined. The title attribute is in English.
WCAG 1.4.3 Contrast ratios
WCAG 3.3.1, 4.1.3 The search does not automatically provide feedback for the screen reader.
WCAG 1.3.1, 2.4.4 The implementation of the results table is unclear for screen readers (column headings, use of Open links, unnecessary summary attribute)
WCAG 4.1.3 Screen readers do not detect the information about a delay in downloading.
Issues in the list of pledges service
Accessibility issues include the following: screen readers do not receive clear feedback on searches and the keyboard focus is imprecise. Increasing text size to 200% disrupts the layout slightly. The service is not responsive. These issues are listed in more detail below.
WCAG 1.3.1, 1.3.2, 2.4.2 3.1.1 Semantic markings are missing from the PDF file. Headings, document language and the file title attribute have not been defined.
WCAG 1.4.3 Contrast ratios
WCAG 1.3.1, 2.4.4 Column heading is missing from the results table. Use of Open links is unclear in part.
WCAG 1.3.1 The page layout uses a table.
WCAG 1.4.4, 1.4.10 Increasing text size to 200% disrupts the layout slightly. The service is not responsive.
General accessibility
Keyboard focus should be made more precise.
Label is missing from the dropdown list.
Search does not provide clear feedback for the screen reader.
Issues in the credit facility service
Accessibility issues include the following: the site is not fully compatible with all assistive technology, such as screen readers. The service is implemented as a one-page application. The service is not responsive and the contrast ratios are insufficient. Keyboard focus is unclear in places. There are accessibility issues in the error messages and info texts.
WCAG 1.4.4, 1.4.10 Increasing text size to 200% disrupts the layout slightly. The service is not responsive.
WCAG 1.3.1 Negative figures are shown using a dash, meaning the VoiceOver screen reader does not read the character if the default settings are used.
WCAG 2.4.2, 2.4.3, 4.1.3 One-page application, which means that screen readers do not notice changes on the page, such as page downloads. The pages have the same title attribute, meaning that user location is imprecise. Keyboard focus is imprecise in places.
WCAG 1.4.3, 1.4.11 Contrast ratios
WCAG 4.1.2 Feedback Alert role unnecessarily interrupts the screen reader.
WCAG 1.3.1 When presenting information, the heading-value pairs are not programmatically presented, which may impair interpretation.
WCAG 2.4.7 Keyboard focus is imprecise in places.
WCAG 4.1.2 Screen readers do not receive information on the accordion status (open/closed).
WCAG 1.3.1, 2.4.4, general accessibility Tables are implemented in a way that screen readers find unclear (column headings, table links, row headings, button text, number sectioning)
WCAG 1.3.1 Heading hierarchy levels are illogical in relation to each other.
General accessibility Some of the links to orders to be approved use several span elements, which are difficult for the screen reader to interpret.
WCAG 1.3.1 Readable elements have been used unnecessarily in the implementation.
WCAG 1.3.1, 3.3.2 Programmatic label is missing. Parts of a two-field entity have not been problematically linked.
WCAG 1.1.1, 1.3.2 Text alternatives are missing from the calendar buttons.
WCAG 2.1.1, 1.4.13 Info text i icons are not included in the reading and tabulator sequence. Moving the pointer over a speech bubble makes the bubble disappear.
WCAG 3.3.1, general usability Error messages have several issues. Not all error messages are programmatically linked to the fields. Pressing the Continue button does not indicate the errors. Some error messages are read between field headings and units. Error check is performed on the page when writing takes place.
Issues in the corporate finance application service
Accessibility issues in this service include contrasts between the page and the background colour that do not fully meet accessibility requirements. There are problems in reading content: the service is not fully compatible with all assistive technology, such as screen readers, for large text fields, slide pointer fields, increasing collateral and info texts, for example. In addition, the financing application is a one-page application, meaning that page changes in the application form are not noticeable. These issues are listed in more detail below.
WCAG 1.3.1, 3.3.2 Large text field labels have been defined by aria-label attribute, which replaces the actual labels of fields for screen readers. Slide control is a self-programmed custom element. The asterisk denoting a mandatory field has not been explained. Dropdown menu prompts may appear as or resemble prefilled information. Checkboxes have two labels. “Applicant name” has been defined as a label but there is no corresponding field for it.
WCAG 3.3.1, 4.1.3 When proceeding, the user is not informed of a visible field error message. The error message may appear too early or it is not sufficiently informative. Download information is not given to users of assistive devices.
WCAG 1.3.2, 1.4.13 Screen readers cannot access the info texts using arrow keys. Info texts open automatically with a keyboard or a pointer focus and cover other content.
WCAG 1.3.2, 2.4.2, 2.4.3 One-page application, which means that screen readers do not notice changes on the page without help.
WCAG 2.2.1 The dialogue works but the connection time-out is too short.
WCAG 1.4.3, 1.4.11 Contrast ratios are not sufficient.
WCAG 1.1.1, 1.3.1, 1.3.2, 1.3.3, 1.4.1, 1.4.4, 2.4.6, 4.1.2 Screen readers do not receive information about the process path such as the number and status of substeps.
General usability In the page layout, the lengths of input fields do not correspond to the lengths of their inputs. The checkbox layout differs from the established way in which the text is set on the right hand side of the box. The purpose of the save button is unclear. There are no formatting guidelines in the phone number field.
WCAG 4.1.1 Insufficient HTML quality.
WCAG 1.3.1 Screen readers read the page’s cross lines as “dividers” because they have not been hidden.
WCAG 1.3.5 Field autofill remains partially unclear to the user.
WCAG 1.3.1, 2.1.1, 2.4.3 The accordion is not included in the tabulator order. The accordion heading is not an HTML heading. The accordion heading hierarchies are illogical in relation to each other.
WCAG 1.3.1, 2.4.3, 2.4.4 Screen readers may find it difficult to add collateral. When removing collateral, it is difficult to know which collateral the removal link relates to.
WCAG 1.1.1, 1.3.2, 2.4.4 Uploading attachments to the application: the file browse button is placed on top of the system button. It may be difficult to understand from the removal link which file the link should relate to. The screen reader may not be able to interpret file icons in the right places.
WCAG 1.3.2, 2.4.3 The file upload link is placed after the return link in the reading and tabulator sequence.
WCAG 1.3.1, 1.3.2 Markings are missing from the PDF file which makes it difficult to read for the screen reader.
Issues in the Loans with OP Corporate Bank service
This corporate loan online service meets the requirements in part. Accessibility issues include the following: the site is not fully compatible with all assistive technology, such as screen readers. The service is implemented as a one-page application. The service is not responsive and the contrast ratios are insufficient. Keyboard focus is imprecise in places. There are accessibility issues in the error messages. These issues are listed in more detail below.
WCAG 1.4.4, 1.4.10 Increasing text size to 200% disrupts the layout slightly. The service is not responsive.
WCAG 1.3.1 Negative figures are shown using a dash, meaning the VoiceOver screen reader does not read the character if the default settings are used.
WCAG 2.4.2, 2.4.3, 4.1.3 One-page application, which means that screen readers do not notice changes on the page, such as page downloads. The pages have the same title attribute, meaning that user location is imprecise. Keyboard focus is imprecise in places.
WCAG 1.4.3, 1.4.11 Contrast ratios
WCAG 4.1.2 Feedback Alert role interrupts the screen reader.
WCAG 1.3.1 When presenting information, the heading-value pairs are not programmatically presented.
WCAG 2.4.7 Keyboard focus is imprecise in places.
WCAG 4.1.2 Screen readers do not receive information on the accordion status (open/closed).
WCAG 1.3.1, 2.4.4, general accessibility Tables are implemented in a way that screen readers find unclear (column headings, table links, row headings, button text, number sectioning)
WCAG 1.3.1 Heading hierarchy levels are illogical in relation to each other.
General accessibility Some links include several span elements.
WCAG 1.3.1 Readable elements have been used unnecessarily in the implementation.
WCAG 1.3.1, 3.3.2 Programmatic label is missing. Parts of a two-field entity have not been problematically linked.
WCAG 1.1.1, 1.3.2 Text alternatives are missing from the calendar buttons.
WCAG 2.1.1, 1.4.13 Info text i icons are not included in the reading and tabulator sequence. Moving the pointer over a speech bubble makes the bubble disappear.
WCAG 3.3.1, general accessibility Error messages have several issues (not all error messages are programmatically linked to the fields); pressing the Continue button does not indicate the errors; some of the error messages are read between the field headings and the units; an error check is performed on the page while writing takes place).
Issues in the factoring service
The website of the factoring service does not meet all of the accessibility requirements but none of the observed deficiencies prevent the service from working or prevent its use. Correcting the deficiencies is dependent on the required technical change, i.e. the update schedule of the browser framework currently in use. 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 with keyboard use. Observance of a tabulator order is missing, and since this is a one-page application, screen readers do not notice the changes on the page.
These issues are listed in more detail below.
WCAG 1.3.1, 4.1.2 Navigation
WCAG 1.3.1, 3.3.2, 4.1.2 Toggle switches
WCAG 1.3.1, 3.3.2, 4.1.2 Drag and drop controls
WCAG 1.3.2, 2.4.2, 2.4.3 One page app
WCAG 1.3.1, 2.4.1 Page structure
WCAG 2.1.1, 1.4.1, 1.4.13, 4.1.2 Charts
WCAG 1.3.1 Negative figures
WCAG 2.4.7 Keyboard focus visible
WCAG 4.1.3 Feedback
WCAG 4.1.3 Download animation
WCAG 2.2.1, 4.1.3 Time-out
WCAG 1.4.10, 1.4.12 Reflow
WCAG 2.4.1, 4.1.2 Frames
WCAG 1.3.1 Heading-value pairs
WCAG 1.3.1 Clickable elements
WCAG 1.3.1, 2.4.4 Multipart links
WCAG 4.1.1 HTML quality
WCAG 1.3.2, 2.1.1, 2.4.3 Adding viewports
WCAG 2.1.1 Tabs
WCAG 2.1.1 Month selection
WCAG 2.4.2 Page name
WCAG 3.3.1 Error messages
WCAG 1.3.1 Mandatory fields
WCAG 3.3.2 Text in tips
Issues in the Trade Finance online service; online services for bank guarantees and documentary payments
The Trade Finance online services do not fully meet the accessibility requirements. However, none of the detected issues prevent the operation or use of either of the services. An audit of the above-mentioned issues is underway. Some of the issues are known, and a report on correcting the issues will be drawn up after the audit. Please see below for a list of non-conformities and exceptions applicable to some of the requirements.
Accessibility issues in the documentary payment service include the following: the colour contrasts do not fully meet accessibility requirements, and the site is not fully compatible with all assistive technology, such as screen readers. The online service is only in English, as intended. Translation of the bank guarantee products was started in 2023. The launch will commence by the end of 2024. It should be noted that this is a service in which the products are mainly in English and these are used by corporate customers engaged in international trade. The site does not use tips, meaning that the service does not provide guidance. The system supplier’s version update was carried out in October-November 2020, and some of the functionalities are still being updated in production. Further small-scale development to improve functionalities will also be carried out in the future. Some of the updates will require the application version to be updated, the design of which will not be possible until 2024.
Accessibility issues in the bank guarantee online service include the following: the site is not fully compatible with all assistive technology, such as screen readers. The page colour contrasts do not fully meet the accessibility requirements (the colour correspond to the ones used at op.fi). The current online service for bank guarantees will be discontinued when the transfer of the guarantee products to the new application is completed.