Accessibility testing for Shopware stores

What we test

• Storefront and cart: the home page, category listings, product pages, the cart and the start of checkout. Later checkout steps need a login or an address, and we never place an order.
• Keyboard purchase path: we add a product to the cart and go to the start of checkout with the keyboard alone, and report where focus gets lost or a control can't be reached.
• Consent banner: on EU stores the cookie banner is the first thing a shopper meets. We check the banner itself, then decline optional cookies so it doesn't cover the pages we test.
• Languages: we test your shop's main language. Ask us about other languages.

Automated testing finds many common issues; some criteria need human review. An audit adds that review. Our method page explains what we test and how the score works.

What we fix

On self-hosted Shopware 6, we fix the issues listed in your quote in a custom theme plugin that extends your theme: Twig templates, styles and scripts. We never change Shopware's core or the files of a third-party plugin, so updates don't overwrite the fixes; a scan after a major update shows what changed.

• We work on a staging copy of your shop, and you approve every change before it goes live.
• You give us a limited administration account and access to the theme plugin's code for the time of the work.
• After publishing, we scan again and report what changed for every quoted finding.

Remediation follows an audit, so the quote lists exactly what we fix.

Shopware SaaS (Cloud)

For shops on Shopware SaaS (Cloud), we offer monitoring and audits. We don't make code changes there: the audit lists each issue and how to fix it, for you or your agency.

Shopware PaaS, where your own code is deployed, counts as self-hosted: we can fix it as above.

Get started

Start with a free scan of three pages, see the plans and prices, or book a call. Selling to consumers in the EU? Read what the European Accessibility Act asks of online stores.

Get a free scanBook a call