Accessibility Statement for OmaElisa
This accessibility statement applies to Elisa's consumer customer's self-service portal OmaElisa. The accessibility statement describes, how accessible OmaElisa is, what kinds of accessibility limitations there are and how you can give feedback about OmaElisa accessibility.
The service is subject to the Act on the Provisioning of Digital Services, which implements the European Accessibility Act and applies from 28 June 2025. The accessibility of this service has been assessed in cooperation with external accessibility experts in June 2024. This accessibility statement was created on 7th of February 2025 and last updated on 5th of June 2025.
Accessibility Status of OmaElisa
The service largely meets the accessibility requirements of WCAG 2.1 at levels A and AA.
Non-accessible Content
We are working to resolve identified accessibility issues as part of our continuous development process.
OmaElisa web service
- Header structure and alignment do not work consistently in all views. (WCAG 1.3.1, 1.3.2, 2.4.3, 2.4.6)
- The descriptive names of some functions and links are incomplete. (WCAG 4.1.2, 1.1.1)
- Pop-ups are not always correctly aligned and some are not accessible with the keyboard. (WCAG 2.1.1, 2.1.2 )
- In the contact information verification modal, in case of errors, the guidance text is not always visible. In addition, the text fields are missing labels. (WCAG 1.4.1, 2.4.6, 3.3.1)
- The screen reader is not told which navigation item is selected. (WCAG 4.1.2)
- The screen reader is not always told that the link will open in a new tab. (WCAG 1.3.1)
- When paying an invoice, the contrast of all bank logos is not sufficient. (WCAG 2.3.5)
- The payment agreement date selector does not fully meet the accessibility requirements. (WCAG 1.1.1, 1.4.3, 2.4.3, 4.1.2)
- No keyboard access to the details of monitoring subscription usage. (WCAG 2.1.1, 4.1.2)
- The address lookup function of the Fixer Tool does not work optimally on the screen reader. The status messages are also incomplete when using the screen reader. (WCAG 2.1.1, 4.1.3)
- There are a few errors in the service termination form related to language management. In addition, the headings indicating the steps of the form are missing. (WCAG 3.1.2, 2.4.3, 4.1.2)
- The authorisation form has text input fields with insufficient contrast. The text input field instructions are only available on the screen reader. (WCAG 1.4.11, 4.1.2)
Accessibility criteria that are not met
- 1.1.1 Non-text Content
- 1.3.1 Info and Relationships
- 1.3.2 Meaningful Sequence
- 1.4.1 Use of Color
- 1.4.11 Non-text Contrast
- 2.1.1 Keyboard
- 2.1.2 No Keyboard Trap
- 2.4.3 Focus Order
- 2.4.6 Multiple Ways
- 3.1.2 Language of Parts
- 3.3.1 Error Identification
- 4.1.2 Name, Role, Value
OmaElisa app
- Header structure and alignment do not work consistently in all views. (WCAG 1.3.1, 1.3.2, 2.4.3)
- Some navigations or menus do not tell the screen reader whether it is a button or a link. (WCAG 4.1.2)
- The screen reader is not always told that the link will open in the browser. (WCAG 1.1.1, 3.2.4)
- Speed test does not work on the screen reader. (WCAG 1.1.1, 2.2.2, 2.4.3)
- The detailed information on the invoice is not accessible from the screen reader. (WCAG 4.1.2)
- The link to edit the invoice delivery method appears visually as a tab. (WCAG 4.1.2)
- Not all text input fields have labels. (WCAG 3.3.2, 4.1.2)
- Not all confirmation messages and notifications are read by the screen reader. (WCAG 1.3.1. 4.1.3)
- When following subscription usage, it is difficult to read the amount of data transfer in large text size. (WCAG 1.4.4)
- In the head navigation, the selected point is only shown with a change in colour. The number of open invoices is not indicated to the screen reader. (WCAG 1.3.1, 1.4.1)
Accessibility criteria that are not met
- 1.1.1 Non-text Content
- 1.3.1 Info and Relationships
- 1.3.2 Meaningful Sequence
- 1.4.1 Use of Color
- 1.4.4 Resize text
- 2.4.3 Focus Order
- 3.2.4 Consistent Navigation
- 3.3.2 Labels or Instructions
- 4.1.2 Name, Role, Value
- 4.1.3 Status Messages