Shopware Alt Text:
The Complete 2026 Guide

Shopware powers thousands of B2C and B2B stores across the DACH region and beyond. Most of them share one quiet problem: large product catalogs full of images without alt text. Manual filling is technically possible, but at any meaningful catalog size it stops being realistic — and since June 2025, it’s no longer just an SEO miss. It’s a compliance gap.

This guide walks through the actual mechanics: where Shopware stores alt text natively, the difference between alt text, title and filename, what Shopware Copilot already does, how bulk processing works in practice, and what the European Accessibility Act expects shop operators to document.

All paths and admin labels in this guide refer to Shopware 6.6 and later. Older Shopware 5 stores have a different admin structure and are not covered here.

1. Why Shopware Alt Text Matters in 2026

Two pressures converged on Shopware shops between 2024 and 2026: image search traffic and accessibility law. Both come down to the same HTML attribute.

Image search is a measurable revenue channel

Roughly 22% of e-commerce organic traffic flows through Google Image Search. For visual product categories — fashion, furniture, home goods, jewelry — the share is often higher. Alt text is the primary signal Google uses to understand what’s in a product image. Without it, the image is effectively invisible to image search.

EAA / BFSG is now enforced, not theoretical

The European Accessibility Act (EAA) and Germany’s national implementation, the BFSG, took effect on June 28, 2025. Both require digital B2C services — including online shops — to meet WCAG 2.1 Level AA. WCAG Success Criterion 1.1.1 (Non-text Content) explicitly requires text alternatives for informative images. Product photos qualify.

What changed in 2026: market surveillance authorities started active audits in January, and warning letters from competing shops began rolling out in August 2025. German maximum fines reach €100,000 per violation. Spain caps fines at €1,000,000.

The multilingual multiplier

Shopware’s strength is multi-storefront, multi-language commerce. Its weakness, for alt text, is exactly that: every sales channel and every language needs its own alt text per image. A 2,500-product catalog with five gallery images and three storefront languages needs 37,500 alt texts. Manual writing at 30 seconds each comes out to about 312 hours of work. That’s why the topic stays unresolved in most shops.

2. Where Alt Text Lives in Shopware 6

Shopware stores alt text in four distinct places. Filling only one of them — usually the product media tab — is a common mistake that leaves Shopping Experiences and category headers without alt text.

Sales-channel languages are independent

Shopware separates content per sales-channel language. A product with German, English, and French storefronts has three independent alt-text fields per image. Shopware does not auto-translate — the field is empty for each language until something writes to it.

This is one of the reasons stores with international sales channels often have alt text in their primary language only. The English and French fields stay blank, and for image search in those locales, those product images do not exist.

3. Alt Text vs. Title vs. Filename: Three Fields, Three Jobs

Shopware stores three separate fields per image, and they’re often confused. Each does a different job, each is read by different systems, and only one of them is legally required.

The “shared image” trap

A practical pitfall in Shopware: when an image is used across multiple products or Shopping Experiences, the alt text is stored centrally per image, not per usage. Editing it in one place changes it everywhere the image appears. For images that need different alt text in different contexts, upload the image as separate media files.

What a plugin actually fills

AutoAlt.ai writes the alt text field by default. The title field can optionally receive the same text via a configuration toggle (“Also apply Alt Text as Image Title”). The filename is set at upload — the plugin doesn’t rewrite filenames after the fact. For new uploads, the responsibility for sensible filenames stays with whoever uploads.

4. Three Practical Approaches

There are three realistic paths to filling Shopware alt text fields at production scale. Each has a place; the right choice depends on catalog size, edition, and how many languages you run.

The reason a native plugin matters specifically for Shopware is structural: Shopware’s media table, sales-channel language model, and Shopping Experiences blocks all need to be addressed through the proper API endpoints. Generic tools don’t know about any of that — they generate text in a separate window that someone then has to paste in by hand.

Plugin landscape in the Shopware Store:

