This accessibility statement concerns loan applications, loan amendment applications and loan calculators for personal customers at op.fi. The services are a part of the website of OP Pohjola, and their accessibility has been assessed by accessibility experts working for OP Pohjola on a project basis. Self-assessments have also been performed with regard to the accessibility of the website.
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.
Provisions on accessibility requirements are specified in the Act on the Provision of Digital Services.
This accessibility statement was created on 1 January 2021 and last updated on 12 June 2025.
Accessibility status of loan services
Loan applications, loan amendment applications and loan calculators partially meet accessibility requirements. The release will rectify accessibility issues where necessary.
The non-compliances with requirements and exemptions are listed below.
Non-accessible content
Loan calculators
Non-accessible content in the home loan calculator
Accessibility requirements of the WCAG (Web Content Accessibility Guidelines) which the calculator does not yet fully meet are listed below.
WCAG 1.4.3 Contrast (minimum)
- There are issues in the contrast between the text and the background.
Non-accessible content in the loan calculators for consumer loans and student loans
Accessibility issues include the correct presentation of information, the function of error messages and the implementation of input fields. The calculators also contain a number of other issues that disrupt the use of assistive technologies such as screen readers and keyboard. In addition, documents included in the calculators do not meet accessibility requirements.
Accessibility requirements specified in the WCAG (Web Content Accessibility Guidelines) which the calculators do not yet fully meet are listed below.
WCAG 2.4.7 Keyboard Focus
- Focus is poorly visible or missing entirely at times.
WCAG 1.4.3 Contrasts
WCAG 1.4.11 Non-text Contrast
- There are issues in the contrast ratios between text and background and between user interface components and graphical objects.
- Some text disappears from view or overflows if the user enlarges text size with a personal CSS file.
- Heading levels are used in an illogical manner in places.
WCAG 1.4.12 Text Spacing
- Some elements are missing from the tabulator order and cannot be accessed using a keyboard. Screen readers do not receive information on all clickable elements.
- Form fields in the calculators are not in the logical tabulator order.
WCAG 1.3.1 Headings
- The slider control in the vehicle loan calculator does not always work with a screen reader.
WCAG 2.1.1 Keyboard Use
WCAG 4.1.2 Name, Role, Value
WCAG 2.4.3 Focus Order
- Info texts cannot be read with a screen reader and they are not included in the tabulator order.
- Icons lack text alternatives.
WCAG 1.3.2 Slider control in the vehicle loan calculator
WCAG 2.1.1 Keyboard
WCAG 1.1.1 Info texts and icons
WCAG 1.3.2
WCAG 1.4.13
WCAG 2.1.1
WCAG 1.1.1 Plus and minus buttons in input fields
WCAG 1.3.1 Info and Relationships
WCAG 1.3.2 Meaningful Sequence
WCAG 2.4.3 Focus Order
WCAG 3.3.2 Labels or Instructions
WCAG 4.1.3 Status Messages
- There are issues with the implementation of buttons and input fields. For example, they have not been programmatically linked, and the fields are missing labels. Screen reader users are not informed about the field’s new value after selecting a button.
WCAG 1.1.1 Links containing images
WCAG 2.4.4 The implementation method of links containing images causing issues to screen readers.
Applying for a loan
Non-accessible content in the home loan application (lainaa.op.fi)
The application contains individual issues that may hinder the use of assistive technology, such as screen readers and keyboards. Documents included in the application do not meet accessibility requirements.
Accessibility requirements specified in the WCAG (Web Content Accessibility Guidelines) which the application does not yet fully meet are listed below.
WCAG 1.1.1 Non-text Content in the preliminary loan offer attachment (PDF)
- Text alternatives for some icons are missing or incorrect.
- Some text alternatives for icons contain phrases that differ from the terms used in the service.
WCAG 1.4.3 Contrast (Minimum)
- There are several issues in the contrast between the text and the background.
Non-accessible content in the application for a secured bank loan
The application contains individual issues that may hinder the use of assistive technology, such as screen readers and keyboards.
Accessibility requirements specified in the WCAG (Web Content Accessibility Guidelines) which the application does not yet fully meet are listed below.
WCAG 1.1.1 Non-text Content
- Text alternatives are missing from some icons.
- Graphical files used for illustrative purposes are not skipped when using a screen reader.
WCAG 1.4.3 Contrast (minimum)
- Contrast ratios between the text and background are not sufficiently high in non-active buttons and in the orange highlight texts.
WCAG 4.1.2 Name, Role, Value
- Some names, roles and values of user interface elements cannot be automatically determined.
Non-accessible content in the Tailored Consumer Credit application
There are accessibility deficiencies in the presentation of information in credit decisions.
WCAG 2.1.1 Keyboard
- The pop-up window that contains credit decision information cannot be opened using the keyboard.
Non-accessible content in the student loan application
Accessibility issues include the correct presentation of information, focus order and feedback input. The application also contains a number of other issues that hinder the use of assistive technology such as screen readers and keyboard. In addition, documents included in the application do not meet accessibility requirements. These issues are listed in more detail below. The service will be updated in 2025–2026.
Accessibility requirements specified in the WCAG (Web Content Accessibility Guidelines) which the application does not yet fully meet are listed below.
WCAG 1.1.1 Non-text Content
- Some images include a redundant text alternative.
WCAG 1.3.1 Info and Relationships
- Selection buttons and checkboxes are not linked programmatically.
- Mandatory fields are not indicated visibly or programmatically.
- Negative numbers are presented incorrectly using hyphens.
- Some pages are aligned using tables, resulting in additional reading for screen readers.
- Some texts and heading/information pairs in text format are not presented programmatically.
WCAG 1.3.2 Meaningful Sequence
- Form elements contain incorrect attributes, causing them to be misaligned visually on the page.
- Some of the issues in headings make it difficult to understand the page’s hierarchy.
- There are issues with reading sequence in PDF files.
WCAG 1.3.6 Identify Purpose
- Form fields that contain the user’s information lack an attribute that determines their purpose.
WCAG 1.4.3 Contrast (minimum)
- There are several issues in the contrast between the text and the background.
WCAG 1.4.11 Non-text Contrast
- There are several issues in the contrast ratios of user interface components and graphical objects.
WCAG 1.4.12 Text Spacing
- When attempting to adjust character spacing, the row in question was cut out of the frame.
WCAG 2.4.2 Page Titles
- PDF files lack descriptive titles.
WCAG 2.4.3 Focus Order
- Focus is moved automatically to the first form field or interactive element, causing any preceding text to be skipped by the screen reader.
- In some cases, moving focus interrupts the reading of a message.
- In some cases, focus is moved automatically to the centre of the page.
WCAG 2.4.4 Link Purpose (In Context)
- File types and sizes are presented separately from links.
- Some links consist of a separate heading and body text, making them difficult to navigate using screen readers.
- The descriptions of some buttons are difficult to distinguish using a screen reader.
WCAG 2.4.7 Focus Visible
- Keyboard focus is not visible in the bar links on the page.
WCAG 3.3.1 Error Identification
- Error messages are not linked to fields programmatically. Fields with errors are not marked programmatically.
WCAG 3.3.2 Labels or Instructions
- Some labels are missing.
WCAG 3.2.4 Consistent Identification
- Some of the buttons on the page are titled inconsistently.
WCAG 4.1.3 Status Messages
- Feedback given by the page is implemented incorrectly, causing the screen reader to be interrupted.
- Feedback headings are not read by the screen reader.
Loan information and changes
Non-accessible content on the loan and repayment plan information page
Accessibility issues include the correct presentation of information, the function of drop-down menus and the logical hierarchy of headings. The application also contains a number of other issues that hinder the use of assistive technology such as screen readers and keyboard. In addition, documents included in the application do not meet accessibility requirements. The service will be updated in the coming years.
Accessibility requirements specified in the WCAG (Web Content Accessibility Guidelines) which the application does not yet fully meet are listed below.
Dropdown lists
WCAG 2.1.1
WCAG 2.1.2
WCAG 3.2.2
WCAG 3.3.2
WCAG 4.1.2
WCAG 4.1.3
- Labels are missing from the dropdown lists, causing screen reader users to fail to receive 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 – and in the method the elements are read.
- Choosing an option from the drop list automatically causes a new page to be downloaded.
Negative numbers and headings
WCAG 1.3.1
- Negative numbers are presented using a hyphen, which causes difficulties for screen readers.
- 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.
Contrasts
WCAG 1.4.3
WCAG 1.4.11
- There are issues in the contrast between the text and the background.
Diagrams in the repayment plan
WCAG 1.1.1
WCAG 1.3.2
WCAG 2.1.1
WCAG 1.4.12
WCAG 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.
Tables
WCAG 1.3.1
WCAG 1.3.2
- Row headings are missing from the 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.
Details of repayment plan instalments
WCAG 1.1.1
WCAG 1.3.1
WCAG 1.3.2
WCAG 2.4.7
- The information on instalments is presented as consecutive lists, 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 out part of the information twice, and in a sequence that is illogical for the user.
Favourites
WCAG 1.3.3
WCAG 1.3.1
- You can select your favourites by clicking the star, but someone using a screen reader
- Adding or removing a favourite is not programmatically separated from the rest of the page, so the user of a screen reader does not know what the X button closes.
Consistency with used terms
WCAG 3.2.4
- Loan and credit terms are used inconsistently throughout the applications.
Pop-up window’s hint
WCAG 4.1.2
WCAG 2.1.1
WCAG 1.3.2
WCAG 1.4.13
- The link that opens the pop-up window has no programmatic label, and it cannot be opened with the keyboard.
- Screen readers cannot read the text in the tip
- The pop-up window is displayed by focusing the mouse, it covers other content, and it cannot be overridden without moving the mouse to it.
Graphs
WCAG 2.1.1
WCAG 1.4.13
WCAG 4.1.2
- Screen readers cannot read the graphs.
- A person using a keyboard cannot access all the data inside graphs, because it requires focusing with the mouse.
Non-accessible content in the application for making changes to a secured loan
Documents included in the application do not meet accessibility requirements.
Accessibility requirements specified in the WCAG (Web Content Accessibility Guidelines) which the application does not yet fully meet are listed below.
WCAG 1.4.3 Contrasts
WCAG 1.4.11
- There are issues with the service’s contrast ratios.
OP Financial analysis for farms
Accessibility of the digital service
The financial analysis service for farms partially meets accessibility requirements. Identified accessibility issues are listed below.
Dropdown lists
There are accessibility issues with dropdown lists when using a screen reader and keyboard. The status of the menu is not clearly indicated, and there are issues with the dropdown list selection in keyboard use.
4.1.2 Name, Role, Value
Additional information buttons
There are accessibility issues with additional information buttons when using a screen reader and keyboard. Screen reader users are unable to perceive how the button works and how it is connected to the accompanying text.
4.1.2 Name, Role, Value
Notification area
The page has a notification area that functions incorrectly and causes accessibility issues for screen reader users.
4.1.2 Name, Role, Value
Tax returns for agricultural operations
Accessibility of the digital service
The service for ordering tax returns for agricultural operations partly meets accessibility requirements. Identified accessibility issues are listed below.
Notification area
The page has a notification area that functions incorrectly and causes accessibility issues for screen reader users.
4.1.2 Name, Role, Value