This accessibility statement explains how the VIBAe online store 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 VIBAe Oy. 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.

You can contact us by email at customercare@vibae.com

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

The content listed below is not accessible for the following reasons:
Non-compliance with the Act on the Provision of Digital Services (306/2019)

The shortcomings listed here are intended to be corrected by 2026.

General issues
There are functional items in the service that do not work with a screen reader and/or keyboard. Below is more detailed information about challenging items and some instructions on ways to work around the problems:

- The main navigation submenus (All Products, Styles, etc.) and the Info submenu do not work with NVDA screen reader or keyboard alone. If you need a screen reader, you can try using VoiceOver on iPhone or TalkBack on Android phone to access the main navigation. You can also navigate from one page to another via the links in the footer.

- Country and language selection does not work at all with the VoiceOver screen reader and works only partially with the NVDA screen reader (NVDA allows the user to select a country from the search field, but the language cannot be selected at all). If you need a screen reader, you can try using the TalkBack screen reader to select a country and language. You can also type the abbreviation of the language you want directly in the address bar after the slash sign, e.g. vibae.com/fi.

- The search results of the size guide's brand search and store search cannot be accessed with only a keyboard.

-In the size guide, the unit of measurement (centimeters/inches), size and foot width cannot be selected with the keyboard alone.

- In the review section, the buttons for awarding stars do not work on the keyboard alone, and using them with a screen reader is complicated. In addition, there is a keyboard trap in the star buttons.

- The video on the Carbon Step page cannot be started with keyboard, and it may also be difficult to start the video with screen reader.
(WCAG 2.1.1, 2.1.2)

- The online service contains some links, buttons and form functionalities whose visible or accessible names are non-descriptive. Also, the accessible names of some modal dialogs are non-descriptive. In addition, the name of the newsletter subscription button varies on different pages and in different views. (WCAG 2.4.4, 2.4.6, 3.2.4)

- Screen readers may pronounce content with incorrect pronunciation in some places. (WCAG 3.1.2)

- A screen reader does not always provide real-time feedback on changes or updates to content (e.g. search results appearing in the same view, using the Next and Previous buttons, applying, removing or clearing filters, synchronization of video transcription, change of button name). In addition, in some situations, the screen reader reads extra noise as a status message (e.g., the number of reviews when the search results page loads and the entire search results section during a store search). (WCAG 4.1.3)

- Some functional items do not have a clear role (e.g. button, radio button, tab). Some functional objects lack information about the state of the item (e.g. selected/not selected, expanded/collapsed, current). Some buttons have additional state information (e.g., collapsed/expanded state in a button for opening a modal dialog). (WCAG 4.1.2)

- Some functional items, such as buttons and links, do not have accessible names, or the accessible name is technically incorrectly marked. (WCAG 4.1.2)

Perceivability of content

- There are images in the service whose text alternatives are not sufficiently descriptive (e.g. a text alternative is the same as a nearby link or heading) or they contain unnecessary information (e.g. “Country flag” in the country selection drop-down menu). Some individual functional and non-functional images have no text alternatives at all. In addition, the service has decorative images with unnecessary and noisy text alternatives. (WCAG 1.1.1)

- The online service contains texts and functional items that do not have sufficient contrast to their background. (WCAG 1.4.3, 1.4.11)

- There are videos on the service that lack audio description, even though the audio track is only music. (WCAG 1.2.3, 1.2.5)

Structure and focus

- The web pages have headings that are not programmatically marked as headings. In addition, on some pages, the heading hierarchy is marked the wrong way around. The online service also has individual non-descriptive headings. (WCAG 1.3.1, 2.4.6)

- Focus often behaves inconsistently in the modal dialogs. The screen reader or keyboard focus does not always go into modal dialogs when they open, and the user may have to manually search for dialogs. Focus also often escapes from modal dialogs, e.g. while pressing the Tab key, navigating with a screen reader, or performing in-dialog actions (e.g. from the shopping cart). After closing a dialog, the focus does not always redirect to the button from which the dialog was opened. (WCAG 2.4.3)

- Some pages have extra focus stops (blanks, slash signs, etc.), and in some places, the screen reader reads content repeatedly. (WCAG 1.3.1, 2.4.3)

- The skip link on the main site does not move the focus to the main content at all, and the skip link on the checkout page moves the focus to a wrong place. (WCAG 2.4.3)

- There are also other focus issues on the service. Sometimes the focus shifts illogically when moving from one page to another or when moving from one modal step to the next. For some actions, such as filters and reviews, checking a checkbox, using the arrow keys inside a drop-down menu, or pressing the Tab key moves the focus to an unexpected location. In some situations, the screen reader focus loops between a few elements. (WCAG 2.4.3, 3.2.1, 3.2.2)

- Perceiving the structures and relationships of content with a screen reader can be laborious in some places. Information is not always clearly grouped (e.g. product cards and reviews). The lists are not always marked as lists programmatically, and the tables have accessibility shortcomings in some places. Sometimes several functionalities are read by the screen reader in the same step when navigating with the arrow keys, and sometimes the screen reader divides links and buttons into several parts with the arrow keys. There are not always word spaces between content parts with a screen reader and a braille display. (WCAG 1.3.1, 2.4.3)

- Not all the functional items have visible keyboard focus. (WCAG 2.4.7)

- On some pages, the reading order of content is illogical with a screen reader. The Next and Previous buttons on product listings are not understandable with a screen reader, because no part of the content is cut out of the view with a screen reader as it is visually. There are also problems with the reading order e.g. in the filter actions on the search results page, on the checkout page, and in product reviews. (WCAG 1.3.2)

Forms

- Some form fields or groups of fields do not always have their labels programmatically associated with them. Sometimes the label is illogically after the form field in the reading order. (WCAG 1.3.1, 1.3.2)

- At the checkout, the sequence numbers of individual radio buttons and the total number of radio buttons in a group are sometimes incorrectly indicated with a screen reader. (WCAG 1.3.1)

Other issues

- On the product search results page, the screen reader does not provide clear feedback on the updated number of results, and the previous number of search results is incorrectly displayed in the page title. (WCAG 4.1.3, 2.4.2)

- There are some individual links in the service whose accessible name does not match their visible name. This can make it difficult to use the links with voice control. (WCAG 2.5.3)

- The meaning of the shopping cart progress bar remains unclear with a screen reader. (WCAG 1.3.1)

How we have tested accessibility
The observations in this accessibility statement are based on a third-party assessment by Avaava Digital Oy of whether the service meets the legal requirements defined in the law.

This statement was prepared on December 5, 2025.
The statement was last updated on December 5, 2025.

Act on the Provision of Digital Services (306/2019) (FI/SV)