Digital Accessibility statement

IKEA Retail (Ingka Group) - As a retail company that is committed to the mission of offering a wide range of well-designed functional home furnishing products at low prices for the many people, we are continuously improving the accessibility of our digital experiences, systems and services for our diverse customer base, including those with disabilities, in accordance with Law 11/2023, of 8 May, transposing EU Directives on accessibility.

We work continuously to improve digital accessibility, and we do this by implementing global standards including the Web Content Accessibility Guidelines (WCAG).

As a company, IKEA Retail (Ingka Group) is committed to a human-centric approach in the use of technology for the benefit of the many.

Conformance status 

WCAG provides guidance on how to make websites easier to use for people with disabilities. There are three levels of conformance and IKEA Retail (Ingka Group) aims to achieve WCAG 2.1 Level AA.

We have taken significant steps to make our digital experiences more inclusive. We are also working with accessibility experts and people with disabilities to test and give feedback.

We know from several accessibility assessments that we still have a few things to improve. Please note that this does not mean that users will be unable to access and use the digital products, but it indicates that we still have some work to do – and we are working on it!

In full transparency, some examples of non-accessible content are: 

IKEA.com

• WCAG 1.1.1   Non-text content such as images does not have a text alternative that serves an equivalent purpose.
• WCAG 1.2.2   Pre-recorded video content does not have captions.
• WCAG 1.2.5   Pre-recorded video content does not have an audio description.
• WCAG 1.3.1   Information, structure, and relationships conveyed through visual presentation are not available to assistive technologies.
• WCAG 1.3.2   The meaningful reading sequence of content cannot be determined programmatically.
• WCAG 1.3.3   Instructions rely solely on sensory characteristics such as shape, colour, or position.
• WCAG 1.3.4   Content is locked to a specific display orientation and does not adapt to user preference.
• WCAG 1.3.5   Input fields that collect personal data do not identify their purpose to assistive technologies.
• WCAG 1.4.1   Colour is used as the only visual means of conveying information or indicating an action.
• WCAG 1.4.10   Content does not reflow to a single column when zoomed to 400%, requiring two-dimensional scrolling.
• WCAG 1.4.11   Non-text user interface components or graphical objects do not have sufficient contrast against adjacent colours.
• WCAG 1.4.12   Text spacing cannot be adjusted without loss of content or functionality.
• WCAG 1.4.13   Additional content that appears on hover or focus cannot be dismissed, hovered, or persists long enough to be read. 
• WCAG 1.4.3   Text does not have sufficient colour contrast against its background.
• WCAG 1.4.4   Text cannot be resized up to 200% without loss of content or functionality.
• WCAG 2.1.1   Not all functionality is operable through a keyboard interface alone.
• WCAG 2.1.2   Keyboard focus can become trapped within a component with no way to move it away. WCAG 2.2.1   Time limits cannot be turned off, adjusted, or extended by the user.
• WCAG 2.2.2   Moving, blinking, or scrolling content cannot be paused, stopped, or hidden by the user. WCAG 2.4.1   No mechanism is available to skip blocks of content that are repeated across pages.
• WCAG 2.4.11   The keyboard focus indicator is not entirely visible during interaction.
• WCAG 2.4.2   Pages do not have descriptive titles that identify their topic or purpose.
• WCAG 2.4.3   Keyboard focus order does not follow a logical and meaningful sequence.
• WCAG 2.4.4   The purpose of links cannot be determined from the link text alone or from its programmatic context.
• WCAG 2.4.5   Only one way is provided to locate a page within a set of pages. WCAG 2.4.6   Headings and labels are not descriptive enough to convey their topic or purpose. 
• WCAG 2.4.7   Keyboard focus indicator is not visible.
• WCAG 2.5.1   Functionality requiring multi-point or path-based gestures cannot be operated with a single pointer.
• WCAG 2.5.2   Actions triggered by a single pointer cannot be aborted or undone before completion.
• WCAG 2.5.3   The accessible name of a component does not contain the visible text label.
• WCAG 2.5.7   Functionality that requires a dragging movement has no accessible single-pointer alternative.
• WCAG 2.5.8   Interactive targets do not meet the minimum required size or offset from neighbouring targets.
• WCAG 3.1.1   The default language of the page is not identified in the page markup.
• WCAG 3.1.2   Passages or phrases in a language other than the default are not identified in the markup. WCAG 3.2.1   A change of context occurs automatically when a component receives keyboard focus. WCAG 3.2.3   Navigation mechanisms are not presented in a consistent order across pages.
• WCAG 3.2.4   Components with the same functionality are not identified consistently across pages.
• WCAG 3.2.6   Help mechanisms are not provided or are not presented in a consistent location across pages.
• WCAG 3.3.1   Input errors are not automatically detected and described to the user.
• WCAG 3.3.2   Labels or instructions are not provided for content that requires user input.
• WCAG 3.3.3   When an input error is detected, suggestions for correction are not provided.
• WCAG 3.3.4   Submissions that involve legal or financial commitments cannot be checked, confirmed, or reversed.
• WCAG 4.1.2   Interactive elements do not have accessible names, roles, or programmatically exposed state information.
• WCAG 4.1.3   Status messages are not programmatically determined and therefore not announced by assistive technologies. 

