Hesburger Application – Accessibility statement

This accessibility statement explains how the Hesburger application strives to comply various accessibility regulations and how you can provide us feedback on accessibility matters.

General Information

The Hesburger application (hereinafter “Application”) is owned and provided for use by Burger-In Oy (hereinafter “Hesburger”), Business ID: 2031967-6, Address: Linnankatu 34, 20100 Turku, Finland.

This statement was created on 12.6.2025.

Accessibility Status of the Application

The Hesburger application is used across multiple countries. Our accessibility approach complies with both the Finnish Act on the Provision of Digital Services 306/2019 and EU-wide accessibility standards, including the European Accessibility Act (EAA).

Our goal is to achieve WCAG 2.2 AA level in the accessibility of our digital services. The Application partially meets accessibility requirements with the deficiencies described in this statement. Work is underway to correct the service's accessibility deficiencies, and we will update the list as they are resolved.

The information in this statement is based on an accessibility assessment conducted by an external expert organization in Finland.

Non-accessible content

The content listed below is not compliant with the regulations.

General

  • The Application content does not rotate according to the device orientation. (WCAG 1.3.4)
  • The Application content does not adapt to the operating system's text size settings on iOS devices at all. On Android devices, most content adapts, but some content does not respond properly to text size settings, including product descriptions and some headings. (WCAG 1.4.4)
  • Some content colour combinations have contrast problems, including blue text on a white background, and the app shows text over background images. The visual detection of some texts, icons, and example content in input fields may be difficult because of this. (WCAG 1.4.3, 2.4.7)
  • Colour has been used in some places as the only way to convey information. Text links and some of the Application's button interactivity is expressed only by colour. It can be challenging for users to identify which elements are clickable. This can prevent smooth use of the service or lead to important functions being overlooked. (WCAG 1.4.1, 1.3.1 and 2.4.4)
  • Link texts are not always clearly expressed, so users cannot always understand with certainty from the text where the link leads. For example, the receipt number shown in user’s order history works as an external link for giving feedback. Using assistive technology is more difficult when the link destination or purpose cannot be clearly determined from the link text. (WCAG 2.4.4)
  • Some elements have shortcomings in text alternatives, or they are not completely unique. For example, the Buy button’s identifiers may be the same if the product price is the same, and the identifiers do not always show which product is being purchased. This particularly makes it difficult to use screen readers and other assistive technologies, when users cannot clearly identify what the button does or what it targets. (WCAG 1.1.1 and 2.5.3)
  • Input fields do not have actual labels, but the field's purpose is presented only as a placeholder text inside the input field. This can cause challenges in interpretation for users with assistive technology, because the field's purpose may not be conveyed technically correctly. Additionally, the placeholder text in the field disappears when the user types, which can make it difficult to remember the field's meaning. (WCAG 1.3.1)
  • Changes in user interface state are not always presented accessibly. Users do not awlays receive information about changes happening in the user interface and their content. For example, the app does not communicate successful login, addition of a new product to the shopping cart, or an error in the right way as a status message to screen readers, so users may be uncertain about the success of their actions. (WCAG 4.1.3)
  • The app has parts that cannot be used with a keyboard because focus cannot be moved to them. For example, the front page quick selection button, which shows the user’s bonus card. (WCAG 2.1.1)
  • The app has some links/buttons that have a smaller than recommended touch area. This can cause challenges in using the app on touch screens, especially for users with motor limitations, as a small target area requires precise finger dexterity. (WCAG 2.5.8)
  • Keyboard focus visibility is not sufficient in all parts and the focus state contrast does not stand out clearly from the background. This makes it difficult for keyboard users to move around the user interface because the focus location is not easily detectable. (WCAG 2.4.7)
  • Keyboard focus does not always stay visible to the user. For example, focus may move to hidden elements in the shopping cart or to background elements when a modal is open. (WCAG 2.4.7)
  • Keyboard and screen reader focus moves unexpectedly in some places. For example, after a modal closes, focus does not return to the point where the modal was opened, but can move unexpectedly to the beginning of a page. This makes smooth navigation with assistive technology difficult. (WCAG 2.4.3)
  • The Application may display inactive selection buttons that are interactive with keyboard and screen reader. For example, if a product is not in the selected restaurant's selection at that time. This can confuse and make the user interface difficult to understand, because removed elements should not be interactive. (WCAG 4.1.2)
  • In product listings, selection buttons have multiple focusable elements with keyboard and screen reader, of which only some make the selection. This can lead to a heavy navigation experience or confuse the user. (WCAG 2.4.3)
  • Some of the Application's input fields use solutions that are problematic from an accessibility perspective. (WCAG 1.3.1)

