How accessible are the online services?

These online services partly meet the A and AA level accessibility criteria required by law (WCAG criteria 2.1). The online services have 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 online services. 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@avi.fi
Telephone (switchboard) +358 295 016 000

More detailed information on technical accessibility

UniSport.fi and the shop and reservation services are not yet fully accessible.

Content or features that are not yet accessible

Unisport.fi

• Images in the service haven’t been given an alternative text or marked as decorative in all instances. (WCAG 1.1.1)
• In the service, there are images, which have text on top of them. In some of these cases, the contrast isn’t sufficient between the text and its background. (WCAG 1.4.3)
• Link elements are not always visually evident, because they differ from surrounding body text with colour only. The color difference contrast is below 3:1. (WCAG 1.4.1)
• The accessible name of the language button doesn’t include it’s visible name. (WCAG 2.5.3)
• There are some pages in the service, where the heading structure is inconsistent. Some of the heading texts starting their own content area have not been marked with a programmatic heading element. (WCAG 1.3.1)
• There are some accessibility issues in the “Popular times at the gym”  element:
  • Contrast between the orange “Busy” line and its background is insufficient (below 3:1). (WCAG 1.4.11)
  • The tooltip content cannot be hidden without moving the pointer and it cannot be hovered on without it disappearing. The content is not shown at all when using keyboard only. (WCAG 1.4.13)
  • The element content is also presented in an invisible table element meant for screen reader users. The table content is in English but the language is not programmatically set. (WCAG 3.1.2)
  • The iframe of the element doesn’t have an accessible name. (WCAG 4.1.2)
  • The graphical elements of the visual presentation (lines, columns, numbers etc.) have not been hidden from screen readers, which makes the content quite complex and difficult to understand. (WCAG 1.1.1, 1.3.1)
  • The elements for choosing the day of the week don’t have an accessible name or state. (WCAG 4.1.2). They are also programmatically implemented in a way that differs from their visual presentation, which in turn affects their use and understandability. (WCAG 1.3.1).
• The carousel elements of the service have some accessibility issues:
  • The button names are in English in all of the language versions, which can mean not all users can understand them. (WCAG 2.4.6)
  • The pagination buttons’ programmatic implementation is inconsistent: they have been hidden from screen readers but they receive tab focus. (WCAG 4.1.2)
  • In the carousel element there is a “listbox”/”option” structure, which does not properly describe the element functionality. Also the pagination element structure has some programmatic accessibility issues. The <div> surrounding the element has the role of “tablist” but it’s child elements are button elements and not tab elements. In addition, the <div> elements surrounding the button elements have the aria-selected attribute, but for appropriate use, the attributes should be in the button elements instead. (WCAG 1.3.1, 4.1.2)
• Some interactive elements don’t have a visual focus indicator when they are used with keyboard only. (WCAG 2.4.7)
• Some accordion elements are button elements which have a heading element inside them. A button element cannot contain heading content, because with this structure it’s not able to retain all of these semantic properties. (WCAG 1.3.1).
• In the service multiple instances of the same landmark are used, but they are not named in way that they could be easily differentiated by users. (WCAG 4.1.2)
• The header region of the service contains roleless <div> elements, which in turn have aria-expanded attributes (but no function). These elements can seem confusing to screen reader users. (WCAG 4.1.2)
• In the service there are some card elements, which have some accessibility issues:
  • The images do not have a descriptive alternative text, or they haven’t been marked as decorative. (WCAG 1.1.1)
  • In some card types, the image is situated in it’s own <article> element, which makes the card structure more complex and difficult to understand when using a screen reader. (WCAG 1.3.1)
  • Some of the buttons that are inside the card elements have an aria-modal=”true” attribute even though they are not modal content. (WCAG 4.1.2)
  • In some cards, the contrast is not sufficient between the text elements and the background image. (WCAG 1.4.3)
  • Some of the card types consist of multiple link elements (with different names or no name), which makes the element structure and functionality difficult to understand, especially in screen reader and keyboard use. (WCAG 1.3.1, 2.4.4)
• In the search view, a list of suggestions appears under the search field. The list cannot be accessed by using keyboard only. (WCAG 2.1.1). If there are no search results in the list, a screen reader confusingly still announces one result. (WCAG 1.3.1).
• The navigation region surrounding the pagination element on the search result page hasn’t been named, although it is not the only navigation region on the page. (WCAG 4.1.2). The pagination element buttons are in English in all of the language versions of the page (WCAG 2.4.6).
• The mobile/enlarged user interface of the service has some accessibility issues:
  • The accessible name of the close button of the mobile menu doesn’t include the visible name of the element. (WCAG 2.5.3)
  • The search button name is in English in all language versions of the service (WCAG 2.4.6)
  • When the search view is activated, the keyboard focus is not transferred to the search area, and the focus is also not enclosed in the search view. (WCAG 2.4.3)
