Your cart

Your cart is empty

Your shopping cart is still empty. Find your favorites from our wide selection

1. General

This accessibility statement applies to the Topaz Oy online store at shop.saarentaika.com. The statement was prepared on 03.03.2025.

Topaz Oy strives to ensure the accessibility of its online store in accordance with the Act on the Provision of Digital Services (306/2019). Our goal is to ensure that as many users as possible – including people with various functional limitations and using assistive devices – are able to use the service smoothly.

2. Service accessibility status

The online store does not yet meet the WCAG 2.1 level A and AA criteria in the following areas. We are constantly developing the accessibility of the online store and will strive to correct the identified deficiencies as soon as possible.

3. Unreachable content

The WCAG 2.1 criteria listed below are not currently met on shop.saarentaika.com. We will also briefly describe the most common deficiencies that we have identified, which we are committed to correcting:

  1. WCAG 1.1.1 – Non-textual content
    1. Some of the online store's video and image material lacks text equivalents (alt texts). This may hinder the ability of users using screen readers to understand the content of the image.
    2. Not all buttons have visible text or an aria-label or similar attribute, so screen readers and other assistive devices do not receive information about what this button does.
  2. WCAG 1.2.2 – Subtitles (saved)
    1. Some videos are missing subtitles.
  3. WCAG 1.3.1 – Information and Relationships
    1. The website does not use clear structure and heading tags (for example, H1, H2, etc.), which can make it difficult to understand the content using assistive devices.
    2. Some form elements are not grouped correctly, which may make it difficult to visualize their relationship using assistive tools.
    3. The checkout does not clearly mark mandatory fields, which may make it difficult to understand them.
  4. WCAG 1.3.5 – Define the purpose of the input
    1. Some form elements lack autocomplete clarification, which may make it difficult to automatically fill the form with the correct information.
  5. WCAG 1.4.3 – Minimum contrast requirements
    1. The contrast between text and background color does not always meet the required level. Low-contrast elements can make content difficult to read for people with low vision.
  6. WCAG 1.4.11 – Contrast of non-text content
    1. The outer edges of form elements do not always meet the required level. Low-contrast elements can make it difficult for people with low vision to perceive the content.
  7. WCAG 1.4.13 – When pointing or targeting content
    1. Submenus are only opened by mouse hover, but cannot be closed without the mouse pointer. Additional content that opens by hover or focus must be able to be closed by the user without moving the pointer or changing the keyboard focus. In this implementation, closing requires a mouse, so the criterion is not met.
  8. WCAG 2.1.1 – Keyboard
    1. Not all functions of the online store can be used with just the keyboard. For example, certain elements do not receive focus when using the keyboard.
  9. WCAG 2.1.2 – No keyboard traps
    1. Some modal dialogs (for example, popups) can create a situation where keyboard focus gets stuck inside the element or cannot be easily closed.
    2. Some site elements (for example, a review section on a product page) can create a situation where the keyboard focus gets stuck inside the element or cannot be easily closed.
  10. WCAG 2.4.2 – Page Headings
    1. Some pages (for example, the search page) do not have a descriptive or informative title.
  11. WCAG 2.4.4 – Link Intent (in Context)
    1. Some links lack a clear description of where the link leads to, such as simply “More information” without any additional context for screen readers.
    2. Some buttons lack a clear description or visible text explanation of what function the button performs.
  12. WCAG 2.4.6 – Headings and labels
    1. The online store's pages do not use clear and descriptive headings or labels everywhere. This impairs the site's navigability.
  13. WCAG 2.4.7 – Visible alignment
    1. The focus indicator used may be incomplete or too subtle, making it difficult for keyboard users to see where the focus is on the page.
  14. WCAG 2.5.3 – Name tag in name
    1. In some form elements, the text intended for screen readers and the text displayed differ from each other.
  15. WCAG 2.5.8 – Minimum item size and spacing
    1. Some of the functional objects do not meet the minimum size requirement (24 × 24 px) or minimum spacing between them. This can make targeting and activation difficult, especially for keyboard or touchscreen users without assistive devices.
  16. WCAG 3.1.2 – Language of Elements
    1. Some of the content on the site appears in the wrong language (for example, a Finnish site has English phrases) without a section-specific language identifier. This can make it difficult for screen readers and other assistive devices to interpret the content.
  17. WCAG 3.3.1 – Error Identification
    1. When entering incorrect credentials in the login form, the user is not shown an error message or other feedback. This can prevent the user from understanding what went wrong and continuing the login process.
  18. WCAG 3.3.2 – Labels and instructions
    1. Some form and selection elements are missing explanatory text. This can make forms difficult to use with screen readers and other assistive devices.
    2. Some intentionally hidden form elements are missing their hidden tag (e.g. aria-hidden). This can make forms difficult to use with screen readers and other assistive devices.
  19. WCAG 4.1.1 – Syntax
    1. The site's HTML code contains structural errors, such as duplicate ID values and serious markup errors, that violate the requirement that content be parsed reliably. Such errors can prevent screen readers and other assistive devices from processing the page content correctly.
  20. WCAG 4.1.2 – Name, Role, Value
    1. Some form elements or buttons do not contain a clear name, role, or value, making it impossible for a screen reader to convey their purpose to the user.
    2. Some button text is missing, so these elements are not visible.

