This accessibility statement explains how well MyWellness mobile application complies with the Act on the Provision of Digital Services, what shortcomings there are in the accessibility of the mobile application and how you can give us feedback on accessibility problems.

UniSport is responsible for this mobile application. We want as many users as possible to be able to access our digital services. We take accessibility into account in the development of digital services.

How accessible is the mobile application?

This mobile application partly meets the A and AA level accessibility criteria required by law (WCAG criteria 2.1). The mobile application has some shortcomings in accessibility, which are described in more detail below.

Did you notice any gaps in accessibility?

We are constantly striving to improve the accessibility of the application. If you observe any issues that are not described on this page, please let us know and we will do our best to fix any shortcomings. We will respond to requests and comments as soon as possible, but no later than within two weeks.

You can contact us by sending an email to unisport.asiakaspalvelu@helsinki.fi.

Accessibility monitoring

The Regional State Administrative Agency for Southern Finland monitors the implementation of accessibility requirements. If you are not satisfied with the response you have received or you do not receive a response at all within two weeks, you can give feedback to the Regional State Administrative Agency for Southern Finland. The website of the Regional State Administrative Agency for Southern Finland provides detailed information on how to file a complaint and how the matter will be processed.

Regional State Administrative Agency for Southern Finland
Accessibility Monitoring Unit
Accessibility Requirements website (in Finnish and Swedish)
saavutettavuus(at)avi.fi
Telephone (switchboard) +358 295 016 000

More detailed information on technical accessibility

MyWellness mobile application is not yet fully accessible.

Content or features that are not yet accessible

Application deployment, registration and login

• There are accessibility problems during the application deployment and registration process, as the form fields are missing visible labels and information about the required fields. Some fields and buttons are also non-descriptively named. (WCAG 3.3.2, 2.4.6)
• The error messages do not describe the correction suggestions. (WCAG 3.3.3)
• The semantic structure of some texts (headings, lists) is not conveyed correctly to the screen reader. (WCAG 1.3.1)
• Some buttons are missing a programmatic role and name. In addition, screen readers do not recognize the type of all dropdown menus correctly. (WCAG 4.1.2)
• The contrast ratios between the texts and the background during the registration and login process are insufficient. (WCAG 1.4.3)

General observations of MyWellness application

• The application's main navigation items (tabs) lack programmatic names, and TalkBack screen reader does not display the current tab. (WCAG 4.1.2)
• In some places, the application has content in different languages, the language markup of which is not correct. (WCAG 3.1.2)
• Using the application with a separate keyboard is very difficult, as the focus indicator is usually not visible. (WCAG 2.4.7)
• The application does not fully adapt to text enlargements, as part of the text content remains hidden. The application does not adapt to the horizontal screen position. (WCAG 1.3.4 and 1.4.4)
• The application lacks some programmatic heading tags. (WCAG 1.3.1)
• Several functional elements, such as buttons and links, lack a name and a role. (WCAG 4.1.2)
• The application has bookmark buttons, in which the status of the button (selected/unselected) cannot be understood with the screen reader. (WCAG 4.1.2)
• The application has drop-down menus, which do not indicate the opened/closed status to screen reader users. (WCAG 4.1.2)
• The application has flaws in the contrast ratios between the texts and the background. (WCAG 1.4.3)

Online lessons and recordings

• With VoiceOver screen reader (iOS) date selection of online lessons is an unclear process, as the screen reader does not read dates and days of the week together and does not recognize the dates as functional buttons. (WCAG 1.3.1 and 4.1.2)
• The VoiceOver screen reader cannot focus to the filters of Online classes at all. (WCAG 1.3.1)
• The application does not sufficiently inform screen reader users about the changes occurring on the page when booking an online class. (WCAG 4.1.3)
• The application (android) uses a table structure for visual layout in a few views. (WCAG 1.3.1)
• The application contains workout recordings published after 23 September 2020, which do not have captions. In some situations, the content of the recordings would also need audio description. Captions and audio descriptions for all the recordings published after September 23, 2020, would cause an unreasonable burden on the organization. We subtitle the recordings at our own discretion. (WCAG 1.2.2, 1.2.3 and 1.2.5)
• Controlling training records is very difficult or impossible with screen readers, as the buttons disappear before the screen reader has had time to read their contents. VoiceOver (iOS) does not find these controls at all. Some of the buttons are unnamed. In addition, the screen view is forced into a horizontal position, which is confusing especially for screen reader users. (WCAG 1.3.1, 2.1.1, 2.1.2, 2.2.2, 1.3.4 and 4.1.2)

Other content

• The carousel images of the home page are missing alt texts, and the area is not named. TalkBack screen reader does not detect controls (buttons) for changing images. (WCAG 1.1.1, 1.3.1 and 4.1.2.)
• The frame of the embedded Google map does not have any name. (WCAG 4.1.2)
• The application has short training recordings containing only a video image, for which there is no text or audio alternative. (WCAG 1.2.1)
• “Connect applications” buttons are missing an accessible name or an alt text of the logos. (WCAG 4.1.2/1.1.1)
• The “Add exercise” section of the application contains tabular data, which is not presented programmatically in a table. (WCAG 1.3.1)
• Adding training information with a screen reader is very difficult, as the selection of time, training duration and training place are unclear functionalities. (WCAG 1.3.1)
• The results view has an infographic, the information of which cannot be reached with a screen reader. Color contrasts of the infographic are also weak. (WCAG 1.3.1, 1.4.3 and 1.4.11)
• The filters of the infographic are missing accessible names or alt texts. (WCAG 4.1.2/1.1.1)

The schedule of the corrections of the shortcomings listed in this statement will be specified until the end of year 2023.

Content that does not have to comply with the accessibility requirements

Some of the training recordings have been published before 9/23/2020. These video recordings are not covered by the requirements of the Act.

Note

Captions and audio descriptions for all the recordings published after September 23, 2020, would cause an unreasonable burden on the organization. We subtitle the recordings at our own discretion.

How have we tested accessibility?

The observations in this accessibility statement are based on a third-party assessment of whether the mobile application meets legal requirements.

The mobile application was published on 1 September 2023.
This statement was prepared on 6 June 2023.
The statement was last updated on 7 September 2023.

Act on the Provision of Digital Services (306/2019) (in Finnish and Swedish)
Accessibility Requirements website (in Finnish and Swedish)