WCAG vs EAA: What's the Difference and Which One Applies to You?
"WCAG" and "EAA" are often used interchangeably — but they are fundamentally different things. WCAG is a technical standard. EAA is EU law. Confusing the two leads businesses to either over-engineer their compliance or completely miss legal requirements that could expose them to fines.
📏 WCAG
- Web Content Accessibility Guidelines
- Created by W3C (international standards body)
- A technical specification — not law
- Used globally as a reference
- Has levels: A, AA, AAA
- Current version: WCAG 2.2
- No penalties — just guidelines
⚖️ EAA
- European Accessibility Act (Directive 2019/882)
- Created by the European Parliament
- EU law — legally binding
- Applies to EU markets only
- References WCAG 2.1 AA as the standard
- In force since June 28, 2025
- Fines up to €250,000 for non-compliance
Think of It This Way
If road safety were the analogy: WCAG is the Highway Code — a documented set of rules for safe driving. EAA is the law that requires you to actually follow those rules. Breaking the Highway Code alone has no legal consequence; breaking the law does.
WCAG exists to define what accessible means. EAA uses WCAG as its technical benchmark and adds the legal obligation to meet it.
Full Comparison
| WCAG 2.1 / 2.2 | EAA (European Accessibility Act) | |
|---|---|---|
| Type | Technical standard | EU law (Directive) |
| Created by | W3C (World Wide Web Consortium) | European Parliament & Council |
| Enforced by | Nobody — voluntary | National government authorities |
| Applies to | Anyone who wants to use it | Businesses serving EU customers |
| Penalty | None | Fines up to €250,000+ |
| Legal force | ❌ No | ✅ Yes — since June 28, 2025 |
| Levels | A, AA, AAA | Requires WCAG 2.1 Level AA minimum |
| Accessibility Statement | Not required | ✅ Legally required |
| Scope | Web content only | Web, apps, software, e-books, ATMs |
Which Level of WCAG Does the EAA Require?
The EAA requires WCAG 2.1 Level AA as its minimum technical standard. This means achieving Level A and Level AA success criteria.
Level AAA (the highest level) is not required by the EAA — it is aspirational. Most websites cannot achieve full AAA compliance without fundamentally compromising usability.
💡 Practical tip: Target WCAG 2.2 Level AA — it's backward compatible with 2.1 (so you satisfy the EAA requirement) and includes better support for mobile and cognitive accessibility that the 2.1 standard lacks.
Does WCAG Compliance = EAA Compliance?
Not automatically. The EAA adds requirements beyond just meeting WCAG criteria:
- ✅ WCAG 2.1 AA technical compliance — required
- ✅ Accessibility Statement — required (WCAG doesn't mention this)
- ✅ A feedback/contact mechanism for accessibility issues
- ✅ A process for responding to user complaints
- ✅ An escalation route to national enforcement body
Many businesses think "we fixed our alt text and labels, we're done." But without the Accessibility Statement, you are technically non-compliant with the EAA — regardless of your WCAG score.
Quick Decision Guide
| Your situation | What applies? |
|---|---|
| Building a website in the UK post-Brexit | WCAG 2.1 AA (referenced by UK accessibility regulations) |
| Selling to EU customers from anywhere | EAA (WCAG 2.1 AA + Statement) |
| US company with EU website visitors | EAA applies if you serve EU customers |
| Public sector website in the EU | Web Accessibility Directive (already enforced since 2016) |
| Small business (<10 employees, <€2M turnover) | Possible exemption — check your country's rules |
Check Your EAA Compliance in 30 Seconds
AccessPatch scans your site for WCAG violations and generates your legally-required Accessibility Statement — all in one tool.
Start Free 14-Day Trial →