Accessibility Statement for the Oma Helen mobile application
This accessibility statement explains how the Oma Helen mobile application complies with the Act on the Provision of Digital Services, what shortcomings there are in its accessibility, and how you can provide us with feedback on accessibility issues.
This service is provided by Helen Ltd. We want as many users as possible to be able to use our digital services. We take accessibility into account in the development of our digital services.
How accessible is the service?
This service partially meets the accessibility criteria required by law at levels A and AA (WCAG 2.1 and 2.2). There are some accessibility shortcomings that are described in more detail below.
Have you noticed accessibility shortcomings?
We continuously strive to improve the accessibility of the service. If you find issues that are not described on this page, please let us know and we will do our best to correct the shortcomings. We will respond within 14 days.
Have you notice any shortcomings with respect to accessibility? Please let us know about it! You can contact us either by filling on an online form and selecting topic 'accessibility' or by calling 09 617 8080 (weekdays between 9 a.m. and 5 p.m.). The accessibility of the services of Helen Ltd is the responsibility of Helen’s Digital Solutions unit and Communications.
Monitoring of Accessibility
The Finnish Transport and Communications Agency (Traficom) monitors the implementation of accessibility requirements. If you are not satisfied with the response you receive, or if you do not receive a response at all within two weeks, you can provide feedback to Traficom. Traficom’s website “Submit a complaint on web accessibility or request clarification” provides detailed information on how to file a complaint and how the matter will be handled.
Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
www.webaccessibility.fi
saavutettavuus@traficom.fi
Telephone switchboard: +358 29 534 5000
Detailed Information on Technical Accessibility
The service is not yet fully accessible.
Content or Functions that are Not Yet Accessible
- Many views are missing heading tags for elements that act as headings. (WCAG 1.3.1)
- Users cannot change the app orientation. (WCAG 1.3.4)
- Charts might be hard to perceive due to color being used as the only distinguishing feature. (WCAG 1.4.1)
- Some charts are hard to understand due to missing information or visual information hierarchy. (WCAG 1.3.1, 1.3.2)
- There are some views, where user focus is not set to the start of the page when user selects “next” or opens a new view. (WCAG 2.4.3)
- With Android devices there are some cases, where content outside the screen space is not preloaded and is skipped. (WCAG 2.4.3)
- There are tab lists, which are not properly marked. (WCAG 1.3.1, 4.1.2)
- Some instructions are given only with visual or directional cues. (WCAG 1.3.3)
Informational structures are not clear for assistive technologies when checking electricity spot prices. (WCAG 1.3.2) - When logging into the app, there are elements that are communicated as disabled, while they are not: checkboxes for confirming terms of use and accepting information use for marketing. (WCAG 4.1.2)
- Some buttons that would lead the user back from a view are not named. (WCAG 4.1.2)
- The button for opening contacts is marked as an image. (WCAG 4.1.2)
Some buttons for editing information in contracts view are not named on Android. (WCAG 4.1.2) - Many buttons leading to more information do not have a role or name. (WCAG 4.1.2)
- Many elements on the main view are missing a role. (WCAG 4.1.2)
- When revealing content for specific element, sometimes the contents appear before the button. (WCAG 1.3.1, 1.3.2)
- Views with buttons for changing the views content do not have a name or the name is not informative of the purpose of the button. (WCAG 4.1.2)
- Many checkboxes and radiobuttons do not have a role, or do not have a clear association with each other. (WCAG 1.3.1, 4.1.2)
- Some text fields don’t have an accessible name. (WCAG 4.1.2)
- Instructions for inputs are not properly associated to input fields. (WCAG 3.3.2)
- Modals might have small problems with where the focus is set on Android. (WCAG 2.4.3)
The shortcomings listed here are intended to be corrected by the end of 2025.
How we have tested accessibility
The observations in this accessibility statement are based on a third-party assessment of whether the service meets the legal requirements defined in the law. The service and its accessibility are continuously being improved.
This statement was prepared on May 16, 2025.
The statement was last updated on May 16, 2025.