• The dialog elements have some accessibility issues:
  • When a dialog element is activated, a screen reader user will receive no feedback that something has happened. This is because focus is not automatically transferred to the dialog content that has been activated. (WCAG 2.4.3, 4.1.2). When the dialog element is closed, focus is not transferred to the element that originally opened the dialog element.
  • The dialog elements have missing roles and attributes, which would help users to understand their semantic properties and functionalities. (WCAG 4.1.2)
• In the service there is a video, which doesn’t have an audio description. The closed captions of the video do not include a description of the music playing in the audio track. (WCAG 1.2.5)
• The chat element of the service doesn’t have an accessible name. (WCAG 4.1.2) 

An effort to correct the shortcomings listed above will be made by 30.09.2024.

Webshop (oma.enkora.fi/unisport/reservations2)

• There are some buttons and headings in the service, which are not descriptive enough. (WCAG 2.4.6)
• In the Enkora service calendar, the reservation status of different spaces has been presented as symbols without alternative texts. In addition, there are some decorative image elements, which have alternative texts, which in turn adds to to the repetitiveness of the content. (WCAG 1.1.1, 1.4.5).
• Colour has been used as the only differentiator between the reservation statuses in the Enkora service. (WCAG 1.4.1)
• There are some contrast issues in the text and graphical elements in the service. (WCAG 1.4.3, 1.4.11)
• Screen reader and keyboard focus is not always transferred to modal content when it’s activated. The focus is also not set to the beginning of a new page in all instances. (WCAG 2.4.3)
• The page titles of the shop and reservation services are not descriptive enough. (WCAG 2.4.2)
• Using the service with assistive devices is problematic in some situations. In the service there are heading-like texts that haven’t been marked as programmatic headings. There are icons and images, which haven’t been marked as decorative, or been given an accessible name, so the indescriptive file name is read instead. There are situations, where screen readers read content repetitively or read elements which have been visually hidden. There are some form fields and elements, which don’t have their labels programmatically connected to them. (WCAG 1.3.1)
• There are some table structures and lists used in the service, but they don’t convey their information correctly when using a screen reader. Especially the reservation calendar element is a very difficult element to use on a screen reader, because the reservable objects are outside of the table structure. (WCAG 1.3.1)
• Tooltip content is not read at all when using a screen reader. (WCAG 1.3.1)
• There are some buttons and other elements which don’t convey necessary information of their current state (expanded/collapsed) to the user. Some links, buttons and other interactive components are missing an accessible name and role. In some cases the role given to an element is misleading, for example in the cookie window. (WCAG 4.1.2)
• The shop and reservation services have buttons and other elements which don’t convey the currently selected state accordingly to the user. (WCAG 1.3.1, 4.1.2)
• Visible status or other important changes happening in the shop and reservation service user interfaces are not always communicated accordingly to screen reader users. (WCAG 4.1.3)
• There is some content in the service, which appears on hover, but cannot be closed without moving the pointer device. The content cannot be hovered on without it disappearing. (WCAG 1.4.13) 

An effort to correct the shortcomings listed above will be made by 30.09.2024.

Online classes and recordings (Mywellness)

• The profile button is nameless and roleless and cannot be used with a keyboard or screen reader. (WCAG 1.3.1, 2.1.1 and 4.1.2)
• Bookmark buttons are nameless, and their active status is not interpreted to the screen reader. (WCAG 4.1.2)
• The browsing view of online classes has nested buttons, which is why they do not work correctly with a screen reader. (WCAG 4.1.2)
• The service has unnamed icon-buttons. (WCAG 4.1.2)
• The search field is missing a visible label. (WCAG 3.3.2)
• The service has drop-down menus, the status of which is not shown by the screen reader. (WCAG 4.1.2)
• The service contains heading-like texts, which are lacking heading tags. (WCAG 1.3.1)
• The video frames are not named descriptively. (WCAG 2.4.6)
• The service contains workout recordings published after September 23, 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 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)
• Video recordings have unnamed control buttons. (WCAG 4.1.2)
• The video rewind buttons cannot be reached with a keyboard or screen reader. (WCAG 1.3.1 and 2.1.1)
• The focus order of control buttons for videos is illogical. (WCAG 2.4.3)

The schedule of correcting the shortcomings listed above will get more precise during the spring 2024.

Options to work around accessibility issues before corrections are made

• The list view is a more accessible tool for doing reservations with screen reader than the calendar view. You can also reserve services by phone +358 2941 22151.
• Along with chat you can contact customer service and get support by phone (+358 2941 22151) or email (unisport.asiakaspalvelu@helsinki.fi).
• The virtual tours of sports facilities are not accessible to screen reader users. However, each facility page includes text-based information about the equipment of the facilities.

Note

There are recordings on the website, which are published before accessibility requirements were set and therefore don't meet accessibility criteria.

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 online services meet legal requirements.

The online services were published 2016.
This statement was prepared on 24 January 2023.
The statement was last updated on 3 May 2024.

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