What is WCAG?
The Web Content Accessibility Guidelines (WCAG) are a set of technical standards that, when followed, improve the accessibility of web content, websites, and web applications for people with a wide range of disabilities. The WCAG standards fall under the European Accessibility Act (EAA).
The four main principles of WCAG is that content must be perceivable, operable, understandable, and robust.
How Does Doofinder Complies with WCAG?
Under Directive (EU) 2019/882 (European Accessibility Act), digital services that facilitate access to eCommerce and public-facing information must meet specific accessibility requirements. Doofinder, as a provider of search & discovery solutions used in eCommerce and digital platforms, falls indirectly within the scope of this directive.
Our services are subject to the EAA due to our role in enabling digital interactions on eCommerce websites and platforms serving consumers in the EU.
By 28 June 2025, Doofinder must ensure new deployments and contracts comply with the accessibility standards. Contracts and versions existing before 28 June 2025 have a transition period until 28 June 2030.
Doofinder is working actively to fully adapt our services to the EAA compliance for all our products, aligning with WCAG 2.2. Level A and Level AA, and the EU's harmonized accessibility standard EN 301 549.
Layer Compatibility with the European Accessibility Act
New or non-customized (default) layers are compatible with EAA and WCAG requirements. All WCAG-related updates developed by Doofinder will be automatically applied to these layers.
Customized layers must be updated manually to meet the Web Content Accessibility Guidelines.
What Is a Customized Layer?
A customized layer involves proactive edits to the Product Card Template. As a result, WCAG updates do not apply automatically to layers that include this type of manual customization.
Only default layers or newly created layers that have not been manually edited will automatically be kept up to date with the latest accessibility updates, no action is required for these layers.
For customized layers to comply with EAA requirements, you need to create a new layer and reapply and adapt your previous customizations, including changes to the Product Card Template and CSS.
Doofinder WCAG Compliance Checklist
In this section, you can review the latest WCAG Level A and Level AA accessibility requirements.
Refer to the following legend to understand what each status means in both tables:
| Status | Meaning |
|---|---|
| Compliant | Fully meets the success criterion. |
| In Progress, Partially Compliant | Meets the success criterion in some areas but is not yet fully compliant across all features and products. Work is actively ongoing. |
| In Progress, Not Compliant | Does not yet meet the success criterion but is currently being addressed. |
| Under Review | Currently being tested or evaluated. |
| Not Applicable | The success criterion does not apply to any of Doofinder’s features or products, so no action is required. |
The following checklist was last updated on June 30, 2025.
WCAG 2.1. Level A
| Success Criterion | Description | Status |
|---|---|---|
| 1.1.1 – Non-text Content | Text alternatives are provided for non-text content. | Compliant |
| 1.2.1 – Audio-only and Video-only (Pre-recorded) | A transcript is provided for audio-only content and a transcript or audio description is provided for video-only content. | Not Applicable |
| 1.2.2 – Captions (Pre-recorded) | Captions are provided for video with audio. | Not Applicable |
| 1.2.3 – Audio Description or Media Alternative (Pre-recorded) | A transcript and/or audio descriptions are provided for video with audio. | Not Applicable |
| 1.3.1 – Info and Relationships | Information and content relationships implied by formatting are communicated in text or in a way that works with assistive technology. | Compliant |
| 1.3.2 – Meaningful Sequence | The reading order of content is meaningful, no matter how a user accesses or consumes it. | Compliant |
| 1.3.3 – Sensory Characteristics | Instructions rely on more than one sense. | Compliant |
| 1.4.1 – Use of Color | Color is not the only way used to distinguish an element, convey meaning, indicate an action, or prompt a response. | In Progress, Partially Compliant |
| 1.4.2 – Audio Control | A mechanism is provided to control audio that plays on page automatically for more than three seconds. | Not Applicable |
| 2.1.1 – Keyboard | All functionality is operable using a keyboard (with exceptions). | In Progress, Partially Compliant |
| 2.1.2 – No Keyboard Trap | The focus does not get trapped on any element in keyboard-only navigation. | Compliant |
| 2.1.4 – Character Key Shortcuts | No single-key shortcuts are used, or a way to turn them off or change them is provided. | Compliant |
| 2.2.1 – Timing Adjustable | If a page has a time limit, users can turn the time limit off, adjust it, or extend it. | Not Applicable |
| 2.2.2 – Pause, Stop, Hide | User controls are provided for moving or dynamically changing content. | Not Applicable |
| 2.3.1 – Three Flashes or Below | No content flashes more than three times per second, or the flash is below flash thresholds. | Compliant |
| 2.4.1 – Bypass Blocks | When blocks of content are repeated on multiple pages, a mechanism is provided to bypass/skip them. | In Progress, Partially Compliant |
| 2.4.2 – Page Titled | Page titles clearly describe the page topic or page purpose. | Not Applicable |
| 2.4.3 – Focus Order | The tabbing order of the content is meaningful and supports operation. | In Progress, Partially Compliant |
| 2.4.4 – Link Purpose (In Context) | The purpose of each link can be determined from the link text alone or from the link text and its related context. | Compliant |
| 2.5.1 – Pointer Gestures | A single pointer alternative to complex pointer or touch gestures is provided. | Compliant |
| 2.5.2 – Pointer Cancellation | For functionality that is operated by a single pointer, a way to cancel the pointer input is provided. | Compliant |
| 2.5.3 – Label in Name | The programmatic name contains the text that is presented visually. | Compliant |
| 2.5.4 – Motion Actuation | For functions that are triggered by moving a device or by gesturing toward a device, an alternative way of triggering the response is provided. | Not Applicable |
| 3.1.1 – Language of Page | Each page has a human language assigned. | Compliant |
| 3.2.1 – On Focus | Interactive elements receiving focus do not trigger any functionality. | In Progress, Partially Compliant |
| 3.2.2 – On Input | Interactive elements receiving input do not trigger any functionality. | Compliant |
| 3.2.6 – Consistent Help | Help options provided are consistently available and in the same relative place throughout. | Under Review |
| 3.3.1 – Error Identification | When input error is detected, the user is notified and the error is described. | Compliant |
| 3.3.2 – Labels or Instructions | A persistent visible label and/or instructions are provided for elements that require user input. | Compliant |
| 3.3.7 – Redundant Entry | Information that the user has already entered during a process is made available to them. | Compliant |
| 4.1.2 – Name, Role, Value | All user interface components communicate their accessibility properties and actions to assistive technology. | Compliant |
WCAG 2.1. Level AA
| Success Criterion | Description | Status |
|---|---|---|
| 1.2.4 – Captions (Live) | Synchronized captions are provided for live videos containing audio. | Not Applicable |
| 1.2.5 – Audio Description (Pre-recorded) | If there is important visual content in a video that is not presented in the accompanying audio, an audio description is provided. | Not Applicable |
| 1.3.4 – Orientation | Screen orientation is not restricted unless the orientation is considered essential. | Compliant |
| 1.3.5 – Identify Input Purpose | For each form field collecting user information, the purpose of the field is programmatically declared. | Compliant |
| 1.4.3 – Contrast (Minimum) | The contrast ratio between regular-sized, non-decorative text and its background is at least 4.5:1. | In Progress, Not Compliant |
| 1.4.4 – Resize Text | Text can be resized up to 200% without loss of content or function. | Compliant |
| 1.4.5 – Images of Text | Aside from a few specific exceptions, there are no images of text. | Compliant |
| 1.4.10 – Reflow | Content presentation is responsive and doesn’t require scrolling in two dimensions. | Compliant |
| 1.4.11 – Non-Text Contrast | The contrast ratio between non-text elements (including any states) and their background is at least 3:1. | In Progress, Not Compliant |
| 1.4.12 – Text Spacing | Text spacing can be overridden to improve the reading experience. | Compliant |
| 1.4.13 – Content on Hover Focus | When additional content is presented on hover or on focus, the new content is persistent and dismissable. | Compliant |
| 2.4.5 – Multiple Ways | There is more than one way to reach each page. | Not Applicable |
| 2.4.6 – Headings and Labels | Headings and labels are clear and descriptive. | Compliant |
| 2.4.7 – Focus Visible | Keyboard focus is clear and visible. | In Progress, Partially Compliant |
| 2.4.11 – Focus Not Obscured (Minimum) | When an actionable element receives focus, at least a portion of it remains visible. | Compliant |
| 2.5.7 – Dragging Movements | If any part of a website requires a dragging movement, an alternative means of dragging, such as tapping or clicking, is provided. | Compliant |
| 2.5.8 – Target Size (Minimum) | The size of a target is at least 24 by 24 CSS pixels (with exceptions). | Compliant |
| 3.1.2 – Language of Parts | Assistive technology can distinguish and reflect when the human language on a page changes. | Compliant |
| 3.2.3 – Consistent Navigation | Navigational elements are consistently displayed, including their location and the order of their content. | Compliant |
| 3.2.4 – Consistent Identification | Components with the same functionality are consistently identified. | Compliant |
| 3.3.3 – Error Suggestion | Users receive helpful/specific suggestions when they make errors. | Compliant |
| 3.3.4 – Error Prevention (Legal, Financial, Data) | When users enter financial or legal data, submissions are reversible, and data is checked and confirmed before submission is finalized. | Compliant |
| 3.3.8 – Accessible Authentication (Minimum) | When a cognitive function test is used to authenticate a user, an alternative way to authenticate, or a help mechanism to complete the authentication is provided. | Not Applicable |
| 4.1.3 – Status Messages | Status messages can be presented to the user by assistive technology without receiving focus. | Not Applicable |