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 Financial Group, and their accessibility has been assessed by accessibility experts working for OP Financial Group 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 18 June 2024.
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 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 a number of issues that significantly hinder the use of assistive technology such as screen readers and keyboard. In addition, documents included in the application do not meet accessibility requirements.
Customers can apply for a home loan and discuss matters related to home loans and housing financing at OP bank branches in person or, depending on the bank, by phone or video conference.
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.11 Non-text Contrast
- The contrast ratio of user interface components and graphical objects is incorrect.
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 (lainaa.op.fi/pankkilaina)
The service has accessibility issues in, for example, headings, structures and labels, causing difficulties for screen reader users. In addition, colour contrasts in the application do not always meet accessibility requirements, and some graphical objects lack text alternatives. There are also issues with keyboard navigation.
Customers can apply for a secured bank loan and discuss matters related to bank loans also at OP bank branches in person or, depending on the bank, by phone or video conference.
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.3.1 Info and Relationships
- Headings, structures and labels are not always correctly programmatically marked, or the markings are missing altogether.
WCAG 1.3.5 Identify Input Purpose
- Input purpose has not been defined in the service’s section for contact information.
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 1.4.4 Resize Text
- Text size cannot be changed on the login page.
WCAG 2.1.1 Keyboard
- Some elements on the service’s homepage cannot be navigated with a keyboard.
WCAG 2.4.1 Bypass Blocks
- The service’s main content cannot be accessed directly from the start page.
WCAG 2.4.2 Page Titles
- The page title is identical on each page of the application service and does not describe the purpose of individual pages.
WCAG 2.4.3 Focus Order
- Focus order logic varies between different views in the service and is inconsistent at times.
WCAG 2.4.7 Focus Visible
- Focus is not always visible when navigating elements with a keyboard.
WCAG 3.3.1 Error identification
- Screen readers do not automatically read error messages that occur when filling in the application.
- Error messages are not programmatically linked to the fields that they concern. The error message may also appear incorrectly while the user is inputting information.
WCAG 3.3.2 Labels or Instructions
- Some labels are not programmatically linked to the elements that require user input, or the labels are missing altogether.
WCAG 4.1.1 Parsing
- Some IDs in the application form are not unique.
WCAG 4.1.2 Name, Role, Value
- Some names, roles and values of user interface elements cannot be automatically determined.
WCAG 4.1.3 Status Messages
Error messages cannot be programmatically identified as error messages. When loading the next view or after successfully sending the form, the screen reader does not automatically read the relevant status message.
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.
WCAG 2.1.1
WCAG 2.1.2
WCAG 3.2.2
WCAG 3.3.2
- 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.
- Choosing an option from the drop list automatically causes a new page to be downloaded.
WCAG 1.3.1 Negative numbers and headings
- 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.
WCAG 1.4.3 Contrasts
WCAG 1.4.11
- There are issues in the contrast between the text and the background.
WCAG 1.1.1 Diagrams in the repayment plan
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.
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.
WCAG 1.1.1 Details of repayment plan instalments
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.
Non-accessible content in the application for making changes to a secured loan
Accessibility issues include the correct presentation of information, the logical hierarchy of headings and the implementation of forms. 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.
Accessibility requirements specified in the WCAG (Web Content Accessibility Guidelines) which the application does not yet fully meet are listed below. The application for making changes to a secured loan will be updated in 2024.
WCAG 1.3.1 Labels or Instructions
WCAG 3.3.2
- Labels are missing for some form fields.
- Interrelated fields in the application, and instructions related to fields and remaining character counters are not programmatically linked to the fields. ´
WCAG 1.3.2 Tabulator order and reading sequence
WCAG 2.4.3
- Keyboard focus moves automatically to the first field on the application page.
WCAG 1.3.1 Error messages
- Error messages are not programmatically linked to the fields.
- Invalid values entered in a field are automatically changed to numbers.
WCAG 4.1.3 Status Messages
- Screen readers cannot detect loading animations in the service.
- Feedback is implemented using the alert role, which interrupts the screen reader.
- Screen readers may read text that is not displayed on the page.
WCAG 1.3.1 Negative numbers
- Negative numbers use hyphens.
WCAG 1.1.1 Information Texts
WCAG 1.3.2
WCAG 1.4.13
WCAG 2.1.1
- Info texts cannot be read with a screen reader and they are not included in the tabulator order.
- Icons lack text alternatives and open automatically when the pointer is over them, causing them to block other content from view
WCAG 1.4.3 Contrasts
WCAG 1.4.11
- There are issues with the service’s contrast ratios.
WCAG 1.3.1 Headings
WCAG 1.4.3
WCAG 1.4.11
- Heading levels are illogical in places, and not all headings are programmatically determined.
- Heading/value pairs in accordion menus are not presented semantically.
WCAG 1.3.1 Table structure
- Several cells in the loan table are merged as a single cell, and the row headings have not been determined.
- Expanding the rows jumbles the table’s heading.
WCAG 1.1.1 Plus and minus buttons in input fields
WCAG 1.3.1
WCAG 1.3.2
WCAG 2.4.3
WCAG 3.3.2
WCAG 4.1.3
- The plus and minus buttons and input fields are not programmatically linked.
- The fields lack labels, and the minus button is missing a text alternative.
- Units are not linked to the fields.
- Screen reader users are not informed about the field’s new value after making a selection.
WCAG 1.1.1 Step progress path structure
WCAG 1.3.1
WCAG 1.3.2
WCAG 1.3.3
WCAG 1.4.1
WCAG 1.4.4
WCAG 2.4.6
WCAG 4.1.2
- The implementation of the step progress path is not compatible with screen readers, causing screen reader users to fail to receive information about the path’s structure.
WCAG 2.4.3 Disabled continue button
- The Continue button is disabled if mandatory information is missing from the form, making it difficult for users to know why the button is disabled.
Farmers’ financial analysis
The farmers’ financial analysis partially meets the accessibility requirements. The accessibility issues are listed below.
WCAG 1.3.1, 4.1.2 Error messages
WCAG 2.4.7, 1.4.11 Keyboard focus visible
WCAG 2.4.3 Invisible elements
WCAG 4.1.2 Dropdown lists