Is Your Online Store EAA-Compliant? How to Audit in 5 Minutes
This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for guidance specific to your business situation.
EU Accessibility Act deadline: June 28, 2025 — already passed.
Any online store selling to EU customers must already comply with WCAG 2.1 Level AA. If your store is not accessible, you are technically in violation today. Enforcement is active across EU member states.
135M+
People with disabilities in the EU
27
EU member states enforcing EAA nationally
€100K
Maximum fine per violation in Germany
If your online store sells to European Union (EU) customers, this is not optional anymore. The European Accessibility Act (EAA) is now law, and the compliance deadline — June 28, 2025 — has already passed. That means your store could already be in violation, even if you had no idea this law existed.
This is not a future problem. It is a present one. Enforcement is active across EU member states. Disability advocacy groups are filing complaints. Regulatory bodies are issuing formal notices. And for ecommerce businesses — whether you are a boutique in Barcelona or a direct-to-consumer brand in Boston shipping to European customers — the exposure is real.
Ignoring EAA compliance exposes your business to:
- Legal risk: fines, enforcement actions, and formal complaints filed by regulators or individual users
- Reputational risk: accessibility failures can go public quickly, especially when advocacy organizations are involved
- Operational risk: emergency remediation is expensive, disruptive, and rushed fixes often introduce new problems
Find out if your store is in violation — in minutes
WCAGsafe scans your pages and PDFs for WCAG 2.1 AA violations instantly — no setup, no developer required.
Scan your store free →This comprehensive guide breaks down everything you need to know: who the EAA applies to, what it requires technically, how to audit your store in under five minutes, the most common violations, what fines and enforcement actually look like, and a detailed remediation checklist. By the end, you will know exactly how to protect your business — and your customers — while making your ecommerce store fully accessible.
1. EAA Is Now Law — The Deadline Passed, You May Already Be in Violation
The European Accessibility Act was adopted by the EU in 2019 to ensure that products and services are accessible to everyone, including people with disabilities. After a six-year implementation window, the compliance deadline for private sector businesses hit on June 28, 2025.
That window is closed. Any online store targeting EU customers should already be fully accessible under WCAG 2.1 AA standards. If your store is not, you are technically breaking the law right now — even if no enforcement action has arrived yet.
The 2026 enforcement reality
In 2025, most of the conversation was about preparation. That phase is over. In 2026, businesses are no longer asking whether they need to comply — they are asking how to fix violations fast enough to avoid consequences. Enforcement timelines in the EU tend to follow a predictable pattern:
- Deadline passes
- Advocacy groups begin systematic complaint filing
- Regulators issue formal notices requiring remediation within 30–90 days
- Non-responsive businesses face escalating fines
- High-profile cases get press coverage, increasing reputational damage
Ecommerce is particularly vulnerable because it is consumer-facing, transaction-dependent, and highly visible. A checkout that cannot be completed by a screen reader user is not a minor technical issue — it is a documented barrier to commerce that triggers specific EAA provisions.
2. Who the EAA Applies To
This is where many US-based businesses make a costly mistake: assuming the EAA only applies to European companies. It does not.
The EAA applies to any business that offers products or services to consumers in the EU — regardless of where that business is incorporated, headquartered, or operated. If your online store ships physical products to EU addresses, accepts payment in Euros, or markets to EU customers through advertising or localization, you are within scope.
Who specifically must comply
- EU-based ecommerce websites of all sizes (with limited exemptions for microenterprises)
- US-based online stores that accept EU shipping addresses or serve EU customers
- Global marketplaces and platforms that facilitate cross-border sales into the EU
- B2B platforms where the end user may be an EU consumer
- Mobile commerce apps that serve EU users alongside or instead of a web store
Who is exempt
The EAA includes an exemption for microenterprises — businesses with fewer than 10 employees and annual turnover or balance sheet below €2 million. For most ecommerce operations with meaningful EU sales, this exemption does not apply.
There is also a disproportionate burden clause that allows temporary exemption from specific requirements if full compliance would impose excessive financial burden. However, this requires formal application and does not apply to core transaction flows like checkout.
3. What EAA Requires for Online Stores
The EAA references WCAG 2.1 Level AA as the technical standard for digital accessibility — the same standard used by the US DOJ for ADA Title II compliance. For ecommerce specifically, these requirements break down into five critical areas.
3.1 Checkout Processes
The checkout flow is the highest-risk area for ecommerce EAA violations. Any barrier here directly prevents a person with a disability from completing a purchase — the core harm the EAA is designed to prevent. Your checkout must:
- Allow all users to complete transactions independently, without assistance
- Have every form field properly labeled so screen readers announce it correctly
- Present error messages accessibly — with text descriptions, not color alone
- Be fully keyboard navigable — no step should require a mouse or touchscreen gesture
- Meet minimum color contrast ratios (4.5:1 for normal text, 3:1 for large text)
- Not use CAPTCHA inaccessible to blind users without an accessible alternative
<label for> or aria-labelledby. A screen reader user hears "combo box" with no context — they cannot complete the purchase.3.2 Product Pages
Product pages are the second-highest risk area, particularly for stores with large catalogs. Every product image must have descriptive alt text, headings must structure product descriptions with semantic HTML, product videos require captions and transcripts, and dynamic content like carousels must be keyboard operable and announced by screen readers.
For large catalogs, this is a significant operational challenge. Automated tools can scan for missing alt text across your entire catalog and flag it for remediation.
3.3 Forms and Interactive Elements
Beyond checkout, most ecommerce stores have newsletter signups, account registration, returns requests, contact forms, and product reviews — all of which must meet WCAG 2.1 AA. Every field needs a programmatically associated label, required field indicators must not rely on color alone, and no form should create a keyboard trap.
3.4 PDFs and Downloadable Documents
This is one of the most overlooked areas in ecommerce. Product manuals, terms and conditions, return policies, and warranty documents must all be accessible. Use a PDF accessibility checker to audit every document linked from your store. A PDF distributed as a scanned JPEG is invisible to a blind customer — under EAA, that is a violation.
An accessible PDF requires proper tag structure, selectable text (not scanned images), defined reading order, labeled form fields, and document language metadata.
3.5 Mobile Accessibility
If you have a native mobile app or mobile web experience, it must meet the same standards as your desktop site. This includes screen reader support (VoiceOver on iOS, TalkBack on Android), accessible alternatives to swipe gestures, touch targets of at least 44x44 CSS pixels, text resizability to 200%, and autocomplete attributes on form fields.
4. How to Audit Your Store in 5 Minutes
A thorough accessibility audit takes time — but a high-risk scan that surfaces your most critical violations can be done in under five minutes.
Run an automated scan with WCAGsafe
WCAGsafe uses axe-core to detect WCAG 2.1 AA violations across your pages in minutes — missing alt text, contrast failures, missing form labels, keyboard focus issues, ARIA errors, and more. Start with your homepage, a high-traffic product page, the checkout flow, and any PDFs. WCAGsafe also supports PDF accessibility scanning directly.
Run a free WCAGsafe scan →Manual keyboard navigation test
Close your mouse and navigate your entire checkout using only Tab, Enter, and Space. If you get stuck at any point — a modal you cannot close, a dropdown you cannot open, a form you cannot submit — that is a critical EAA violation.
Screen reader smoke test
Enable VoiceOver (Mac: Command + F5) or download NVDA (free, Windows) and navigate to your checkout page. If you hear fields announced as "edit text" with no label, or images described only by filename, those are violations.
Prioritize by risk
Triage findings into Critical (checkout, payment forms), High (product pages, PDFs, filtering), Medium (marketing content, blogs), and Low (informational pages). Fix critical issues first.
5. Most Common Violations Found in Ecommerce
After scanning thousands of ecommerce pages, the same violations appear repeatedly. Knowing them can help you prioritize remediation.
| Violation | Description | Risk |
|---|---|---|
| Missing alt text | Product images with no or empty alt attributes | Critical |
| Insufficient color contrast | Text against low-contrast backgrounds | Critical |
| Unlabeled form fields | Checkout and signup fields with no programmatic label | Critical |
| Keyboard traps | Modals, overlays, or popups that cannot be dismissed by keyboard | Critical |
| Image-only PDFs | Scanned documents with no selectable text | Critical |
| Missing focus indicators | Keyboard users cannot see which element is focused | High |
| Empty link text | Links like "click here" or icon-only links with no accessible name | High |
| Uncaptioned videos | Product demos or promotional videos with no captions | High |
| Missing skip navigation | No way to skip repetitive header/navigation on every page | Medium |
| Complex dropdowns | Custom-styled menus inaccessible via keyboard | High |
| Dynamic carousels | Auto-rotating banners with no pause control | Medium |
| Missing error associations | Error messages not programmatically linked to their form field | High |
6. What Fines and Enforcement Look Like in the EU
Enforcement is handled at the national level, which means consequences vary by country. But the general framework is consistent: complaint, investigation, formal notice, remediation deadline, and fines for non-compliance.
| Country | Enforcement Body | Fine Range |
|---|---|---|
| Germany | Market surveillance authorities | Up to €100,000 |
| France | ARCOM and consumer protection bodies | Sanctions + public disclosure |
| Spain | AEPD and consumer protection bodies | €3,000 – €30,000+ |
| Netherlands | ACM (Authority for Consumers and Markets) | Active investigation |
| Italy | AGID + consumer protection bodies | Civil claims possible |
How complaints typically start
- A user with a disability encounters a barrier on your site
- They file a complaint with a national disability organization or market surveillance authority
- The authority contacts your business requesting a response and remediation timeline
- If no action is taken within 60–90 days, formal proceedings begin
- Fines and public enforcement notices follow
Case examples
Don't wait for a formal notice to find your violations
WCAGsafe scans your pages and PDFs in minutes and gives you a prioritized list of exactly what needs fixing — before enforcement finds you first.
Run a free scan now →7. A Complete EAA Compliance Fix Checklist
Use this checklist to systematically bring your store into full compliance. Work through it in priority order.
Phase 1: Audit
- ☐Run WCAGsafe automated scan on homepage, product page, checkout, and forms
- ☐Scan all PDFs linked from your store with WCAGsafe PDF checker
- ☐Complete keyboard-only navigation test through full checkout flow
- ☐Run basic screen reader test on checkout and product pages
- ☐Export and triage scan results by severity
Phase 2: Critical Fixes — Checkout & Transaction Flows
- ☐Add <label for> or aria-labelledby to every form field
- ☐Ensure all error messages are programmatically associated with their field
- ☐Remove all keyboard traps in modals, popups, and overlays
- ☐Add visible focus indicators to all interactive elements
- ☐Ensure checkout can be completed using only keyboard navigation
- ☐Add accessible CAPTCHA alternatives where CAPTCHA is used
- ☐Test color contrast on all form labels, buttons, and error messages (minimum 4.5:1)
Phase 3: Product Pages
- ☐Add descriptive alt text to all product images (not filenames or generic labels)
- ☐Audit and fix heading hierarchy (h1 > h2 > h3 — no skipped levels)
- ☐Add captions and transcripts to all product videos
- ☐Make image carousels keyboard operable with pause control
- ☐Ensure tabbed product specifications use proper ARIA tab pattern
- ☐Fix any zoom or lightbox features that trap keyboard users
Phase 4: PDFs and Downloads
- ☐Tag all PDFs with proper heading, paragraph, list, and table structure
- ☐Convert scanned/image PDFs to text using OCR
- ☐Set correct reading order for all tagged PDFs
- ☐Label all PDF form fields
- ☐Add document title and language metadata to all PDFs
- ☐Replace PDFs with HTML where possible — HTML is inherently more accessible
Phase 5: Mobile and App
- ☐Test iOS VoiceOver and Android TalkBack through full purchase flow
- ☐Replace all gesture-only interactions with accessible alternatives
- ☐Ensure all touch targets are at least 44x44 CSS pixels
- ☐Test text resize to 200% — no content should be cut off or overlapping
- ☐Add autocomplete attributes to all form fields
Phase 6: Governance and Monitoring
- ☐Publish an accurate Accessibility Statement on your site (required under EAA)
- ☐Include a working contact method for accessibility feedback in the statement
- ☐Schedule monthly automated scans with WCAGsafe to catch regressions
- ☐Add accessibility review to your QA checklist for all new releases
- ☐Train your development team on WCAG 2.1 AA requirements
- ☐Document your remediation progress for potential regulatory inquiries
8. Conclusion
The European Accessibility Act is enforceable today. For ecommerce businesses — whether you are based in the EU or selling to EU customers from anywhere in the world — the question is no longer whether you need to comply. The question is how quickly you can fix what is broken.
The risk is not abstract. Enforcement bodies are active. Disability organizations are filing complaints. Fines are being issued. And every day your checkout is inaccessible, you are also losing customers who simply cannot use your site.
You do not need to fix everything at once — you need to fix the most dangerous things first and have a documented remediation plan in place. Start with an automated scan, prioritize your critical violations, and work through the checklist above.
Identify your EAA violations in minutes
Run a free WCAGsafe scan on your online store — plain-English results, no setup required, PDF scanning included.
Scan your store free →Frequently Asked Questions
Does the EAA apply to US-based online stores?
Yes. The EAA applies to any business that offers products or services to consumers in the EU, regardless of where that business is located. If your store ships to EU addresses, accepts EU currencies, or markets to EU customers, you are within scope.
What is the fine for EAA non-compliance?
Fines vary by EU member state. Germany can issue fines up to €100,000. Spain has issued fines ranging from €3,000 to €30,000+. Some member states also allow civil claims from users affected by inaccessibility. Beyond fines, public enforcement notices can cause significant reputational damage.
What technical standard does the EAA require?
The EAA references WCAG 2.1 Level AA as the benchmark for digital accessibility. This covers perceivability, operability, understandability, and robustness — including requirements for alt text, color contrast, keyboard navigation, form labels, captions, and accessible PDFs.
Does EAA apply to mobile apps?
Yes. If you have a native iOS or Android app used by EU consumers, it must meet the same WCAG 2.1 AA standards as your website. This includes screen reader support, accessible gestures, sufficient touch target sizes, and text resizability.
Are small businesses (microenterprises) exempt?
Microenterprises — defined as businesses with fewer than 10 employees and annual turnover or balance sheet below €2 million — are exempt from the service accessibility requirements. However, most ecommerce businesses with meaningful EU sales do not qualify for this exemption.
Do PDFs on my store need to be accessible?
Yes. Product manuals, terms and conditions, return policies, warranty documents, and any other downloadable PDF must be accessible under EAA. This means proper tagging, selectable text (not scanned images), correct reading order, and accessible form fields.
Can an accessibility overlay widget make my store EAA-compliant?
No. Accessibility overlay widgets do not reliably solve WCAG violations and can introduce new barriers for screen reader users. They are not an accepted substitute for genuine remediation. EU enforcement bodies do not accept overlay-based compliance claims.
How is EAA different from ADA?
The EAA (EU) and ADA (US) both reference WCAG 2.1 AA, so the technical requirements are nearly identical. The key differences are enforcement jurisdiction and penalties. The ADA covers US consumers; the EAA covers EU consumers. A store accessible under one is generally accessible under the other.