The accessibility of the services 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 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.
Provisions on accessibility requirements are specified in the Act on the Provision of Digital Services.
This accessibility statement was created on 30 November 2020 and is last updated on 27th November 2024.
Accessibility status of the digital service
The Service reporting and Agreement management service do not conform to requirements.
Inaccessible content in the service Service Reporting
Some of the table headers can be used for sorting the rows. There are several problems with this functionality. The Raportti dropdown has no programmatic label. Screen reader users don’t hear the label when focusing on the element. The Yritys selection is complicated and has several accessibility issues. The date fields don’t have programmatic labels and the date fields are not programmatically grouped. Screen reader users don’t hear the labels when focusing on the elements and users don’t get information about their relationship. After the page loads, focus is often set at an atypical location such as the footer. This is very confusing. There is no feedback for screen reader users for the presence of an error message or the number of search results after the page load. There is few issues with text contrasts. The form doesn’t fit on a 320 CSS-pixel wide screen without horizontal scrolling. The error messages have some accessibility and usability issues that are not WCAG failures. The date pickers can’t be accessed using the keyboard or a screen reader. Keyboard focus is sometimes poorly visible. The pagination element is not programmatically separated from the rest of the page content. Therefore, it may be difficult for screen reader users to understand what it is. The “show instructions” link has no programmatic name, so screen reader users don’t know what the link does. There are several issues with the tabs in guidance. These issues are listed in more detail below.
WCAG 1.3.1 Info and Relationships
WCAG 1.3.2 Meaningful Sequence
WCAG 1.4.10 Reflow
WCAG 1.4.11 Non-text Contrast
WCAG 2.4.3 Focus Order
WCAG 2.4.6 Headings and Labels
WCAG 2.4.7 Focus Visible
WCAG 4.1.2 Name, Role, Value
WCAG 4.1.3 Status Messages
Inaccessible content in the service Agreement management
Accessibility issues include that nearly all form fields lack labels, making it impossible for screen reader users to know which field is currently in focus. Screen reader users cannot receive error messages without moving focus, and field-specific error messages are not programmatically linked to the fields. Screen reader users cannot receive feedback on performed functions. Keyboard focus is not visible in all elements, making it impossible for keyboard users to know which element is currently in focus. Tabulator order differs from the order of links on the page in some situations, and calendar elements are not included in the tabulator order. Pages have been organised using tables, resulting in unnecessary reading for screen readers. The tables also lack reflow. Page headings remain unchanged at various stages of the process. As a result, screen reader users do not receive clear feedback on what is happening. There are issues in the contrast between the application’s text and the background. These issues are listed in more detail below.
These issues are listed in more detail below.
WCAG 1.1.1 Non-text Content
WCAG 1.3.1 Info and Relationships
WCAG 1.3.2 Meaningful Sequence
WCAG 1.3.3 Sensory Characteristics
WCAG 1.4.3 Contrast (minimum)
WCAG 1.4.10 Reflow
WCAG 1.4.11 Non-text Contrast
WCAG 2.4.2 Page Titles
WCAG 2.4.3 Focus Order
WCAG 2.4.6 Headings and Labels
WCAG 2.4.7 Focus Visible
WCAG 3.3.1 Error Identification
WCAG 3.3.2 Labels or Instructions
WCAG 4.1.1 Parsing
WCAG 4.1.2 Name, Role, Value
WCAG 4.1.3 Status Messages