The IKEA app

• WCAG 1.1.1   Non-text content such as images does not have a text alternative that serves an equivalent purpose.
• WCAG 1.2.1   Pre-recorded audio-only or video-only content does not have an equivalent text or audio alternative.
• WCAG 1.2.3   Pre-recorded video content does not have an audio description or full text alternative.
• WCAG 1.2.5   Pre-recorded video content does not have an audio description.
• WCAG 1.3.1   Information, structure, and relationships conveyed through visual presentation are not available to assistive technologies. 
• WCAG 1.3.2   The meaningful reading sequence of content cannot be determined programmatically.
• WCAG 1.4.1   Colour is used as the only visual means of conveying information or indicating an action.
• WCAG 1.4.11   Non-text user interface components or graphical objects do not have sufficient contrast against adjacent colours.
• WCAG 1.4.2   Audio that plays automatically for more than three seconds cannot be paused, stopped, or muted.
• WCAG 1.4.3   Text does not have sufficient colour contrast against its background.
• WCAG 1.4.4   Text cannot be resized up to 200% without loss of content or functionality.
• WCAG 2.1.1   Not all functionality is operable through a keyboard interface alone.
• WCAG 2.1.2   Keyboard focus can become trapped within a component with no way to move it away. WCAG 2.2.1   Time limits cannot be turned off, adjusted, or extended by the user.
• WCAG 2.4.11   The keyboard focus indicator is not entirely visible during interaction.
• WCAG 2.4.3   Keyboard focus order does not follow a logical and meaningful sequence.
• WCAG 2.4.4   The purpose of links cannot be determined from the link text alone or from its programmatic context.
• WCAG 2.4.5   Only one way is provided to locate a page within a set of pages.
• WCAG 2.4.6   Headings and labels are not descriptive enough to convey their topic or purpose.
• WCAG 2.5.1   Functionality requiring multi-point or path-based gestures cannot be operated with a single pointer.
• WCAG 2.5.3   The accessible name of a component does not contain the visible text label.
• WCAG 2.5.8   Interactive targets do not meet the minimum required size or offset from neighbouring targets.
• WCAG 3.2.1   A change of context occurs automatically when a component receives keyboard focus.
• WCAG 3.2.2   Changing the setting of a user interface component triggers an automatic change of context. 
• WCAG 3.2.3   Navigation mechanisms are not presented in a consistent order across pages.
• WCAG 3.2.4   Components with the same functionality are not identified consistently across pages. WCAG 3.3.1   Input errors are not automatically detected and described to the user.
• WCAG 3.3.2   Labels or instructions are not provided for content that requires user input.
• WCAG 3.3.3   When an input error is detected, suggestions for correction are not provided.
• WCAG 3.3.4   Submissions that involve legal or financial commitments cannot be checked, confirmed, or reversed.
• WCAG 3.3.7   Previously entered information is not automatically re-entered in repeated fields within the same session.
• WCAG 4.1.2   Interactive elements do not have accessible names, roles, or programmatically exposed state information.
• WCAG 4.1.3   Status messages are not programmatically determined and therefore not announced by assistive technologies. 

Local web products

We have two locally purchased solutions in the ikea website in Spain that have some deficiencies with respect to the new legal requirements of digital accessibility. We are working on improving these to make them fully compliant with the new legislation.

1. Customer Support Invoice Request Page
   This is a web form to request an invoice or create a duplicate invoice upon the customer´s request.  Legal and fiscal information is captured in a web form, allowing our Remote Contact Centre to create and share a new invoice or generate a duplicate.
2. Spain Affiliation program
   This is a private virtual network product to create, manage, and scale our Partner Programs under our own brand name.  Affiliates can log into ikea.es and then can navigate to a website managed by an external partner. 

We are actively working to address these issues as part of an ongoing effort to improve the accessibility of our digital experiences, systems, and services.

Get in touch

Choose one of the following ways to get in touch with us.

Drafting of this accessibility statement

This declaration is based on the evaluations completed by our expert accessibility teams with the support of frequent evaluations from our accessibility providers.

The statement was prepared on 2026-06-28 and last reviewed and updated on 2026-06-28.