Accessibility Statement

Accessibility

We want our website to be accessible to everyone, regardless of ability. Accessibility is an important part of our work, and we follow the WCAG guidelines to ensure that as many people as possible can perceive, operate, and understand the content.

Report deficiencies and get help with accessibility issues

If you experience any difficulties using any part of the website, we encourage you to report this to us via email at kundservice.se@bubbleroom.com, so that we can correct it. Your feedback is valuable and helps us improve the user experience.

There are also other systems and services that can make it easier for you to use the website — for example, screen readers, magnification tools, or other assistive technologies that you can use to gain better access to the content.

How we have tested the website

We have engaged external experts from MetaMatrix to conduct a comprehensive accessibility analysis of our website. They have reviewed the site based on the requirements set out in the Act on the Accessibility of Certain Products and Services.

MetaMatrix was founded in 1999 with the ambition of creating inclusive and sustainable services that make life easier for everyone. They are experts in accessibility and digitalization.

Testing methods:

• Automated review using tools such as Accessibility Insights for Web and Siteimprove Accessibility Checker.

• Manual review including screen reader testing, keyboard navigation, content magnification, and responsiveness checks.

The most recent accessibility analysis was conducted on 2025-05-19.
The most recently updated accessibility statement for Bubbleroom was published on 2025-06-13.

---

Completed items

Below we list the accessibility requirements and levels that we already meet according to WCAG 2.1 guidelines:

• Pop-up functions can be handled and closed by all (R158) AA

• Document accessibility features (R172) AA

• Do not make instructions dependent on sensory characteristics (R123) A

• Create a design that works regardless of screen orientation (R153) AA

• Ensure that the cursor does not get stuck during keyboard navigation (R130) A

• Avoid flashing that can trigger epileptic seizures (R133) A

• Write clear and informative headings (R61) AA

• Do not perform unexpected changes when focusing (R143) A

• Do not perform unexpected changes when entering data (R144) A

• Be consistent in navigation, structure, and layout (R29) AA

• Define functions consistently (R146) A

• Consistent help WCAG 2.2 A

• Provide suggestions on how errors can be corrected (R149) AA

• Allow users to undo, correct, or confirm important transactions (R150) AA

• Do not ask for the same information multiple times WCAG 2.2 A

• Make login accessible WCAG 2.2 AA

• Ensure that code validates (R84) A

• Ensure accessibility in customer service (R173) A

• Develop the system so it can be operated using only a keyboard (R129) A

• Allow users to pause or disable motion (R132) A

• Ensure logical tab order (R136) A

• Make it possible to undo clicks (R161) A

• Provide text descriptions for all non-text content (R115) A

• Define in code the role of different page elements (R121) A

• Create flexible layouts that work when zoomed in or on small screens (R91) AA

• Use sufficient contrast between text and background (R126) AA

• Ensure text can be enlarged without problems (R127) AA

• Use text rather than images to display text (R128) AA

• Clearly indicate which field or element is in focus (R140) AA

• Ensure that elements with focus are visible WCAG 2.2 AA

• Indicate where an error has occurred and describe it clearly (R2) A

• Create clear and clickable field labels (R55) A

• Ensure custom components work with assistive technologies (R152) A

• Ensure assistive technologies can present off-screen messages (R164) AA

• Document accessibility features (R172) A

Areas we continue to work on internally

We are continuously working to improve the accessibility of our website and have identified certain areas where further actions are needed. Below you can read about the points we are currently working on:

• Present content in a meaningful order for everyone (R122) A

• Do not rely on color alone to convey information (R124) A

• Mark up common form fields in the code (R154) AA

• Use sufficient contrast in components and graphics (R156) AA

• Ensure it is possible to increase spacing between letters, lines, paragraphs, and words (R157) AA

• Allow users to adjust time limits (R131) A

• Offer the possibility to skip repetitive content (R75) A

• Write descriptive page titles (R135) A

• Write clear links (R5) A

• Offer users several different ways to navigate (R32) AA

• Enable voice control of buttons and controls (R162) A

• Indicate language changes in the code (R142) AA

• Provide alternatives if a recording consists only of audio or video (R116) A

• Ensure sufficiently large clickable areas WCAG 2.2 AA

• Specify the page’s language in the code (R141) A

• Respect the user’s preferences (R170) A

• Ensure accessibility in customer service (R173) A

Known accessibility issues

• Deficiencies in PDF documents created before 2025-06-28.

• Accessibility issues that we have raised with third-party suppliers: Triggerbee, Varbi, Avarda, ChatBot, and CookieBot.

• Image loading issues in campaigns created before 2025-06-28.

Report Bubbleroom.se to PTS

The Swedish Post and Telecom Authority (PTS) is the supervisory authority for this legislation.

If you are not satisfied with our response, or if you believe we are not meeting the legal requirements, you can report our website to PTS.

Report accessibility issues to PTS.