Web Accessibility for German Online Shops: BFSG Compliance Guide (2025 Deadline)
BFSG deadline passed June 28, 2025. Understand who must comply, fines up to 100k EUR, WCAG 2.1 AA standards, and practical implementation for German e-commerce sites.
The Barrierefreiheitsstärkungsgesetz (BFSG) – Germany's Web Accessibility Act – had a compliance deadline of June 28, 2025. That deadline has passed. German businesses operating e-commerce sites, digital services, or publishing online content are now at risk of fines up to €100,000 for non-compliance.
Critical: Deadline Expired
The June 28, 2025 BFSG compliance deadline has passed. If your site is not compliant, you are in violation and subject to enforcement action. Immediate remediation is required.
What is BFSG and Why It Matters
The Barrierefreiheitsstärkungsgesetz (BFSG) is German legislation implementing the EU Web Accessibility Directive (2016/2102). It requires public and private organizations to make their websites and digital services accessible to people with disabilities. Non-compliance results in penalties, negative brand reputation, and exclusion of a significant portion of the market (15-20% of the population has a disability).
1. Who Must Comply with BFSG?
Affected Entities
BFSG applies to all commercial websites and digital services. However, certain entities are exempt.
- Public sector websites (government, public institutions)
- B2C e-commerce (online shops selling to consumers)
- Digital services (software, apps, web applications)
- Websites of organizations providing digital services
- Digital services related to payment systems or telecommunications
Exemptions: Who Doesn't Have to Comply (Yet)
Micro-enterprises with fewer than 10 employees are exempt until December 28, 2030. However, this exemption applies only to accessibility requirements; other regulations may still apply.
- Micro-enterprises: <10 employees (exempt until 2030)
- Sole proprietorships: May qualify for exemption if <10 employees
- SMEs with 10-49 employees: Must comply (no exemption)
- Larger organizations: Must comply regardless of size
Exemption Clarification
If you are a micro-enterprise, you are exempt NOW, but the exemption expires December 28, 2030. Plan for compliance by 2029-2030. If you have 10+ employees, you must be compliant immediately (deadline expired June 28, 2025).
2. WCAG 2.1 Level AA: The Standard
BFSG requires compliance with WCAG 2.1 Level AA (Web Content Accessibility Guidelines). WCAG is the international standard for web accessibility, developed by the W3C.
What is WCAG 2.1 Level AA?
WCAG 2.1 consists of 78 success criteria organized into 4 principles: Perceivable, Operable, Understandable, and Robust (POUR).
- Level A: Basic compliance, minimum accessibility
- Level AA: Recommended standard, covers most common disabilities
- Level AAA: Highest standard, more difficult/expensive to achieve
- BFSG requires Level AA, which is the global best practice for most organizations
3. Key WCAG 2.1 AA Requirements
1. Text Alternatives (Alt Text)
All images, icons, and visual content must have descriptive alt text describing the content and function. Screen reader users rely entirely on alt text.
- Product images: 'Blue ceramic coffee mug, 12oz, premium quality' (not 'mug.jpg')
- Decorative images: Leave alt text blank (alt='')
- Icons: Describe function, not appearance ('Search' not 'Magnifying glass')
- Charts/graphs: Provide data summary in alt text or accessible description
2. Keyboard Navigation
All functionality must be operable via keyboard alone. Users with motor disabilities or visual impairments use keyboards instead of mice.
- Tab order: Logical, sequential (top-to-bottom, left-to-right)
- Skip links: Allow users to skip repetitive navigation (skip to main content)
- Focus indicators: Visible focus outline on buttons/links (never set outline: none)
- No keyboard traps: User must be able to tab away from any interactive element
- Dropdown menus: Operable with arrow keys, not just mouse hover
Common Violation: Removing Focus Outlines
Many websites remove focus outlines for aesthetic reasons using `outline: none` in CSS. This is a critical accessibility violation. Users relying on keyboard navigation cannot see where they are. Always provide visible focus indicators.
3. Color Contrast
Text and background colors must have sufficient contrast for people with color blindness and low vision. WCAG AA requires a 4.5:1 contrast ratio for normal text, 3:1 for large text.
| Text Type | Required Ratio | Example |
|---|---|---|
| Normal text (<18pt) | 4.5:1 | Black (#000000) on white (#FFFFFF) = 21:1 ✓ |
| Large text (≥18pt) | 3:1 | Gray (#666666) on white (#FFFFFF) = 7:1 ✓ |
| UI components/borders | 3:1 | Border color must contrast with background |
| Insufficient (red on orange) | N/A | Red (#FF0000) on orange (#FF8000) = 1.3:1 ✗ |
Tools like WebAIM Contrast Checker or Color Contrast Analyzer help verify ratios. Test all color combinations on your site.
4. Form Labels and Instructions
All form inputs must have associated labels. Screen reader users need to know what each field is for.
- Use HTML <label> elements linked to inputs via 'for' attribute: <label for='email'>Email</label><input id='email'>
- Placeholder text alone is NOT sufficient (disappears when user types)
- Error messages must be associated with fields and announced to screen readers
- Instructions should be before form fields, not hidden in tooltips
- Required fields must be marked (*) and announced in the label
5. Headings and Content Structure
Use proper HTML heading hierarchy (H1, H2, H3, etc.). Screen reader users navigate by headings.
- One H1 per page (main title)
- Logical hierarchy: H1 → H2 → H3 (no skipping levels)
- Don't use headings for styling; use CSS instead
- Table headers (<th>) for data tables
- Lists: Use <ul>, <ol>, <li> instead of <div> elements
6. Accessible PDFs and Documents
Downloadable PDFs and documents must be accessible. This includes tagging, proper structure, alt text for images, and searchable text (not scanned images).
- PDFs should be tagged with proper structure elements
- Avoid scanned images without OCR (use searchable PDFs)
- Images in PDFs need alt text
- Links should have descriptive text (not 'click here')
- Consider offering alternate formats: HTML, Word, etc.
7. Video and Audio Captions
Multimedia content must include captions (for videos) and transcripts (for audio). Deaf and hard-of-hearing users rely on captions.
- Videos: Closed captions or subtitles (not just auto-generated by YouTube)
- Audio: Full transcript provided below or linked
- Avoid auto-playing media without user control
- Provide volume controls and pause buttons
8. ARIA Landmarks and Regions
Use semantic HTML and ARIA landmarks to define page regions. This helps screen reader users navigate complex layouts.
- <nav> for navigation
- <main> for main content
- <aside> for sidebars
- <footer> for footer content
- role='search' for search functionality
- role='contentinfo' for footer information
4. Technical Standards: EN 301 549
EN 301 549 is the European standard for ICT accessibility that BFSG references. It incorporates WCAG 2.1 and adds additional requirements for non-web digital services (mobile apps, software, etc.).
- Incorporates WCAG 2.1 Level AA
- Adds requirements for mobile apps and software
- Requirements for authoring tools and content management systems
- PDF/document standards
- Real-time communication (accessibility of video conferencing, chat)
5. Common BFSG Violations in German E-Commerce
| Violation | Impact | Fix |
|---|---|---|
| Missing alt text on product images | Screen readers can't describe products | Add descriptive alt text to all images |
| No focus outlines on buttons | Keyboard users can't navigate | Set focus styles: outline or background color change |
| Low color contrast (gray on white) | Low vision users can't read | Increase contrast to 4.5:1 ratio |
| Form fields without labels | Screen readers can't identify inputs | Use HTML <label> elements with 'for' attribute |
| Video without captions | Deaf users can't watch | Add captions/subtitles |
| Dropdown menus mouse-only | Keyboard users can't navigate | Add arrow key support |
| Auto-playing video/audio | Startling for users, especially on assistive tech | Require user action to play |
| Text in images (no alternative) | Screen readers see only image, not text | Use actual text or SVG with alt text |
6. Testing and Auditing Tools
Automated Testing Tools
- WAVE (WebAIM): Browser extension, highlights accessibility issues on any page
- axe DevTools: Developer tools extension, detailed reports on violations
- Lighthouse: Built into Chrome, accessibility audit tab
- NVDA (screen reader): Free screen reader for Windows testing
- JAWS: Premium screen reader, market standard
These tools are good for baseline testing but don't catch all issues. Manual testing and real user testing with assistive technology users are essential.
Manual Testing Checklist
- Navigate site using only Tab key (no mouse)
- Zoom browser to 200% and verify layout
- Test with Windows high contrast mode enabled
- Use a screen reader to verify content makes sense
- Resize browser window; check responsive design
- Test all form submission flows
- Test keyboard shortcuts are discoverable
7. BFSG Enforcement: Penalties
Who Enforces BFSG?
Marktüberwachungsbehörden (Market Surveillance Authorities) at the state (Länder) level enforce BFSG. Complaints can come from consumers, disability advocates, or proactive market surveillance.
Penalties for Non-Compliance
BFSG violations carry significant penalties:
- First violation: Administrative fine up to €100,000
- Repeat violations: Fines can escalate
- Ongoing violations: Repeated fines for continued non-compliance
- Alternative enforcement: Court orders to remove non-compliant site or service
Enforcement is Active
German authorities are actively enforcing BFSG. In 2024-2025, several major e-commerce sites received fines or enforcement notices for non-compliance. This is not a theoretical risk.
8. Cost Estimates for BFSG Compliance
| Project Scope | Timeline | Cost Range (EUR) | Notes |
|---|---|---|---|
| Audit only (identify issues) | 1-2 weeks | 2,000-5,000 | Doesn't include fixes |
| Small site (10-50 pages) | 4-8 weeks | 5,000-15,000 | Basic e-shop, straightforward fixes |
| Medium site (50-200 pages) | 8-16 weeks | 15,000-40,000 | More complex, may need redesign |
| Large/complex site (200+ pages) | 16+ weeks | 40,000-100,000+ | Extensive redesign, major backend changes |
| Ongoing maintenance (annual) | Ongoing | 2,000-5,000/year | Monthly audits, new content review |
Compliance cost varies based on site complexity, current state, and whether you hire consultants or use in-house resources.
9. Implementation Roadmap (2025-2026)
If your site is not yet compliant, here's a practical timeline:
- Month 1: Conduct accessibility audit (WAVE, axe, manual review)
- Month 1-2: Prioritize fixes: critical issues first (alt text, contrast, keyboard nav)
- Month 2-4: Implement critical and major fixes
- Month 4: Run comprehensive test (automated + manual + screen reader)
- Month 4-5: Fix remaining minor issues
- Month 5: Final audit and prepare compliance statement
- Ongoing: Monthly maintenance, new content review, quarterly audits
10. Transition Period: Existing Products (2025-2030)
For products that existed before June 28, 2025, there is a transition period until December 28, 2030 for physical or software products. However, this does NOT apply to websites or digital services—those must be compliant immediately.
- Websites and online shops: Must be compliant immediately (deadline passed)
- Physical products: Transition period until 2030 (not your concern)
- Software/apps: Must be compliant immediately
- Digital documents: Must be compliant immediately
11. Compliance Documentation and Accessibility Statement
BFSG requires websites to provide an accessibility statement that documents compliance efforts and provides contact information for accessibility issues.
What to Include in Your Accessibility Statement
- Declaration of conformance with WCAG 2.1 Level AA
- Explanation of how accessibility was achieved
- List of known non-compliant elements (if any)
- Contact email for accessibility issues
- Process for handling accessibility complaints
- Link to Marktüberwachungsbehörde (if complaint unresolved)
Your accessibility statement should be easily accessible (e.g., footer link). Review it annually.
12. Business Case for Accessibility
Beyond legal compliance, accessibility is good business:
- Market expansion: ~15-20% of population has disabilities; inclusive design captures this market
- Better user experience: Accessibility improvements benefit all users (captions help in noisy environments, clear navigation helps everyone)
- SEO improvement: Proper headings, alt text, semantic HTML improve search rankings
- Legal risk reduction: Proactive compliance avoids fines and lawsuits
- Brand reputation: Shows commitment to inclusion
- Mobile optimization: Accessible sites often work better on mobile devices
13. Practical Implementation Checklist
Quick Wins (Can be done in 1-2 weeks)
1. Add descriptive alt text to all images (prioritize product images) 2. Check and fix color contrast on text and buttons (use WebAIM Contrast Checker) 3. Ensure all buttons and links have visible focus indicators 4. Add skip-to-main-content links 5. Review form labels: ensure all inputs have <label> elements 6. Test keyboard navigation: can you navigate the entire site with Tab key?
Summary
The BFSG compliance deadline passed June 28, 2025. If you haven't already, immediate action is required to avoid fines up to €100,000. Start with an accessibility audit, prioritize critical issues (alt text, contrast, keyboard navigation), and plan for comprehensive compliance within 2-3 months. Beyond legal requirements, accessibility is good business—it expands your market, improves user experience, and builds brand loyalty.
Disclaimer: Finance Stacks is not a financial advisory service. All content is for informational purposes only and does not replace professional advice from a tax advisor, accountant, or financial consultant.