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 19 January 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.
Please see below for a list of non-conformities and exceptions applicable to the requirements.
Inaccessible content in the service
Using assistive devices such as screen readers may not be possible or may be very difficult for certain functions. Some of functions do not work with a keyboard, only with a mouse or a screen reader. Screen reader users do not receive feedback on the functions. When content appears to the right the focus does not move there automatically. Users of screen readers and keyboards will have to search for the content themselves. Correspondingly, the focus also does not move back to the main content when the process is complete. The focus does not always automatically move to different modal dialogue windows. It is extremely difficult for screen reader and keyboard users to access the dialogues. The programmatic labels for some elements are in English; a screen reader user who does not understand English will not understand which element is being referred to. The row headings are not defined, which makes identifying tables on the screen reader difficult. Error messages shown on forms are not automatically supported for screen readers. When there are mistakes on a form and a user tries to progress, nothing happens from a screen reader user’s point of view. Notifications have not been programmatically separated from other content, so their nature is not clear for screen reader users. Screen reader users do not receive feedback on the completion of various searches. The same symbol has several different meanings. 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.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
Content which is not accessible on the basis of disproportionate burden
Accessibility issues will be corrected during year 2024.