EN 301 549 vs WCAG 2.2 2026 | European Accessibility Standard Comparison

Last updated: 2026-04-12

EN 301 549 is the European harmonized standard for ICT accessibility, while WCAG 2.2 is the W3C's internationally recognized Web Content Accessibility Guidelines. These two standards are closely related but serve different audiences and legal contexts. EN 301 549 was developed by ETSI, CEN, and CENELEC at the request of the European Commission and covers a broader range of ICT products than just websites — including mobile apps, software, hardware, and documents. WCAG 2.2, maintained by the W3C, focuses specifically on web content and provides the foundational technical criteria that EN 301 549 incorporates by reference. With the European Accessibility Act (EAA) taking full effect in June 2025, organizations doing business in the EU must demonstrate compliance with EN 301 549. For most web products, meeting WCAG 2.1 Level AA is the practical starting point, but EN 301 549 extends requirements beyond the web. Understanding how the two standards relate — and where they diverge — is essential for any organization facing EU accessibility obligations or seeking to align with international best practice.

At a Glance

Feature EN 301 549 WCAG 2.2
Scope Web, mobile apps, software, documents, hardware, ICT services Web content (browsers and assistive technology); limited mobile guidance
Legal mandate in the EU Yes — required under EAA (private sector from June 2025) and Web Accessibility Directive (public sector) No direct mandate; referenced by EN 301 549 for web content requirements
Web content requirements Incorporates WCAG 2.1 AA by reference (clauses 9 and 10) WCAG 2.2 defines the criteria directly; more up-to-date than EN 301 549's reference
Mobile app requirements Yes — clause 11 covers non-web software including native mobile apps Limited — WCAG 2.2 applies to mobile browsers but not fully to native apps
Document accessibility Yes — clause 10 covers non-web documents (PDFs, Word, etc.) No — WCAG does not cover non-web document formats directly
Testing tool support Limited — few automated tools test against EN 301 549 holistically Excellent — axe, WAVE, Lighthouse, Pa11y all test against WCAG criteria
International adoption Primarily EU; referenced in some international procurement standards Global — adopted by US Section 508, Canada AODA, Australia DDA, UK Equality Act
Conformance reporting Accessibility Statement required under Web Accessibility Directive; VPAT-equivalent ACR for procurement VPAT/ACR using WCAG 2.x conformance levels is industry standard for procurement

EN 301 549

Type: European harmonized ICT accessibility standard Pricing: Free to download from ETSI website. Compliance audits typically $5,000–$30,000+ depending on product scope Best for: Organizations subject to EU law — public sector bodies, and private sector companies selling products/services in the EU — who need a single standard covering web, mobile, software, and documents.

Pros

  • Legally mandated for EU public sector bodies and, from June 2025, for private sector products/services under the EAA
  • Covers all ICT product types — websites, mobile apps, desktop software, documents, and hardware — in a single standard
  • Incorporates WCAG 2.1 AA by reference for web content, so web teams already familiar with WCAG have a strong foundation
  • Includes additional functional performance statements that go beyond WCAG, addressing real-world use with assistive technology
  • Provides explicit guidance for non-web ICT that WCAG does not address, such as closed functionality and biometric authentication

Cons

  • Large and complex document spanning 200+ pages, difficult to navigate without accessibility expertise
  • Enforcement mechanisms and audit methodologies vary by EU member state, creating compliance uncertainty
  • Hardware and telecommunications requirements are outside the expertise of most web development teams
  • Periodic updates lag behind the rapidly evolving ICT landscape, with v3.1.1 being the current version as of 2019

WCAG 2.2

Type: W3C international web accessibility guideline Pricing: Free to use. Third-party audits range from $3,000–$25,000 depending on site scope Best for: Web development teams and organizations that need a clear, testable technical standard for web and mobile browser-based content, especially those operating under multiple international jurisdictions.

Pros

  • Internationally recognized baseline adopted by accessibility laws in the US (Section 508), Canada (AODA), Australia (WCAG 2.1), and the EU (EN 301 549)
  • Clear, testable success criteria organized by conformance level (A, AA, AAA), making compliance evaluation straightforward
  • WCAG 2.2 adds 9 new success criteria over 2.1, including improvements for mobile users and cognitive accessibility
  • Extensive supporting documentation, techniques, and understanding documents available from the W3C
  • Widely supported by testing tools — virtually every accessibility scanner tests against WCAG criteria

Cons

  • Covers only web content — does not address native mobile apps, desktop software, hardware, or PDF documents in depth
  • Does not have direct legal weight on its own — legal mandates reference WCAG at specific versions (often 2.1 AA, not yet 2.2)
  • Success criteria can be ambiguous in edge cases, requiring significant expertise to interpret correctly
  • AAA criteria are aspirational and rarely required by law, which can cause organizations to overlook high-impact improvements

Our Verdict

For organizations operating in the EU, EN 301 549 is the legally relevant standard, and meeting it for web content is substantially equivalent to meeting WCAG 2.1 Level AA — which remains the most pragmatic starting point. However, EN 301 549's broader scope matters if your products include native mobile apps, desktop software, or documents: those are covered by clauses not present in WCAG. Organizations outside the EU can safely focus on WCAG 2.2 Level AA as their primary benchmark, knowing it satisfies most international legal requirements. The practical recommendation for most teams is to target WCAG 2.2 AA as your technical standard, use an EN 301 549 conformance report (ACR) template for EU procurement, and address non-web ICT requirements with clause-specific review. Do not treat them as competing standards — EN 301 549 is a superset that includes WCAG for web content, with additional requirements layered on top.

Further Reading

Other Comparisons