This statement applies to the accessibility of the Domos investor portal used in connection with alternative investments. The service is part of op.fi, which is the website for OP Financial Group companies.
The accessibility of the Domos portal 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 following systems were used in the self-assessments:
- Accessibility on desktop computers was tested using the Chrome web browser and NVDA screen reader software.
- Accessibility on mobile devices was tested using Apple devices and the Safari web browser (touch gestures).
Digital accessibility is regulated by the Finnish Act on the Provision of Digital Services.
This Accessibility Statement was created on 10 January 2025 and was last updated on 17 March 2025.
Accessibility status of digital service
Meets the requirements in part. Non-compliance with requirements and the applicable exemptions are listed below.
Inaccessible content
The Domos FS portal has digital accessibility issues in the following features and functionalities, for example:
Text and non-text contrasts of the site do not fully meet the digital accessibility requirements.
Also the focuses, headings and language selections of the site include certain issues.
In addition, all functions are not entirely accessible during activation and login. The screen reader does not necessarily function as expected in this context.
As for the documentation and documents, there are certain digital accessibility issues.
1. General
1.1 Language
The language of the pages has not been programmatically determined.
WCAG 3.1.1
1.2 Text contrasts
There are some flaws in the contrasts of the portal’s text that make the reading of the text more difficult
for people with reduced eyesight or who use screens with low brightness.
WCAG 1.4.3
1.3 Non-text contrasts
There are some issues in contrasts that make the reading of the text more difficult for people with reduced eyesight or who use screens with low brightness.
WCAG 1.4.11
1.4 Focus
During activation and login, the focus is set to the first input field when the page is opened.
WCAG 4.1.3, 2.4.3
1.5 Heading
The page heading is the same in most pages.
WCAG 2.4.2
1.6 Language selection
The available language selection at login is a button with a flag.
The flag button has been hidden from assistive technology. The flag button does not have programmatic or visual signs of it opening the language selection menu.
In the portal, it is not possible to open the language selection using a keyboard.
WCAG 1.1.1, 2.1.1, 4.1.2, 4.1.3
2. Activation and login
2.1 Deleted buttons
CTA buttons are inactive by default, until correct information has been entered in the fields.
WCAG 3.3.2, general accessibility
2.2 The OP logo
The alternative text for the OP logo is just “Logo”. Here, it does not determine which logo it is.
WCAG 1.1.1
2.3 Errors
If a user makes an error in the portal, an error message is immediately shown on the screen.
However, screen readers do not notify the user of the message.
WCAG 4.1.3, 1.3.1
2.4 Show and hide
Users can show or hide their password using the button at the end of the input field. As the accessible name does not contain visible text, using the button might be difficult or impossible with voice control.
WCAG 2.5.3, 4.1.2
2.5 Activation email
In the activation email, the OP logo has an empty IT attribute even though it does indicate from whom the email is.
The NVDA screen reader reads it as “empty”, because there are empty cells before and after it. The text refers to “the button below”. However, the button is technically a link, so screen reader users cannot find the “button” mentioned in the text.
WCAG 1.1.1, 1.4.3
2.6 Choosing the password
In choosing the password, users are not given instructions about the restrictions for the password.
The restrictions appear as error messages one at a time.
Screen reader users do not get notified of error messages.
WCAG 3.3.2, usability
2.7 Steps
Two steps of activation: passwords and two-factor authentication. The steps are unclear for screen reader
users for the following reasons:
- The steps have not been programmatically connected.
- The steps are span elements which are read together by the screen reader.
- The icons in front of the steps are hidden from screen readers. Screen reader users do not know the number of the step or whether the step has been completed or is it a coming step.
WCAG 1.1.1, 1.3.1
2.8 Checkbox
Users can select whether they want to use two-factor authentication using a switch
that functions programmatically as a checkbox. Screen reader users do not hear this when the focus is on the checkbox.
WCAG 1.3.1
2.9 Two-factor authentication
The alternative text for the QR code is “No QR code available”, which gives screen reader
users the wrong impression. When screen reader users navigate in the focus mode, using the switch
sends them directly to the PIN field, so they miss all the information in between.
Scanning a QR code might be difficult especially for blind users or users with restricted motor skills. Also the time limit of 30 seconds might pose challenges for certain users.
WCAG 1.1.1, general accessibility
3. Document site
3.1 Programmatic structure
The site does not have programmatic headings. Visually, New documents and All documents
are headings. The site has a main area, but the elements on the left are not in any of the
areas. Also the menu button is not marked as navigation.
WCAG 1.3.1, 2.4.1, general accessibility
3.2 Search
An accessible name is missing from the search button. Screen reader users might not know what it does. It comes before the input field in the reading and tab order, which is a bit odd and might lead to using the button only rarely.
The own search field label is the placeholder text.
Both the placeholder text and the search button have poor contrast, so some users might have difficulties to know for what the input field is intended.
WCAG 4.1.2, 1.4.3, 1.4.11, 4.1.3
3.3 Filters
Filters have labels but they are not programmatically linked to input fields.
On smaller screens, the labels are not entirely visible and the input field cannot be seen.
Dates cannot be entered, and the user has to use the date selector.
In case of an error, the edges of the field turn to red.
WCAG 1.3.1, 3.3.2, 3.3.3
3.4 Document tables
In document tables, the tables are not programmatically tables.
In addition, the tables are not responsive, and they cannot be scrolled on small or zoomed screens.
Table headings have poor contrast, and they are not interactive.
The checkboxes do not have a label.
PDF identifiers have been hidden from assistive technology, so screen reader users do not know the format.
WCAG 1.3.1, 1.4.10, 1.4.3, 4.1.2, 3.3.2, 1.1.1
3.5 Downloading
Screen reader users do not get feedback from downloading a document.
WCAG 1.1.1, 4.1.3
4. Documents
4.1 PDF files
The digital accessibility of PDF documents has not been fully considered when creating them:
Identifiers and language definition are missing from the documents.
Also headings are missing from the documents.
WCAG 1.3.1, 2.4.2, 3.1.1