Deviation based on unreasonable burden:

We are not currently claiming an unreasonable burden. We have begun development work to address the shortcomings and will update this statement as accessibility improves.

4. Alternative ways of doing business

If you are unable to use all the functions of the shop.saarentaika.com online store or you have difficulties, for example, placing an order, the following options are available:

5. Providing feedback and contact information

We welcome feedback on the accessibility of our online store and development ideas to improve it. You can send feedback in the following ways:

We will respond to feedback within 14 days.

6. Supervisory authority

If you notice any accessibility issues on the site, please first provide feedback to us, the site administrator. If you are not satisfied with the response you receive or do not receive a response within two weeks, you can file a report with the supervisory authority. In Finland, the supervisory authority is the Regional State Administrative Agency of Southern Finland:

Regional State Administrative Agency of Southern Finland, Accessibility Monitoring Unit

7. Preparing and updating the report

  • The report was prepared on June 26, 2025 .
  • The report was last updated on June 26, 2025 .
  • Method of evaluation: external evaluator.
  • We are actively developing the online store based on the feedback we receive and any identified shortcomings.

8. Development plans

We are committed to improving the accessibility of the shop.saarentaika.com online store. The following development activities are underway or about to begin:

  • Text equivalents and video subtitles: Adding missing alt texts to images and aria-label attributes to all buttons, and ensuring that all videos receive subtitles.
  • Structure and heading hierarchy: Review and correct H1–H6 headings, group form fields logically, and clearly mark required fields.
  • Defining the purpose of the input: Define autocomplete attributes for form elements and add the necessary aria attributes (e.g. aria-required, aria-describedby).
  • Contrast Improvement: Updated text-to-background contrast ratios and form and non-text element margins to meet WCAG 1.4.3 and 1.4.11 requirements.
  • Hover and focus content management: Implement submenus so that they can be closed with both the mouse and keyboard or focus.
  • Keyboard usability: Ensuring that all interactive elements receive focus and that modal dialogs do not create keyboard traps.
  • Page-specific titles and link descriptiveness: Add descriptive <title> elements, check the clear text of the links, and utilize aria-describedBy contexts if necessary.
  • Focus indicator visibility: Improves the visual distinction of focus when using the keyboard (e.g., highlight frame, flicker).
  • Size and spacing of functional items: Ensure that all interactive elements are at least 24×24 px and have sufficient spacing between each other.
  • Section language: Define the appropriate lang attributes for the different language sections of the page.
  • Error recognition and guidance: Show clear error messages, for example when logging in, and add help texts and help texts to form fields (WCAG 3.3.1–3.3.2).
  • Hidden element markings: Add aria-hidden to hidden elements and ensure they don't distort the parsing.
  • HTML structure cleanliness: Fix duplicate IDs and other markup errors so that content can be parsed reliably (WCAG 4.1.1).
  • Name, role, and value: The missing name, role, and value attributes are added so that screen readers can receive complete information about the elements (WCAG 4.1.2).

We aim to complete these fixes in phases throughout 2025. Some of the actions are awaiting updates from third-party developers. We will update this statement as accessibility improves.

Customer feedback