Accessibility Statement for the K-Ruoka mobile application

This service is provided by Kesko PLC. 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.

Accessibility Statement in Finnish: K-Ruoka-sovelluksen saavutettavuusseloste

Accessibility Statement in Swedish: K-Ruoka mobilappens tillganglighetsutlatande All accessibility statements for K-Ruoka 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 via the web form

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

General

• The app cannot be used in landscape orientation. (WCAG 1.3.4)
• In some views, the focus order of the screen reader does not correspond to the visual order in which the elements are presented, and the order can also be internally inconsistent if the screen reader user changes the navigation method. On Android, the focus order varies between different views. (WCAG 1.3.2, 2.4.3)
• The service includes videos that do not have audio description or a clearly expressed equivalent. (WCAG 1.2.3 and 1.2.5)
• There are some issues with focus control. In the iOS app, VoiceOver focus does not always go to the beginning of a new view when moving from one view to another. In some places, after typing, the focus of the screen reader does not stay in the text field after the user has hidden the keyboard. (WCAG 2.4.3)
• When there is floating but fixed content on the screen, the keyboard or assistive technology focus may go under such floating content in some scenarios. In this case, the sighted user will not be able to see the focus, and screen readers (especially VoiceOver) may misread the content. WCAG 2.4.11)
• VoiceOver may activate the wrong item, or it may not activate the item at all with a double-tap. This can happen, for example, when the visual focus indicator is hidden under other content and the user tries to activate the focused content. The problem may also be related to situations in which the visual view does not move with the screen reader focus. You can try activating the element after scrolling down the view (VoiceOver: three-finger swipe up). (WCAG 2.1.1, 2.4.3)
• In some long views, VoiceOver focus jumps uncontrollably. You can try scrolling the screen to resolve the issue. (WCAG 2.4.3)
• VoiceOver also does not always wrap text correctly. Sometimes a large amount of visually grouped information is read by a screen reader at once, and sometimes line-breaking by VoiceOver is too dense. In some places, the grouping of information is otherwise unclear with assistive technologies. Sometimes VoiceOver repeats information unnecessarily or reads extra noise. (WCAG 1.3.1)
• There are functionalities in the application that are not correctly marked as functionalities (e.g. a button not marked as a button, a link not marked as a link, or a text field not marked as a text field). (WCAG 4.1.2, 1.3.1)
• The app contains images with important information that do not have a text alternative, or the text alternative is inaccurate. These include, for example a picture of the user’s Plussa card and some of the information on the product packaging (e.g. the Heart Symbol). (WCAG 1.1.1)
• The screen reader user does not always receive sufficient information about changes on the screen, such as errors. In some places, the status messages contain English text in the Finnish application. On the other hand, when typing in a text field with TalkBack, assistive messages are sometimes too intense and interfere with typing (writing the name of a shopping list). Sometimes VoiceOver also interrupts reading a status message because of a competing message. (WCAG 4.1.3)

Viewing and managing products

• The language of the descriptions of the products in English and Swedish is not marked correctly in the Finnish iOS app, which means that VoiceOver reads them with the wrong pronunciation. You can change the language in the screen reader settings. (WCAG 3.1.1)
• Additional actions in the shopping list open modal dialogs, but the focus of the TalkBack screen reader does not automatically move to them. The modal dialogs also have extra and unclear focus stops or ghost buttons. (WCAG 2.4.3, 1.3.1)
• The tabs in the Benefits section are only focusable on Android when they are visually visible. (WCAG 2.4.3)

Buying

• In the confirmation view for adding a new card, the visual label of the continue button does not match the invisible, programmatic name of the button, which can cause difficulties for sighted voice control users. (WCAG 2.5.3)
• The form does not always provide a known correction suggestion for errors made by the user. (WCAG 3.3.3)

Other issues

• The product request form for an individual store does not have a standard way to hide the virtual keyboard with VoiceOver screen reader. Try double-tapping some non-functional text to hide the keyboard. (WCAG 2.1.2)
• After purchase, when selecting feedback emojis, feedback is sent without separate user confirmation. In addition, VoiceOver doesn't read the thank you message in real time. (WCAG 3.2.2, 4.1.3)

The shortcomings listed here are intended to be corrected by May 31, 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 was launched in September 2015.

This statement was prepared on May 30, 2025.

The statement was last updated on November 24, 2025.

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

Web accessibility website