Accessibility
ThemeWare® is already accessible according to the criteria of PageSpeed Insights, as you can see under the following link:
Note: Shopware currently does not yet fulfil the new WCAG 2.1 AA requirements. However, Shopware is already working on the necessary adjustments of the storefront and has already implemented some improvements. The aim of version 6.7 is to be fully prepared before the legally prescribed deadline of the Barrier-Free Accessibility Act.
German implementation of the EAA (European Accessibility Act)
The implementation of the Directive (EU) 2019/882 of the European Parliament and of the Council on the accessibility requirements for products and services (in German "Barrierefreiheitsstärkungsgesetz" – BFSG) will be transposed into national law by 28 June 2025.
Shopware plans to provide the necessary technical adaptations in Shopware Core by then. We will of course support these adaptations, optimise ThemeWare® and offer additional accessibility configurations in ThemeWare® for Shopware 6.7 if required.
In addition, we will provide instructions, tips and hints for the individual implementation of accessibility requirements to make the process as smooth as possible for you.
In Shopware 6.6, it will also be possible to activate the ACCESSIBILITY_TWEAKS feature flag to fulfil the new requirements. This feature flag will also be supported by ThemeWare® update in an upcoming update.
Tip: For the latest announcements on planned releases, regularly check the "News and Announcements" block in the ThemeWare® Service Portal.
Making your website accessible
The theme itself only has a small part to play in the accessibility of your shop. Similar to SEO and PageSpeed, a large part is influenced by user-generated content, over which themes have no direct influence.
With ThemeWare®, we can do a lot for you, but not everything - because accessibility also depends on your settings and content. You are responsible for aspects such as alt texts, sufficient colour contrasts, accessible audio and video content, understandable abbreviations and a sensible heading structure. We have summarised the most important information for you so that you are well prepared.
1-click solutions (overlays) for accessibility
1-click solutions are currently being advertised by many providers. We recommend Eye-Able® for this. You can test Eye-Able® for 30 days free of charge and get an additional month for free with the keyword "ThemeWare".
Colour contrasts
When configuring colours, ensure that there is sufficient contrast between the text and the background. Too little contrast makes it difficult to read and can be problematic for people with visual impairments.
Accessible audio and video
Since audio and video files are difficult for people with visual or hearing impairments to use, the accessibility of this content is all the more important. Provide alternative content such as descriptive transcripts.
Accessible images
Check all images for meaningful
alttexts. Exception: purely decorative images – these should have an emptyalt=""attribute so that screen readers skip them.
Accessible texts
Use easy-to-understand language and avoid complicated words and sentences.
Accessible system
Keep Shopware and your theme, as well as all other extensions used, up to date.
1-click solutions (overlays) for accessibility
Numerous free and paid tools help you to test accessibility. To provide you with the best possible support, we have brought Eye-Able® on board as an expert who will guide you with innovative tools and clear recommendations. You can test Eye-Able® for 30 days free of charge and get an additional month for free with the keyword "ThemeWare".
Colour contrasts
When configuring colours, ensure that the contrast between text and background is sufficiently high (at least 4.5:1). It is best to use online tools (e.g. the WebAIM Contrast Checker) to check the contrast to ensure that your colours comply with current accessibility standards.
Tip: Also note the images in which you have placed text.
Accessible images
For meaningful images that are added via the Shopware Media Manager, you should include a descriptive alt text directly in the media settings.
The alt text is read aloud by screen readers and should describe the content or purpose of the image for users who cannot see it.
Example:
<img src="dhl-logo.svg" alt="Shipping with DHL">Special case: Image with visible adjacent text
If the image is purely decorative or if there's a visible descriptive text next to it, the alt attribute should still be present, but intentionally left empty:
Example:
<img src="dhl-logo.svg" alt="">
<span>Shipping with DHL</span>This ensures the image is ignored by screen readers and only the visible text is announced — preventing redundancy or confusion.
Tip: In doing so, also maintain the title attribute.
Accessible Links with Images
If a link contains only an image (e.g. a logo or icon without visible text), using an alt attribute on the image alone is not enough. In this case, you should add an aria-label to the <a> tag, clearly describing the purpose of the link.
The image itself gets an empty alt="" so that screen readers will announce only the aria-label and the picture is only decorative.
Example:
<a href="/shipping" aria-label="Learn more about our shipping with DHL">
<img src="dhl-logo.svg" alt="">
</a>This way, screen reader users hear only:
"Link: Learn more about our shipping with DHL"
and not an additional “Image: DHL”, which could be redundant or unclear.
Why not just use alt?
alt?The alt attribute belongs to the image — not to the link. Images alone often don’t provide enough context to describe where the link goes. The aria-label, on the other hand, describes the function of the link and ensures a clear, complete message for all users.
Accessible system
Shopware plans to fully fulfil the requirements of WCAG 2.1 AA with version 6.7 before the legally prescribed deadline of the Accessibility Improvement Act. There will then also be a compatible and compliant version of your ThemeWare® theme for Shopware 6.7
In addition, ThemeWare® for Shopware 6.6 will also support the ACCESSIBILITY_TWEAKS feature flag with an upcoming release.
Further information
We have put together more information on the topic of "BFSG" for you in a news article in our Service Portal:
Last updated
Was this helpful?