iOS Application

  • When navigating forward with the Tab key, the app crashes or closes unexpectedly. This makes keyboard navigation difficult to use and causes a significant accessibility problem for users who cannot use other input methods. (WCAG 2.1.1)
  • Coupons are not fully usable with screen readers. When the user uses a coupon’s additional selection buttons with a screen reader and then opens the "Show at checkout" view or continues to pre-order, the screen reader gets stuck with its focus on content behind the modal. The user cannot navigate within the modal or close it, which prevents placing an order through the app. If the additional selection buttons are not used, coupons work correctly. (WCAG 2.4.3, 1.3.2)
  • The payment card information input field is not usable with screen readers. When a screen reader is in use, focus automatically moves to the expiration date, and the card number focus does not activate. This prevents people who only use screen readers from entering payment information. (WCAG 2.1.1, 1.3.2)
  • In keyboard navigation, moving through content with Tab key presses varies and is not consistent. Sometimes you can move forward with the Tab key, sometimes only with arrow keys. (WCAG 2.4.3)
  • Meal editing functions are not fully usable with keyboard. When the user selects an additional product, they cannot select the quantity because the quantity input field's plus and minus buttons are not accessible through keyboard navigation. Additionally, the "Add same product with different options" button works with keyboard, but the editing options for the added product row are not visible or accessible without removing the product and reselecting it. (WCAG 2.1.1, 1.3.2)
  • The Application’s "Join Bonus Club" button is not accessible through keyboard navigation. This prevents users who use only keyboard from registering for the service through the Application. (WCAG 2.1.1)

Android Application

  • Modals cannot be closed with the keyboard, as modals do not have close buttons and you cannot exit modals with keyboard commands. (WCAG 2.1.1 and 2.1.2)
  • Keyboard users get trapped in on-screen visible elements because the Application does not carry focus to content that remains outside the visible screen area. (WCAG 2.1.2)
  • The Application does not have clear navigation areas set that would make it easier to find targets. For example, Buy and Continue buttons are always located at the bottom of the screen, and reaching them requires long navigation through the extensive "Select products" listing. This causes an unreasonable burden for assistive technology users. (WCAG 2.4.7)
  • The restaurant list filtering window is located at the bottom of the page in reading and focus order, which is why it is difficult to detect with screen readers and difficult to access with a keyboard. (WCAG 1.3.2, 2.4.3)
  • In situations with input field errors, the user is not given clear textual feedback about what is wrong in the form or what needs to be corrected. For example, when a user tries to register with a phone number that has been given in a wrong format. This makes it difficult for users to identify and correct errors in forms. (WCAG 3.3.1)
  • Toggle buttons lack a clear text identifier that would tell the user what the approval concerns (e.g., approving email and text message marketing). This particularly weakens screen reader users' ability to understand the buttons' purpose. (WCAG 4.1.2)

Other considerations

  • The Application has some repeated content and navigation paths. This can make it difficult to use with screen readers and other assistive tools. For example, users must go through several pages to find the login option. Also, when looking at food items, the different meal sizes create extra content that users need to navigate through.

Content Not Subject to Accessibility Requirements

The Application uses third-party map services including Google Maps, Apple Maps, and Petal Maps. We cannot guarantee the accessibility of third-party services. However, we also provide the same location information in text format for all users.

Correcting Deficiencies

The identified accessibility deficiencies are being addressed alongside other development and maintenance work. Our goal is to complete all corrections by the end of 2025. The list of accessibility deficiencies identified in this statement will be updated as they are resolved.

Providing Feedback and Contact Information

If you notice accessibility deficiencies, please first provide feedback to us, the service provider Burger-In Oy. We will reply within 14 days.

You can send feedback via email to: accessibility@hesburger.fi

Supervisory Authority

The Finnish Transport and Communications Agency Traficom supervises the implementation of accessibility requirements in Finland. If you are not satisfied with the response you received or do not receive a response at all within 14 days, you can file a report on Traficom's website. The link opens in new window. The Finnish Transport and Communications Agency Traficom's website provides detailed information on how to file a report and how the matter will be processed.

For users in Finland:
Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
P.BOX 320
FI-00059 TRAFICOM
www.saavutettavuusvaatimukset.fi/en (link opens in a new window)
saavutettavuus(at)traficom.fi
Tel. +358 29 534 5000

For users in other EU countries:
If you are not satisfied with the response you received to your feedback, or you do not receive a response at all within 14 days, you can file a report to your local supervisory authority. Users in other EU countries can contact their respective national supervisory authorities regarding accessibility compliance. Each EU member state has designated bodies that monitor and enforce accessibility requirements under the EU Web Accessibility Directive.