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).
Provisions on accessibility requirements are specified in the Act on the Provision of Digital Services.
This accessibility statement was created on 8 December 2020 and is last updated on 27th November 2024.
Accessibility of the digital service
The Invoicing service does not meet accessibility requirements. However, none of the identified issues prevent using the service for its primary purpose of creating and sending invoices.
Inaccessible content in the service
When content opens on the right, focus is not always automatically moved to it. Screen reader and keyboard users need to search for the content themselves. Similarly, focus does not always move from the right back to the main content when the process is complete. Focus does not always automatically move to different modal dialogue boxes but instead stays on the page below the dialogue box. It is extremely difficult for screen reader and keyboard users to access the dialogues. The page does not scale sufficiently. There are deficiencies in the definition of tables in the service. Screen reader users do not receive feedback on functions. It is unclear to them whether the action they are trying to perform has been executed. Many form elements have instructions, but they have not been programmatically attached to the elements. Error messages displayed on forms are not automatically read by the screen reader. When the form contains errors and the user tries to proceed, nothing happens from the screen reader's perspective. There is no feedback to the screen reader if different searches are completed. Elements that need to be focused are placed in layers and, among other things, cause the available name for the inner element not to be read when moving with the tab key between the elements. Keyboard focus is very weak on buttons. There are some deficiencies in the page headers. The current date is not programmatically marked in the date selector. The magnifying glass button has been used with different meanings. Some function buttons do not work with the keyboard, only with the mouse or screen reader. Messages have not been programmatically separated from other content and it is unclear to the screen reader user what they relate to. The programmatic name labels for both fields in the time period are the same. Fields and buttons related to the work process have not been grouped programmatically. Screen reader users do not receive information about which element is related to the workplace when they focus on fields or buttons. The step path has been implemented with an element intended to display long processes. 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 Meaninful Sequence
WCAG 1.4.3 Contrast (Minimun)
WCAG 1.4.10 Reflow
WCAG 1.4.11 Non-text Contrast
WCAG 2.1.1 Keyboard
WCAG 2.4.3 Focus Order
WCAG 2.4.6 Headings and Labels
WCAG 2.4.7 Focus Visible
WCAG 2.5.3 Label in Name
WCAG 3.2.4 Consistent Identification
WCAG 4.1.2 Name, Role, Value
WCAG 4.1.3 Status Messages