European Accessibility Act 2025: What Website Owners Must Fix Before the Deadline
The EAA applies from June 28, 2025. If you sell to EU consumers online, your website and e-commerce flows likely must meet WCAG 2.1 AA. Here is a practical compliance checklist.
TL;DR
- The European Accessibility Act (EAA) has applied since June 28, 2025 — EU member states enforce accessibility for covered products and services sold to consumers.
- Covered e-commerce websites and apps must meet EN 301 549, which embeds WCAG 2.1 Level AA for web interfaces.
- Top failure categories: missing alt text, keyboard traps, insufficient color contrast, unlabeled forms, non-semantic headings, inaccessible modals.
- Remediation timeline: 2–8 weeks for marketing sites; 2–4 months for complex e-commerce — depending on debt and CMS constraints.
- Nova Sidera audits accessibility as part of our €50 consultation at /consultation/ — technical SEO, WCAG quick scan, and prioritized fixes; full remediation from €4,500 fixed-scope.
What Is the European Accessibility Act?
The European Accessibility Act (Directive (EU) 2019/882) harmonizes accessibility requirements across the EU single market. Before the EAA, accessibility law was a patchwork of national rules. Now, certain products and services must meet consistent functional accessibility requirements when placed on the EU market.
The Act focuses on consumer-facing digital services — not every brochure website on the internet, but any business that falls within its scope and sells to EU consumers.
Key official resources:
- EU EAA summary (European Commission)
- EN 301 549 standard (ETSI) — the harmonized technical specification
- W3C Web Accessibility Initiative (WAI) — WCAG guidelines and techniques
Non-compliance exposes businesses to market surveillance actions, contract penalties in public procurement, and reputational damage — plus the ongoing cost of excluding 15–20% of EU adults who live with disabilities.
Accessibility is also an SEO and GEO signal: semantic HTML, clear headings, and descriptive link text help search engines and AI crawlers parse your content.
Who Must Comply with the EAA?
The EAA covers specific service categories. For website owners, the most relevant are:
| Service category | Examples | Web impact |
|---|---|---|
| E-commerce | Online shops, SaaS sold to consumers, marketplaces | Full purchase flow: browse, cart, checkout, account |
| Consumer banking / financial services | Retail banking apps, payment services | Transaction interfaces |
| E-books and digital publishing | EPUB platforms, reader apps | Reader UI + store |
| Telecom / audiovisual consumer equipment | Hardware UI — less relevant to pure web agencies | Embedded web views |
| Passenger transport services | Booking websites, mobile tickets | Booking + ticketing flows |
| Emergency communications (112) | Public-sector interfaces | Critical access paths |
B2B-only sites with no consumer sales fall outside direct EAA scope — but enterprise buyers increasingly require WCAG conformance in RFPs. If you sell SaaS to EU SMEs or consumers, assume you are in scope.
Micro-enterprises (under 10 employees and ≤ €2M turnover) get limited exemptions for service provision, but not for product obligations — and exemptions are narrower than founders assume. Consult national transposition law in your target markets (Germany BFSG, France, Italy each transposed separately).
What WCAG Level Do You Need to Meet?
For web content, EN 301 549 points to WCAG 2.1 Level AA. Level A alone is insufficient. Level AAA is optional except for specific sub-clauses.
The four WCAG principles — Perceivable, Operable, Understandable, Robust (POUR) — translate into concrete requirements:
Perceivable
- 1.1.1 Non-text content: Every meaningful image has alt text; decorative images use
alt="". - 1.3.1 Info and relationships: Headings, lists, and tables use semantic HTML — not styled
<div>s. - 1.4.3 Contrast (Minimum): 4.5:1 for normal text, 3:1 for large text and UI components.
- 1.4.11 Non-text contrast: Icons and form borders meet 3:1 against adjacent colors.
Operable
- 2.1.1 Keyboard: All functionality available via keyboard alone — no mouse-only traps.
- 2.4.1 Bypass blocks: Skip navigation link to main content.
- 2.4.7 Focus visible: Clear focus indicator on interactive elements.
- 2.5.3 Label in name: Visible button labels match accessible names.
Understandable
- 3.3.2 Labels or instructions: Every form field has a visible
<label>oraria-label. - 3.2.4 Consistent identification: Same icons and labels mean the same thing site-wide.
- 3.1.1 Language of page:
<html lang="en">set correctly; language switches marked.
Robust
- 4.1.2 Name, role, value: Custom components expose correct ARIA roles and states.
- Valid HTML — parsers and assistive tech depend on it.
Use the WCAG 2.1 Quick Reference as your checklist. Publish an accessibility statement page describing conformance level, known gaps, and contact for feedback — required in several member states.
What Are the Most Common Website Failures?
From audits we run on marketing and e-commerce sites, these issues recur:
| Issue | WCAG criterion | Fix complexity |
|---|---|---|
Missing / generic alt text (alt="image") |
1.1.1 | Low — content pass |
| Color contrast on muted text and badges | 1.4.3 | Low–medium — design tokens |
| Inaccessible custom dropdowns and modals | 2.1.1, 4.1.2 | Medium — component refactor |
| Form errors not announced to screen readers | 3.3.1, 4.1.3 | Medium |
| Auto-playing video without pause control | 2.2.2 | Low |
<div onclick> instead of <button> |
4.1.2 | Medium — semantic HTML |
| Missing focus trap management in dialogs | 2.4.3 | Medium |
| PDF-only documents without accessible HTML alternative | 1.1.1, 2.4.5 | High — content migration |
Automated scanners (axe DevTools, WAVE, Lighthouse accessibility audit) catch contrast and missing-label issues fast. They miss keyboard flow problems, screen reader announcement order, and "makes sense out of context" alt text — manual testing is non-negotiable.
Test with NVDA (Windows, free) or VoiceOver (macOS, built-in). Tab through your checkout without a mouse. If you get stuck, you fail 2.1.1.
How Should You Plan Remediation?
A practical phased roadmap:
Phase 1 — Audit (1–2 weeks)
- Automated scan of all templates and top 20 URLs.
- Manual keyboard + screen reader pass on critical paths: home, product, cart, checkout, contact form.
- Deliverable: prioritized issue list tagged Blocker / Major / Minor with WCAG references.
Phase 2 — Quick wins (1–2 weeks)
- Alt text, labels, lang attributes, skip links, focus styles.
- Pause controls on media; fix contrast on body text and buttons.
- Often 40–60% of automated findings.
Phase 3 — Component fixes (2–6 weeks)
- Refactor modals, menus, carousels, date pickers to accessible patterns.
- Use WAI-ARIA Authoring Practices Guide (APG) for combobox, dialog, and tabs patterns.
- Prefer native
<button>,<select>,<dialog>over custom widgets when possible.
Phase 4 — Process and statement (ongoing)
- Accessibility acceptance criteria in Definition of Done.
- Regression testing in CI with axe-core or pa11y.
- Public accessibility statement with feedback email and remediation SLA.
For a marketing site on a modern static stack (like Eleventy or Next.js), Phase 1–3 often completes in 4–8 weeks. Complex Shopify or custom e-commerce with legacy templates may need 3–4 months.
What Does EAA Compliance Cost?
| Scope | Typical budget (EUR) | Notes |
|---|---|---|
| Audit + report only | €500–€2,000 | Our €50 consultation covers a rapid scan + call; deep audit quoted separately |
| Marketing site remediation | €4,500–€10,000 | Fixed-scope friendly — Nova Sidera Project from €4,500 |
| E-commerce full flow | €10,000–€30,000 | Checkout, account, filters, CMS templates |
| Ongoing retainer | €1,500–€4,000/month | Part of dedicated team from €6,500/month |
Cheaper to build accessible from day one. Retrofitting a React component library with 40 custom widgets costs multiples of doing it right in the first sprint.
Legal review of your accessibility statement adds €500–€1,500 depending on jurisdiction — not a substitute for technical conformance.
What Should You Do Next?
If the June 2025 deadline passed and your site is not audited:
- Run Lighthouse accessibility on home, product, and checkout — export report.
- Tab-test your contact form and main CTA — fix blockers this week.
- Publish a draft accessibility statement — even "partially conformant, improvements in progress" shows good faith.
- Book Nova Sidera's €50 audit at /consultation/ — technical SEO, WCAG quick scan, GEO readiness, 30-minute review; credited toward remediation.
- Quote fixed-scope fixes from €4,500 if you need implementation, not just a report.
Accessibility law is not going away — and accessible sites convert better for everyone, not only assistive-tech users. Clear structure, readable contrast, and keyboard-friendly flows are the same properties that help GEO citations and mobile SEO.
Frequently asked questions
Did the EAA deadline already pass?
Yes — the European Accessibility Act has applied since June 28, 2025. Member states enforce it through national market surveillance. If you sell to EU consumers and have not audited your site, treat compliance as urgent.
Does WCAG 2.1 Level AA apply to all websites?
Not all websites — but e-commerce services, booking systems, and consumer-facing digital products covered by the EAA must meet EN 301 549, which references WCAG 2.1 AA for web content. Many B2B sites voluntarily adopt AA as best practice.
Can automated tools alone prove compliance?
No. Tools like axe or Lighthouse catch ~30–40% of issues. Manual keyboard testing, screen reader review, and cognitive checks are required for a defensible conformance statement.
Need help with your product?
We build MVPs, audit existing sites for SEO & GEO, and ship production software from Montenegro.