Skip to content
Technical 6 min read

EAA vs WCAG: Understanding the Difference

EAA vs WCAG explained: how WCAG, EN 301 549 and the European Accessibility Act fit together, what WCAG 2.2 and EN 301 549 v4.1.1 change, what tests can prove.

RP
By RankProof
Editorial Team · RankProof

Short answer

WCAG is a technical standard from the W3C; the European Accessibility Act is EU law. The link between them is the harmonised standard EN 301 549, whose web chapter adopts WCAG — 2.1 Level AA in the version used today, 2.2 Level AA in the version published in September 2026. Meeting WCAG covers the interface, but the Act also asks for published accessibility information, sector-specific features and accessible support.

WCAG
W3C technical standard
EAA
EU law · Directive (EU) 2019/882
Bridge
EN 301 549 (web chapter = WCAG)
WCAG 2.1 A + AA
50 success criteria
WCAG 2.2 A + AA
55 success criteria
Beyond WCAG
Annex V information · sector rules

EAA vs WCAG: Understanding the Difference

"Are we WCAG compliant?" and "Do we meet the EAA?" are different questions. WCAG is a technical standard that says how to test web content. The European Accessibility Act (EAA) is a law that says which products and services must be accessible and what their providers must do. This guide shows how the two connect, what the law adds, and what changes with WCAG 2.2.

What WCAG is

The Web Content Accessibility Guidelines are published by the W3C. They are organised under four principles — perceivable, operable, understandable, robust — and each guideline has testable success criteria at three levels: A, AA and AAA. Laws and contracts usually ask for Level AA, which means meeting every A and AA criterion.

VersionPublishedA + AA criteria
WCAG 2.0December 200838
WCAG 2.1June 201850
WCAG 2.2October 202355

Each version builds on the last. WCAG 2.2 adds six criteria at A and AA and removes one (4.1.1 Parsing, now obsolete), so a page that meets WCAG 2.2 AA also meets 2.1 AA, apart from that removed criterion.

WCAG on its own creates no obligation. It becomes binding only when a law, a contract or a procurement rule refers to it.

What the EAA is

Directive (EU) 2019/882 sets accessibility requirements for a list of products (computers, phones, self-service terminals, e-readers) and consumer services (e-commerce, banking, transport, electronic communications, audiovisual media access, e-books). It has applied since 28 June 2025 through each EU country's national law. Our guide "What is the European Accessibility Act?" covers scope, dates and exemptions.

The Act describes outcomes in plain language. For websites and apps, Annex I, Section III asks that they be made accessible "in a consistent and adequate way by making them perceivable, operable, understandable and robust" — the four WCAG principles, but without a single success criterion.

The bridge: EN 301 549

The Act does not name a standard. Instead, a product or service that meets a harmonised standard cited in the EU's Official Journal is presumed to conform. For information and communication technology that standard is EN 301 549, written by ETSI, CEN and CENELEC.

EN 301 549 covers more than websites. Its chapters include web content (chapter 9, which adopts WCAG), non-web documents such as PDFs (chapter 10), software including mobile apps (chapter 11), documentation and support services (chapter 12), and hardware and two-way voice communication.

  • v3.2.1 (2021) adopts WCAG 2.1 A and AA. It is cited for public-sector websites under the Web Accessibility Directive and is the reference most EAA audits use today.
  • v4.1.1 (September 2026) adopts WCAG 2.2 A and AA and was prepared at the European Commission's request for the EAA. Until it is cited in the Official Journal, it does not give presumption of conformity.

What the EAA asks for beyond WCAG

ObligationWhere it comes fromCovered by WCAG?
Accessible website and app interfaceAnnex I, Section IIIYes — WCAG through EN 301 549
Mobile apps and online documentsAnnex I, Section IIIThrough EN 301 549 chapters 10 and 11
Published information on how the service meets the requirementsArticle 13, Annex VNo
Support services (help desk, call centre) give accessibility information in accessible formatsAnnex I, Section IIINo
E-commerce: show the accessibility information of the products you sellAnnex I, Section IVNo
Accessible identification, security and paymentAnnex I, Section IVPartly — the interface yes, a third-party provider's flow is theirs to fix too
Banking: information understandable at no more than level B2Annex I, Section IVNo
Documented assessment when claiming disproportionate burdenArticle 14, Annex VINo
Enforcement by national authorities, penaltiesArticles 23 and 30No

The right-hand column is why a clean WCAG report is not the end of the work. The Annex V information, support processes and sector features are organisational tasks that no scanner can see.

What changes with WCAG 2.2

The six new A and AA criteria are practical, and most are cheap to meet when a page is built:

  • 2.4.11 Focus Not Obscured (Minimum), AA — the element with keyboard focus is not completely hidden, for example behind a sticky header or a cookie banner.
  • 2.5.7 Dragging Movements, AA — anything done by dragging also works with single clicks or taps.
  • 2.5.8 Target Size (Minimum), AA — click and tap targets are at least 24 × 24 CSS pixels, or have enough space around them.
  • 3.2.6 Consistent Help, A — help options (contact link, chat, phone) appear in the same place on every page.
  • 3.3.7 Redundant Entry, A — users are not asked to type the same information twice in one process.
  • 3.3.8 Accessible Authentication (Minimum), AA — signing in does not depend on remembering or transcribing something; allow pasting and password managers.

Our recommendation: keep testing against WCAG 2.1 AA, the baseline authorities use today, and build new templates to WCAG 2.2 AA. When v4.1.1 is cited, you will have nothing to redo.

What automated tests can and cannot prove

Automated rules check what code can show: missing alt attributes, unlabeled fields, contrast ratios, invalid ARIA, missing page language. They cannot judge whether alt text describes the image, whether the reading and focus order make sense, whether captions are accurate, or whether a checkout can be completed with a keyboard and a screen reader.

For example, on 7 October 2026 RankProof's accessibility scanner ran WCAG 2.1 A and AA rules on our own homepage: no issues the rules could detect, 22 rules passed, and one check — colour contrast — flagged for a person to review, because the rules could not decide it automatically. That is a good starting point, not a conformance claim: the manual checks still have to be done.

A workable split:

  1. Automated scan of every template — fast, repeatable, catches regressions.
  2. Manual checks of the key journeys: keyboard only, a screen reader, 200% zoom and a 320 px wide window.
  3. Content review: alt text, link text, headings and plain language.
  4. Paperwork: the Annex V information, a support process, and records of what you tested and fixed.

Common misunderstandings

  • "We pass WCAG, so we comply with the EAA." Only for the interface part. The information, support and sector obligations are separate.
  • "The EAA requires WCAG 2.2." Not yet. It requires the outcomes in Annex I; WCAG 2.1 AA through EN 301 549 v3.2.1 is the usual way to show them until v4.1.1 is cited.
  • "An overlay widget makes the site compliant." A script added on top cannot fix missing labels, wrong structure or inaccessible documents at the source, and it can interfere with users' own assistive technology.
  • "AAA is required." No law asks for full Level AAA; WCAG itself says it is not possible for all content.

Start with a free check

Run the free audit or pick one of the tools — no account, and every result explains what to fix.

Try Free Scan