• AutoAlt.ai — in-house plugin from webAufstieg GmbH (Germany). 5☆ rating. Covers product media, Shopping Experiences, categories, manufacturers. Bulk + auto-on-upload. EU servers.
• Other AI alt text plugins — available via third-party developers; coverage and support vary. Check Shopware Store ratings and review counts before deciding.
• General-purpose AI assistants for Shopware (chat-style) sometimes generate alt text as a side feature; quality and bulk capability are usually limited.

For a broader market view across all platforms, see our comparison of seven alt text tools. There’s also a fourth option worth understanding properly — Shopware’s own native AI feature.

5. What Shopware Copilot Already Does (and Where It Stops)

Since Shopware 6.5.1.0, the Commercial edition (Rise plan and up) includes the Image Keyword Assistant — part of Shopware’s broader AI Copilot toolset. It’s Shopware’s native answer to image metadata, and the obvious question is: do you still need a separate plugin?

The honest answer: it depends on your edition, your catalog, and what you mean by “alt text.”

What Shopware Copilot does well

• Generates keywords from image content using AI
• Optionally appends those keywords to the alt text field
• Processes new uploads automatically once enabled
• Configurable per language
• Four modes for handling existing keywords (overwrite, append, prepend, leave alone)
• Native integration — no third-party trust required

Where it stops

• Keywords, not full sentences. Output looks like “leather jacket, black, women, zipper” rather than a WCAG-compliant descriptive sentence. Screen readers read it as a comma-separated list, which is harder to parse than a coherent description.
• Existing media is not processed automatically. Per Shopware’s official documentation: existing media is only re-tagged when re-uploaded via the “Replace” function. A 5,000-image legacy catalog won’t be touched.
• Rise plan and up only. Commercial pricing starts at approximately €600/month (Shopware’s published Rise tier). Below that, the feature isn’t available.
• No bulk generator for thousands of legacy images
• No documented compliance log for EAA/BFSG audits
• No OCR for text-in-image hero banners

How they actually compare

Honest recommendation

If you’re on Rise or higher and your catalog is mostly forward-looking (new uploads, low volume of legacy gaps), Shopware Copilot can handle a meaningful share of the work — especially combined with manual review on hero images. The moment legacy bulk, multilingual coverage, descriptive-sentence quality, or EAA documentation enters the picture, a specialized plugin closes the gaps. The two are not mutually exclusive: many Rise+ shops run Copilot for keyword tagging and AutoAlt.ai for the actual alt text.

6. Step-by-Step: Install AutoAlt.ai for Shopware

Setup takes about five minutes. The plugin is free; you only pay for the alt texts you generate beyond the free 50 credits per month.

Once auto-on-upload is active, your forward-looking image catalog is solved. Existing images are the next step.

7. Bulk Optimization for Existing Catalogs

Auto-on-upload only handles new images. For an existing 5,000-image catalog, bulk processing is the realistic path. The plugin includes a Bulk Alt Text Generator accessible from the plugin’s main view.

How bulk works

You select a target — an entire media folder, a set of products by category, or all media without alt text — and trigger the run. The plugin queues images and processes them in the background through your queue worker. Generation takes roughly 2–4 seconds per image. There is no impact on storefront performance because the work happens in the admin queue, not on the customer-facing application.

You receive an email notification when each bulk run completes. Failed images (corrupted files, format unsupported) are flagged in the history view and can be retried without consuming additional credits.

Strategy: prioritize what indexes

Before triggering a 50,000-image run, prioritize. Run bulk first on:

• Top 100–500 best-selling products (revenue impact)
• Category landing pages and Shopping Experiences (high-traffic SEO surfaces)
• New collections and seasonal landing pages
• Manufacturer/brand pages

Long-tail historical products can be processed in a second pass. For audits, partial-but-documented coverage of high-traffic surfaces is more defensible than uniform partial coverage everywhere.

8. Multilingual Storefronts: One Credit, All Languages

This is the structural difference for Shopware specifically. Shopware shops typically run multiple sales channels — shop.de, shop.com, shop.fr — with different languages. Each sales-channel language stores its own alt text per image.

