European Accessibility Act: What online shops should be able to evidence after 28 June 2025
Accessibility ComplianceKnowledge
What Is The European Accessibility Act?
The European Accessibility Act, or EAA, is an EU framework that aims to make selected products and services more accessible. In Germany, it is implemented through the Barrierefreiheitsstaerkungsgesetz (BFSG). Since 28 June 2025, accessibility is no longer only a topic for public-sector websites. It is relevant for many commercial digital services as well.
This article is not legal advice. It explains the practical website perspective: which shop journeys should be reviewed, what evidence is useful, and why accessibility work should become a recurring process.
Why Online Shops Are Affected
Online shops are not static brochures. Users search, filter, compare, add products to carts, enter addresses, choose payment methods, confirm orders, and read service information. If one of those steps is inaccessible, the business problem is not abstract. Users may be unable to buy.
For ecommerce teams, the key question is not only whether the site "has accessibility." The better question is whether critical purchase journeys can be operated, understood, and verified by people with different abilities and assistive technologies.
Which Shop Areas Should Be Checked First?
1. Homepage And Main Navigation
Users need to reach categories, search, account areas, and service pages without relying only on mouse interaction or visual cues.
2. Category And Search Result Pages
Filters, sorting, pagination, product cards, and dynamic updates must remain operable and understandable.
3. Product Detail Pages
Images need meaningful alternatives where relevant. Product variants, price information, availability, delivery notes, reviews, and add-to-cart controls need clear semantics.
4. Cart
Quantity controls, delete actions, error states, delivery options, and price summaries must be keyboard-accessible and understandable.
5. Checkout
Checkout is the highest-risk journey. Forms, validation, payment selection, focus handling, and error recovery need special attention.
6. Legal And Service Information
Returns, terms, privacy information, accessibility statements, contact options, and support routes must be findable and readable.
WCAG, EN 301 549 And BFSG
In practice, many accessibility projects use the Web Content Accessibility Guidelines, or WCAG, as the technical reference. WCAG describes how to make web content more accessible to people with a wide range of disabilities.[^wcag22]
EN 301 549 is also relevant in the European context. The W3C notes that organizations working with the European Accessibility Act often use WCAG and EN 301 549 as reference points. For concrete legal obligations, teams should involve qualified advice.
Why A One-Off Accessibility Audit Is Not Enough
Online shops change constantly: new templates, campaigns, consent tools, product media, payment methods, recommendation widgets, and third-party scripts. Accessibility can regress quickly. A one-off audit can be useful, but it does not create an operating routine.
The practical goal is evidence: what was checked, which barriers were found, who owns remediation, when fixes were verified, and what changed since the last run.
Common Accessibility Problems In Online Shops
Missing Or Weak Alternative Text
Images that communicate product information need appropriate text alternatives. Decorative images should not create noise.
Insufficient Color Contrast
Price labels, sale badges, disabled states, error messages, and secondary buttons often fail contrast expectations.
Navigation That Cannot Be Operated
Menus, filters, carousels, modals, and dropdowns must work with keyboard and predictable focus behavior.
Broken Forms
Checkout forms often fail because labels, errors, required fields, focus handling, or field grouping are unclear.
Incorrect ARIA Use
ARIA can help, but incorrect ARIA can make a component worse. Native HTML should be preferred where possible.
Dynamic Content Without Announcement
Cart updates, filter changes, validation messages, and stock alerts need to be conveyed properly to assistive technologies.
Practical First Review Checklist
Structure And Semantics
- Are headings meaningful and nested sensibly?
- Do important controls use native elements where possible?
- Are landmarks and page regions understandable?
Navigation And Keyboard Operation
- Can users navigate menus, filters, product cards, modals, and checkout with keyboard?
- Is focus visible?
- Is focus order predictable?
Forms And Checkout
- Are labels connected to inputs?
- Are errors clear and close to the relevant field?
- Can users recover from errors without losing progress?
Content And Media
- Are meaningful images described?
- Are videos, if relevant, supported with captions or alternatives?
- Is important product information available as text?
Contrast And Visual Design
- Do text, buttons, badges, and error states meet reasonable contrast expectations?
- Are states conveyed by more than color alone?
Dynamic Components
- Are cart updates, filter changes, and validation messages announced appropriately?
- Are overlays and dialogs managed correctly?
How +Analytics Pro Helps
+Analytics Pro can support accessibility work with the WAVE Accessibility Checker, recurring website checks, issue workflows, and transparency outputs. Automated checks are useful for recurring detection and prioritization, but they do not replace manual WCAG evaluation or legal review.
Why Accessibility Also Matters For Search And AI Visibility
Accessible content tends to be better structured, easier to parse, and clearer for users and machines. Good headings, labels, text alternatives, and robust content architecture help search systems and AI systems understand pages more reliably. This is not a visibility guarantee, but it is a strong content-quality foundation.
Conclusion
Accessibility is not a decorative layer. For online shops, it affects whether people can find, understand, and buy products. Since the EAA has raised the practical relevance of accessibility for commercial services, shop teams should build a repeatable review and remediation routine.
Frequently Asked Questions
- Does the European Accessibility Act apply to every website?
No. Scope depends on the service, provider, market, and legal context. Online shops and ecommerce services should review applicability carefully.
- Do small businesses need accessible shops?
The EAA and national implementations include scope rules and exemptions. Small teams should not assume they are exempt without checking their situation.
- Is an accessibility overlay enough?
No. Overlays cannot reliably fix structural, semantic, content, keyboard, and process issues. Accessibility needs to be addressed in the site itself.
- Is WCAG conformance the same as BFSG compliance?
No. WCAG is a technical standard. BFSG is German law implementing the EAA. WCAG is an important reference, but legal compliance requires legal interpretation.
- How often should a shop be checked?
At minimum after major template changes, checkout changes, campaign launches, plugin changes, and regularly as part of operations.