EAA vs WCAG: Understanding the Difference

EAA vs WCAG: Understanding the Difference

Many organisations assume that WCAG compliance equals EAA compliance. This is not the case. While WCAG is a critical component, the EAA has a broader scope.

What is WCAG?

The Web Content Accessibility Guidelines (WCAG) are published by the W3C's Web Accessibility Initiative (WAI). WCAG 2.1, published in June 2018, is the version referenced by the EAA through the harmonised standard EN 301 549.

WCAG defines four principles (POUR):

1. Perceivable — Information must be presentable in ways users can perceive
2. Operable — Interface components must be operable
3. Understandable — Information and UI operation must be understandable
4. Robust — Content must be robust enough for assistive technologies

WCAG has three conformance levels: A (minimum), AA (target for most regulations), and AAA (highest).

What does the EAA add beyond WCAG?

1. Legal obligation, not a voluntary standard

WCAG is a technical standard — adoption is voluntary unless required by law. The EAA makes specific WCAG criteria legally binding across the EU.

2. Covers products AND services

WCAG focuses on web content. The EAA covers a wide range of products (hardware, ATMs, smartphones) and services (banking, transport, e-commerce).

3. Declaration requirement

The EAA mandates a public Annex V accessibility declaration. WCAG has no such requirement. This declaration must:

• Identify the service provider
• Identify the product or service
• Reference the standards used for assessment
• Be publicly accessible

4. Sector-specific obligations

The EAA's Annex I Section IV defines requirements specific to banking, transport, telecommunications, e-commerce, and publishing that go beyond general web accessibility.

5. Enforcement and penalties

WCAG non-compliance has no direct legal consequence (unless referenced by another law). EAA non-compliance can result in fines, product withdrawal, and service suspension.

The mapping between WCAG and Annex I

The harmonised standard EN 301 549 v3.2.1 maps WCAG 2.1 Level AA success criteria to EAA requirements. Key mappings include:

Requirements without WCAG equivalents

Some Annex I requirements have no direct WCAG mapping:

• I.1.a — Accessibility documentation (no WCAG equivalent)
• I.2.a — Communication services accessibility
• V.1.a-c — Declaration content requirements
• VI.a-b — Exemption criteria

These requirements must be assessed manually or through organisational processes, not automated scans.

Practical implications

1. Automated scans are necessary but not sufficient — they cover WCAG-mapped requirements but miss declaration and process obligations
2. You need both a technical AND legal compliance strategy — an automated WCAG scan, like the one RankProof runs, can cover many of the WCAG-mapped Annex I requirements, but the Annex V declaration and the rest of the legal documentation still have to be prepared separately
3. WCAG compliance is your foundation — start with WCAG 2.1 AA, then address the additional EAA requirements