AutoAlt.ai counts one credit per image. That credit produces alt text in every active sales-channel language at once. A product image processed once for a German + English + French shop consumes one credit and writes three alt texts.

The cost difference compounds quickly:

Per-channel language configuration

The plugin reads your active sales-channel language list automatically. You don’t maintain a separate language table. If you add a Polish sales channel next month, the plugin starts generating Polish alt text on the next bulk run or new upload — no reconfiguration.

Currently supported: 25+ storefront languages, including all EU official languages plus English (US/UK/AU), Norwegian, Turkish, Japanese, Chinese (simplified and traditional), Korean.

9. Shopping Experiences, Edge Cases & Industry Examples

Shopping Experiences (Shopware’s CMS) is where most alt text gaps hide. The product media tab is well-known and often partially filled. Shopping Experiences blocks — hero images, image-text blocks, category headers, landing pages — almost never are.

What gets covered

• Hero images and category banners on landing pages and category pages
• Image blocks within text-image, image-grid, and image-slider blocks
• Background images in CMS layouts (where alt text is technically supported)
• Image-text combinations in commerce blocks

What stays manual

Two image types fall outside automatic generation:

• Decorative images — pure visual flourish without informational content. WCAG explicitly requires these to use alt="". Generating descriptive alt text for them adds noise to screen readers. The plugin lets you mark images as decorative; they get an empty alt attribute and consume zero credits.
• Brand-critical hero copy — the main hero on your homepage often carries marketing copy that’s better written by your team than generated. Generate first, then refine the top 5–10 hero images by hand.

The “image with text overlay” trap

A common Shopping Experience pattern is an image with text rendered on top in the same JPEG. Screen readers can’t read text inside an image. The alt text needs to reproduce the visible text, not describe the visual. Example:

<img src="summer-sale-banner.jpg" alt="Summer Sale — Up to 40% off swimwear, in stock now">

The plugin recognizes text-in-image patterns via OCR and reproduces the visible text in the alt attribute. For purely decorative or repeated overlays, manual override remains the right tool.

What good alt text looks like by industry

Theory aside, what does usable alt text actually look like? Six examples by industry, each in three quality levels — bad, okay, optimal — so you can sense-check what AutoAlt.ai (or your team) produces against real-world standards.

For 30+ before-and-after examples across more industries and image types, see our dedicated alt text examples guide.

10. EAA / BFSG Compliance Documentation

Compliance isn’t just having alt text — it’s being able to show that you have alt text, when asked. Market surveillance authorities and warning-letter law firms both ask for documentation, not screenshots.

What the EAA actually requires for images

The EAA references EN 301 549, which references WCAG 2.1 Level AA. The relevant criterion is 1.1.1 Non-text Content: every informative image needs a text alternative that serves the same purpose. Decorative images need an empty alt="". Functional images (icons that act as buttons, etc.) need alt text describing the function.

What this means for Shopware specifically:

• Product main images and gallery images: descriptive alt text required
• Category banners and Shopping Experience hero images: descriptive alt text required
• Manufacturer logos: alt text with the manufacturer name (so “Nike logo” or just “Nike”)
• Decorative dividers, atmospheric icons: alt="", not missing entirely
• Icons that act as buttons (e.g., add-to-cart icon): alt text describes the action

Documentation that holds up in an audit

The plugin keeps a complete history per image: when it was processed, which language, which model, the resulting text, and any manual edits. This log can be exported. For a market surveillance request or a warning-letter response, this is the kind of evidence that closes the case quickly.

Two further pieces are worth keeping on file:

• An accessibility statement on your shop, linked from the footer. Required by BFSG for B2C shops; the EAA expects equivalent disclosure across the EU.
• An accessibility scan report — a snapshot of remaining issues with timeline. Available via the free accessibility scan.

For the legal context of alt text requirements across the DACH region, see our dedicated guides for Germany, Austria, and Switzerland.

11. Frequently Asked Questions

Related Articles