Since June 28, 2025, Germany's Accessibility Strengthening Act (BFSG) has been in force. 95.9% of all websites have at least one WCAG error (WebAIM 2026) — and the first legal warnings have already been sent. A systematic BFSG audit is the only way to make your online shop legally compliant and avoid fines of up to €100,000.
Why a BFSG Audit Is Now Essential
The BFSG is no longer a future concern — it is current law. 80% of German online shops are still not accessible (Aktion Mensch/Google). Market surveillance authorities began active inspections in 2025, and the first legal warnings have been issued at costs of €1,784.10 plus €490 analysis fees (Ratgeberrecht.eu).
At the same time, inaccessible shops miss enormous market potential: 7.9 million severely disabled people live in Germany (Destatis) — 9.3% of the population. Worldwide, 1.3 billion people live with a disability, representing 16% of the global population (WHO). The purchasing power of disabled households globally amounts to $8 trillion (Purple).
In summer 2025, the first competition-law warnings for lack of accessibility were sent. Cost per warning: €1,784.10 + €490 analysis (Ratgeberrecht.eu). Violations of the BFSG can also result in fines up to €100,000 (BFSG §37).
What a BFSG Audit Covers
A professional BFSG audit is more than an automated scan. It combines technical testing methods with manual expert reviews and user testing with assistive technologies. As outlined in our BFSG fundamentals article, automated tools typically detect only 25–40% of WCAG errors (Government Digital Service) — the majority of barriers remain invisible without manual review.
Technical Testing
Automated WCAG scans, HTML semantics, ARIA validation, and contrast checking across all page types
Manual Expert Testing
Keyboard navigation, screen reader compatibility, focus management, and cognitive accessibility
Legal Assessment
BFSG compliance, accessibility statement, and documentation for market surveillance authorities
The Most Common WCAG Errors in Online Shops
The WebAIM Million Report 2026 analyzed the top one million most visited websites. The results are alarming: an average of 56.1 WCAG errors per homepage. The five most common error types affect fundamental aspects of accessibility:
| Error Type | Frequency | Affected Users |
|---|---|---|
| Contrast errors | 83.9% of all websites (WebAIM 2026) | Visually impaired, elderly |
| Missing alt texts | 53.1% (WebAIM 2026) | Blind, screen reader users |
| Missing form labels | 51% / 33.1% of fields (WebAIM 2026) | Screen reader users, motor impaired |
| No keyboard navigation | Only 20 of 65 top shops navigable (Aktion Mensch 2025) | Motor impaired |
| Missing focus indicators | Missing in >70% of shops | Keyboard users |
Particularly alarming: popular shop systems also perform poorly. Magento-based shops average 85.4 errors per homepage, WooCommerce shops 75.6 errors, and Shopify shops 69.6 errors (WebAIM 2025). This shows that no system is fully accessible out of the box — professional optimization is always required. We have summarized the new WCAG 2.2 criteria that are particularly relevant in a separate article.
The 5-Phase Audit Process
A structured BFSG audit follows a proven process that ensures no barrier goes undetected. At XICTRON, we use a combined approach of automated analysis and manual expertise:
- Scope definition and inventory: Capture all page types of the online shop — homepage, category pages, product pages, cart, checkout, contact forms, login area, and help pages
- Automated scan: WCAG 2.1 AA-compliant scan of all captured templates with specialized tools — typically identifies 25–40% of errors (Government Digital Service)
- Manual expert testing: Keyboard navigation, screen reader tests (NVDA, JAWS, VoiceOver), contrast checking, cognitive accessibility, and responsiveness across devices
- Prioritization and reporting: Classification of all identified errors by severity (critical, high, medium, low) with specific action recommendations
- Implementation and re-audit: Fixing identified barriers by experienced frontend specialists, final review, and creation of the accessibility statement
Automated scanners typically detect only 25–40% of all WCAG errors (Government Digital Service). Context-dependent barriers such as illogical tab orders, misleading alt texts, or poorly worded error messages require manual review by trained experts.
Automated vs. Manual Testing
Many shop owners rely exclusively on automated accessibility tools. This is understandable — a scan takes minutes rather than days. But the limitations of these tools are well documented:
| Criterion | Automated Scan | Manual Expert Audit |
|---|---|---|
| Detection rate | 25–40% of WCAG errors | Up to 100% of errors |
| Contrast check | Yes — reliable | Yes — including dynamic content |
| Alt text quality | Only checks presence | Evaluates content quality |
| Keyboard navigation | Limited | Full testing |
| Screen reader compatibility | Not testable | Tests with NVDA, JAWS, VoiceOver |
| Cognitive accessibility | Not testable | Comprehensibility, error handling |
| Time required | Minutes | Several days |
| Legal certainty | No guarantee | Documented test basis |
The ideal approach combines both methods: automated scans as efficient first analysis and manual tests for in-depth quality assurance. This way, cost-effective audits are possible even for larger e-commerce projects.
Practical Testing Methods in Detail
Theory matters — but how do you actually test accessibility in practice? Below we describe the four most important manual testing methods that every shop owner can perform at least in basic form.
Testing Keyboard Navigation
Keyboard navigation is one of the most critical checkpoints — and also the easiest to self-test. Put the mouse aside and try to operate your entire online shop using only the keyboard. Use the Tab key to move forward between interactive elements, Shift+Tab to move backward, Enter to activate links and buttons, and the Spacebar to trigger checkboxes and buttons. Test every step of the purchase process: product search, filter functions, shopping cart, checkout forms, and payment.
Watch for these problems: Can you get trapped in modal dialogs or dropdown menus with the keyboard (so-called keyboard traps)? Does the focus return to the correct position after closing a dialog? Are all interactive elements — including custom widgets like sliders, tabs, and accordions — operable via keyboard? Only 20 of 65 surveyed top German shops were fully keyboard navigable (Aktion Mensch 2025).
Conducting Screen Reader Tests
Screen readers convert visual information into speech or Braille. To test your shop's compatibility, install a free screen reader like NVDA (Windows), use VoiceOver (built into macOS and iOS), or TalkBack (Android). Then navigate through your shop's key pages and check whether the screen reader reads all relevant information.
Particularly critical areas include: Are product images meaningfully described, or does the screen reader only read the filename? Are forms understandable — is it clearly announced what should be entered in each input field? Are status changes communicated, for example when a product is added to the cart? Are prices, availability, and promotions correctly readable? A thorough screen reader review often uncovers issues that no automated scanner can detect.
Systematic Contrast Testing
Contrast errors are the most common error type at 83.9% (WebAIM 2026). WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (18pt or 14pt bold and above). Use browser extensions such as the built-in contrast checker in Chrome DevTools or specialized tools to systematically check every page template in your shop.
Don't forget easily overlooked areas: placeholder text in search fields, disabled buttons, footnotes, links within body text (must be distinguishable not only by color), price information on colored backgrounds, and error messages. Contrast ratios must also be maintained in dark mode and for hover and focus states. In many CMS-based shops, contrast issues can be fixed through targeted CSS adjustments without changing the overall design.
Checking Form Labels and Error Messages
Forms are the heart of every online shop — from the search field to registration to checkout. 51% of all websites have at least one form without correct labels, and 33.1% of all input fields are affected (WebAIM 2026). Placeholder text within the field is not sufficient as a label, as it disappears when typing and is not reliably recognized as a label by screen readers.
Check every form in your shop: Is every input field associated with a visible <label> element? Are required fields marked both visually and programmatically (e.g., via aria-required)? Are error messages specific — not just "Invalid input" but "Please enter a valid email address"? Are errors displayed inline at the respective field rather than only as a general message at the top of the page? Is focus set to the first error message after submission so screen reader users can find the error immediately?
Common BFSG Violations with Specific Examples
In our audit practice, we consistently see the same problem patterns in online shops. The following examples show typical violations and their impact — both for users with disabilities and in terms of legal assessment.
| Violation | Typical Example | Impact |
|---|---|---|
| Overlay widgets instead of real accessibility | Accessibility plugin that displays a menu for adjusting font size and contrast | Rejected by experts and organizations, does not fix structural WCAG errors, can even create new barriers |
| Images in checkout without alt text | Payment symbols (credit card, PayPal) as graphics without labels | Screen reader users cannot identify which payment method they are selecting |
| Color-dependent required field marking | Required fields marked only by red borders, without asterisks or text indicators | Color-blind users cannot identify required fields |
| Custom dropdown without ARIA | Styled select box for shoe size or color without role="listbox" and keyboard control | Screen reader and keyboard users cannot select a variant |
| Auto-carousel on homepage | Automatically rotating banners without pause button and without keyboard control | Motor-impaired users cannot read content, screen readers miss content |
| Session timeout in checkout | Shopping cart emptied after 15 minutes without warning | Users with cognitive disabilities or screen reader users need more time |
These violations are not edge cases. 70% of digital accessibility lawsuits in the US target e-commerce companies (UsableNet 2025). While German law uses different enforcement mechanisms, the trend is clear: online shops are in the spotlight of regulators.
BFSG Audit Checklist for Shop Owners
The following checklist covers the most important audit points for BFSG compliance. Use it as a guide for an initial self-assessment — for a legally sound evaluation, we recommend professional consulting.
- Contrast: All texts meet the minimum ratio of 4.5:1 (normal text) or 3:1 (large text)
- Alt texts: All informative images have descriptive alt texts, decorative images have empty alt attributes
- Form labels: Every input field is associated with a visible label — placeholder alone is not sufficient
- Keyboard navigation: All functions are accessible without a mouse, tab order is logical
- Focus indicators: Visible focus markers on all interactive elements during keyboard use
- Page structure: Heading hierarchy (H1–H6) is logical, no skipped levels
- Error messages: Form errors are clearly described and accessible to screen readers
- Time limits: No automatic timeout in checkout without extension option
- Moving content: Animations and autoplay videos can be stopped
- Accessibility statement: Statement exists, is current, and accessible from every page
Who Is Affected by the BFSG — and Who Is Exempt?
The BFSG generally applies to all companies offering digital products or services to consumers. This includes online shops, booking portals, banking services, and digital media.
Micro-enterprises with fewer than 10 employees and under €2 million annual revenue may be exempt from service obligations (BFSG). Product obligations still apply. A legal review is advisable, as the exemption is interpreted narrowly.
Important: Even if a shop falls under the micro-enterprise exemption, accessibility can make business sense. 69% of online shoppers with disabilities leave inaccessible websites immediately (Click-Away Pound) — and 83% limit their shopping to known accessible shops (Click-Away Pound). Those who are accessible win customers that other shops lose.
The Business Case: Accessibility as a Growth Driver
Accessibility is not just a legal obligation — it is a measurable competitive advantage. Companies that take accessibility seriously benefit from higher conversions, better SEO, and a larger target audience.
A case study shows: After fixing accessibility issues, conversion rate increased by 26% and checkout rate by 21.9% (Build Grow Scale). According to Forrester, every dollar invested in accessibility typically yields $100 in returns (Forrester).
The numbers confirm the trend: 91% of respondents say accessibility improves overall user experience (Level Access). Companies with exemplary accessibility achieve on average 1.6x more revenue and 2.6x more net profit than the industry average (Accenture). The global accessibility software market is growing from $897 million (2025) to an estimated $1.89 billion by 2034 (Straits Research).
Furthermore, the target audience will grow: By 2050, the number of people aged 60+ will double worldwide to 2.1 billion (WHO/WEF). Age-related limitations in vision, fine motor skills, and cognition make accessibility a strategic concern for every online retailer.
The importance of this topic is also reflected in industry developments: 82% of companies now integrate AI tools into their accessibility strategies (Level Access) — from automated alt text generation to AI-powered testing methods. This shows that accessibility is no longer a niche topic but has arrived in the mainstream of digital development.
For SEO, accessibility is equally relevant: clean page structure, correct heading hierarchy, descriptive alt texts, and semantic HTML are essential for both screen readers and search engine crawlers. Shops that take their BFSG audit seriously typically improve their organic visibility at the same time.
Accessibility by Shop System
The starting point for a BFSG audit depends heavily on the shop system in use. None is fully accessible out of the box — but the effort required for optimization varies significantly.
Shopware
Solid foundation in the Storefront theme, but adjustments needed for focus management, ARIA labels, and checkout. Shopware accessibility requires theme modifications.
WooCommerce
Highly theme-dependent. Many popular themes have contrast and keyboard issues. 75.6 errors/page on average (WebAIM 2025). WooCommerce optimization requires high-quality themes.
Magento / Adobe Commerce
Complex frontend with 85.4 errors/page (WebAIM 2025). Custom widgets and checkout in particular require extensive modifications.
Shopify
69.6 errors/page (WebAIM 2025). Dawn theme offers a good foundation, but third-party apps can compromise accessibility.
Tools and Resources for Accessibility Testing
An efficient BFSG audit benefits from a variety of specialized tools. The following overview shows proven tools for different testing areas — from free browser extensions to professional audit platforms.
Automated Scanners
axe DevTools, WAVE, Lighthouse Accessibility audit, Pa11y, and ARC Toolkit check WCAG criteria automatically. They typically catch 25–40% of errors (Government Digital Service), ideal as initial analysis.
Browser Extensions
HeadingsMap for heading hierarchy, Colour Contrast Analyser for contrast testing, Web Developer Toolbar for structure checks, and tota11y for a quick overview of all accessibility issues.
Screen Readers
NVDA (Windows, free), JAWS (Windows, commercial), VoiceOver (macOS/iOS, built-in), and TalkBack (Android, built-in). Manual testing with at least two different screen readers is recommended.
Contrast and Color Tools
Chrome DevTools contrast checker, Stark plugin for Figma/Sketch, Sim Daltonism for color blindness simulation, and the WebAIM Contrast Checker for quick individual checks.
Important: No single tool covers all WCAG criteria. A professional audit strategy combines at least one automated scanner, manual keyboard and screen reader tests, and visual contrast checks. For larger shops, a monitoring solution that automatically checks new pages and changes for regressions is also recommended.
From Testing to Implementation: Typical Measures
After the audit comes implementation. Identified barriers are prioritized by severity and systematically resolved. We distinguish between quick wins and structural changes:
- Quick wins (1–3 days): Adjust contrasts, add missing alt texts, link form labels, set language attribute
- Medium effort (1–2 weeks): Implement focus management, add skip links, correctly assign ARIA roles, improve error messages
- Structural changes (2–4 weeks): Keyboard navigation for complex components (mega menus, filters, configurators), make checkout flow accessible, PDF accessibility
- Accompanying measures: Create accessibility statement, set up feedback mechanism, internal training for content editors
The time required depends on the size and complexity of the shop. A typical Shopware project with 50–200 pages and a modern theme typically takes 4–8 weeks for complete optimization. Legacy systems or complex custom developments may require more effort.
Concrete Implementation Examples
To make these measures tangible, here are some concrete examples from practice: Focus indicators can be made visible for all interactive elements with a single CSS rule — instead of outline: none, a clear focus style should be defined, e.g., a 2px outline in the brand color. Skip links are hidden links at the top of the page that become visible on keyboard focus and jump directly to the main content — they require only a few lines of HTML and CSS.
For alt texts, the following applies: Product images need descriptive texts like "Blue women's t-shirt made of organic cotton, size M" instead of "img_12345.jpg" or "Product image". Decorative elements receive an empty alt attribute (alt=""), so screen readers skip them. For form labels, every input field must be programmatically associated with its label — either through a <label> element with a for attribute or via aria-label or aria-labelledby. Placeholder text alone is not a substitute, as it disappears when typing.
Maintaining Accessibility Long-Term
A one-time audit is not enough. Every update, new content, and design change can introduce new barriers. Sustainable accessibility requires a continuous process:
- Automated CI/CD tests: Integrate accessibility checks into the deployment pipeline
- Regular manual audits: Quarterly screen reader and keyboard tests
- Content guidelines: Standards for alt texts, heading hierarchy, and contrast colors
- Training: Sensitize developers, designers, and content editors to accessibility
- Monitoring: Update accessibility statement annually, evaluate user feedback
The most efficient approach: Integrate accessibility into the development process from the start. Automated accessibility tests in the CI/CD pipeline catch regressions before they reach production. Good UX design principles also support long-term accessibility.
Your Path to an Accessible Online Shop
The BFSG is in force, the first warnings have been sent, and market surveillance is actively checking. At the same time, accessibility offers a measurable opportunity: more customers, higher conversions, and lasting legal compliance. The first step is a professional audit — because only those who know the gaps can close them.
As an experienced e-commerce agency, we combine technical accessibility expertise with an understanding of our clients' business requirements. We audit your shop, create a prioritized action plan, and implement the optimization — from quick wins to structural changes.
This article is based on data from: WebAIM Million Report 2025/2026, Aktion Mensch/Google Accessibility Report, Destatis (Federal Statistical Office), WHO World Disability Report, Click-Away Pound Survey, Government Digital Service, Build Grow Scale Case Study, Forrester Research, Level Access Survey, Accenture Disability Inclusion Study, Straits Research, WHO/WEF Ageing Report, Purple Pound Research, Ratgeberrecht.eu, UsableNet 2025 Digital Accessibility Report. The figures cited may vary depending on timing and methodology.
Costs depend on the scope and complexity of the shop. Factors include the number of page types, custom components, and the current state. A realistic estimate is typically only possible after an initial analysis. Contact us for an individual assessment.
Generally not. Automated scanners typically detect only 25–40% of WCAG errors (Government Digital Service). Context-dependent issues such as confusing error messages, poor tab orders, or misleading alt texts require human evaluation.
A comprehensive audit with automated and manual testing typically takes 1–2 weeks. The subsequent implementation of measures can take 4–8 weeks depending on scope.
Micro-enterprises with fewer than 10 employees and under €2 million annual revenue may be exempt from service obligations (BFSG). However, the exemption is interpreted narrowly — professional legal review is recommended.
The BFSG references the harmonized European standard EN 301 549, which aligns with WCAG 2.1 Level AA. This encompasses 50 success criteria across the areas of perceivability, operability, understandability, and robustness.
Yes. As part of a complete audit, we create a legally compliant accessibility statement documenting the current conformity status, known limitations, and a feedback mechanism — as required by the BFSG.