---
title: "WCAG Evidence for the EU Accessibility Act and EN 301 549"
canonical_url: "https://www.sorena.io/artifacts/eu/accessibility-act/faq/wcag-evidence"
source_url: "https://www.sorena.io/artifacts/eu/accessibility-act/faq/wcag-evidence"
author: "Sorena AI"
description: "When WCAG test evidence helps EAA work, how it maps through EN 301 549, and why WCAG alone does not prove European Accessibility Act compliance."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "EU Accessibility Act WCAG evidence"
  - "EN 301 549 WCAG mapping"
  - "EAA accessibility testing"
  - "WCAG compliance evidence"
  - "EU Accessibility Act"
  - "EAA"
  - "EN 301 549"
  - "WCAG evidence"
  - "Accessibility testing"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# WCAG Evidence for the EU Accessibility Act and EN 301 549

When WCAG test evidence helps EAA work, how it maps through EN 301 549, and why WCAG alone does not prove European Accessibility Act compliance.

*FAQ* *EU Accessibility Act*

## WCAG evidence for EAA and EN 301 549

WCAG test results are useful EAA evidence when they are tied to a covered website, mobile app, document, software interface, or service journey and mapped to the relevant EN 301 549 requirement.

They are not, by themselves, a complete European Accessibility Act compliance conclusion: EAA scope, Annex I requirements, harmonised-standard coverage, technical documentation, service information, and any Article 14 exception still need separate records.

WCAG evidence is useful for EU Accessibility Act work when it is scoped, versioned, and mapped through EN 301 549. It can show that specific web content, non-web documents, or software screens satisfy WCAG-derived EN 301 549 requirements, but it does not prove every EAA duty for a product or service, and it should not be described as an EAA compliance certificate.

## Where WCAG evidence fits

The European Accessibility Act makes the applicable Annex I accessibility requirements the legal target for covered products and services. Article 15 creates a presumption of conformity only where products or services conform with harmonised standards, or parts of them, whose references have been published in the Official Journal of the European Union and only so far as those standards cover the relevant EAA requirements.

EN 301 549 is the practical ICT bridge. ETSI describes it as a European standard for ICT products and services and says it applies to software, hardware, and combinations of hardware and software. The current EN 301 549 V3.2.1 page says the standard supports the Web Accessibility Directive and is planned to be updated to support Directive (EU) 2019/882.

For WCAG evidence, the important point is narrow: EN 301 549 V3.2.1 reflects WCAG 2.1 content in clauses 9, 10, and 11 for web content, non-web documents, and software, and its Annex C explains how to determine conformance with individual requirements. A WCAG report is strongest when it is written as evidence for those EN 301 549 requirements, not as a standalone EAA conclusion.

- Use WCAG evidence for web pages, documents, and software user interfaces where the relevant EN 301 549 clause points to WCAG-derived criteria.
- Keep a separate EAA mapping from the covered product or service to Annex I and to any EN 301 549 clauses relied on.
- Check whether the harmonised standard or technical specification relied on has OJEU status for the relevant EAA requirement before using presumption-of-conformity language.
- Avoid saying that WCAG conformance proves EAA compliance for hardware controls, packaging, support services, service information, economic-operator obligations, or Article 14 assessments unless those items have their own evidence.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the legal target: EAA Annex I requirements, Article 15 presumption of conformity, technical documentation, service information, and Article 14 exception records.
- [ETSI - EN 301 549 V3 harmonized European Standard for ICT Accessibility](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Explains EN 301 549 scope for ICT products and services and its relationship to web, mobile, software, hardware, and future EAA support.
- [European Commission - Harmonised standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports the distinction between voluntary harmonised standards and mandatory legal requirements, including OJEU publication for presumption of conformity.
- [W3C - Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG21/?ref=sorena.io) - Supports WCAG criteria referenced by EN 301 549 V3.2.1 for web content, documents, and software evidence.

## What the evidence record should contain

A useful WCAG evidence record lets a reviewer reconstruct what was tested and why it was relevant. Treat each record as a clause-level test artifact: identify the asset, the user journey or screen, the EN 301 549 requirement, the WCAG success criterion where applicable, the test method, the result, the defect, and the fix.

For products, the EAA technical documentation must make it possible to assess conformity with relevant accessibility requirements and list harmonised standards or technical specifications applied in full or in part. For services, the service provider must explain how the service meets the applicable accessibility requirements and keep that information for as long as the service is in operation. WCAG evidence should feed those records rather than replace them.

- Record asset identity: URL, app version, document version, product model, service flow, locale, and release date or build identifier.
- Record scope: in-scope pages, templates, states, user journeys, documents, software screens, and the reason any item was excluded.
- Record method: WCAG version, EN 301 549 clause, test procedure, tool output, manual checks, browser, operating system, device, assistive technology, and tester.
- Record outcome: pass, fail, not applicable, defect severity, remediation owner, fix evidence, regression result, and residual limitation.
- Record legal mapping separately: EAA Annex I requirement, harmonised-standard part relied on, OJEU or technical-specification basis if used, and whether the conclusion is a narrow test result or a broader compliance assessment.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the need for technical documentation for products and public service information explaining how applicable accessibility requirements are met.
- [ETSI - EN 301 549 V3 harmonized European Standard for ICT Accessibility](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the clause-level EN 301 549 mapping for ICT, including web pages, mobile applications, desktop applications, hardware, and combinations of hardware and software.
- [W3C - Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG21/?ref=sorena.io) - Supports the success-criterion layer used in WCAG-derived testing evidence.

## What WCAG cannot prove by itself

WCAG is not the same thing as EN 301 549, and EN 301 549 is not the whole EAA analysis. EN 301 549 includes functional performance statements and requirements beyond WCAG-derived web criteria, and the EAA includes legal duties about covered products and services, economic operators, conformity assessment, service information, corrective action, and cooperation with authorities.

Do not convert a clean WCAG test into unsupported claims such as 'EAA compliant', 'EN 301 549 compliant', or 'presumed compliant' unless the record shows the exact scope of the claim and the standards or technical specifications actually relied on. If the test covered only sampled pages, say that. If it covered only a checkout journey, say that. If documents, mobile app screens, hardware controls, support services, or procurement evidence were not tested, say that too.

- WCAG evidence does not prove that a product or service is covered or excluded under the EAA.
- WCAG evidence does not prove compliance with all Annex I requirements for products, services, packaging, instructions, support services, or emergency communications.
- WCAG evidence does not prove that a harmonised standard creates presumption of conformity for an EAA requirement unless the OJEU and coverage conditions are met.
- WCAG evidence does not support an Article 14 fundamental-alteration or disproportionate-burden position unless that separate assessment is documented.
- WCAG evidence does not remain reliable after material design, content, platform, supplier, standard, or service changes unless regression testing confirms it.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the broader EAA duties beyond WCAG testing, including Annex I, service-provider information, conformity assessment, and Article 14 assessment records.
- [European Commission - Harmonised standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports careful wording around voluntary standards, OJEU references, and alternate technical solutions.
- [ETSI - EN 301 549 V3 harmonized European Standard for ICT Accessibility](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the point that EN 301 549 contains broader ICT requirements than a generic WCAG audit alone.

## Review checklist for WCAG evidence

Use this checklist before relying on a WCAG report in an EAA evidence pack. The goal is a bounded, reviewable conclusion: what the test proves, what it does not prove, and what additional EAA or EN 301 549 evidence is still needed.

- State the claim in narrow language: for example, 'tested checkout pages against listed WCAG 2.1 success criteria mapped to EN 301 549 clause 9', not 'EAA compliant'.
- Map each WCAG finding to the EN 301 549 requirement and the relevant EAA Annex I requirement or explain why the result is only design-quality evidence.
- Separate sampled evidence from full-coverage evidence and keep the sampling rationale with the report.
- Keep failed criteria visible until remediation and regression evidence is attached.
- Review the record when covered journeys, content templates, software releases, assistive-technology support, suppliers, standards, or legal requirements change.
- Escalate legal wording before using presumption-of-conformity, Article 14, CE marking, EU declaration of conformity, or authority-response language.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the need to keep EAA records tied to applicable accessibility requirements, technical documentation, service information, and exceptions.
- [ETSI - EN 301 549 V3 harmonized European Standard for ICT Accessibility](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports using EN 301 549 as the ICT requirement map rather than treating WCAG as the whole compliance framework.
- [European Commission - Harmonised standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports escalation before using presumption-of-conformity language because harmonised-standard references must be published in the OJEU for that legal effect.

## Primary sources

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Primary legal source for EAA scope, Annex I accessibility requirements, Article 15 presumption of conformity, technical documentation, service information, and Article 14 exception records.
  - Quote: "accessibility requirements for products and services"
- [ETSI - EN 301 549 V3 harmonized European Standard for ICT Accessibility](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Standards source for EN 301 549 scope, ICT applicability, structure, and relationship to WCAG-derived web, document, and software requirements.
  - Quote: "Accessibility requirements for ICT products and services"
- [European Commission - Harmonised standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Commission source for how harmonised standards support EU legal requirements, voluntary use, and OJEU publication for presumption-of-conformity effects.
  - Quote: "The use of these standards remains voluntary."
- [W3C - Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG21/?ref=sorena.io) - WCAG source for the success criteria referenced by EN 301 549 V3.2.1 in clauses covering web content, documents, and software.
  - Quote: "Web Content Accessibility Guidelines"

## Topic Guides

- [EAA Accessibility Conformance Statement Template](/artifacts/eu/accessibility-act/accessibility-conformance-statement-template.md): Template language for an EU Accessibility Act conformance statement covering scope, Annex I mapping, service information, standards, support routes, evidence, and limits.
- [EAA Article 14 disproportionate burden workflow](/artifacts/eu/accessibility-act/disproportionate-burden-assessment-workflow.md): A grounded EU Accessibility Act workflow for Article 14 fundamental alteration and disproportionate burden assessments, records, reassessment triggers, and evidence.
- [EAA conformance statements: products, services, EN 301 549 evidence](/artifacts/eu/accessibility-act/faq/conformance-statements.md): What an EU Accessibility Act conformance statement should include, with product EU declarations, service information, EN 301 549 and WCAG evidence boundaries.
- [EAA e-commerce checkout accessibility FAQ](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md): How to test an e-commerce checkout under the European Accessibility Act, including service scope, payment and identification flows, service information, and evidence.
- [EAA e-commerce checkout accessibility guide](/artifacts/eu/accessibility-act/e-commerce-checkout-accessibility.md): Grounded EU Accessibility Act guide for accessible e-commerce checkout scope, payment and identification requirements, evidence, standards mapping, and customer information.
- [EAA EN 301 549 and WCAG mapping](/artifacts/eu/accessibility-act/en-301-549-and-wcag-mapping.md): Map European Accessibility Act Annex I requirements to EN 301 549 and WCAG evidence without overstating what WCAG tests can prove.
- [EAA EN 301 549 clause mapping for ICT evidence](/artifacts/eu/accessibility-act/en-301-549-clause-mapping.md): Map EN 301 549 clauses to EU Accessibility Act evidence, Annex I outcomes, product and service records, and gaps that need non-ICT support.
- [EAA procurement clauses and accessibility acceptance criteria](/artifacts/eu/accessibility-act/procurement-language-and-acceptance-criteria.md): Buyer-side EU Accessibility Act procurement language for covered products and services, with supplier evidence, EN 301 549 limits, Article 14 exception records, and acceptance criteria.
- [EAA scope classifier workflow for products and services](/artifacts/eu/accessibility-act/accessibility-scope-classifier-workflow.md): Classify EU Accessibility Act scope by product or service category, consumer use, market or service date, operator role, exclusions, exemptions, Article 14 records, and evidence.
- [EAA testing and conformance evidence | Annex I, EN 301 549 and Article 14](/artifacts/eu/accessibility-act/testing-and-conformance-evidence.md): How to document European Accessibility Act testing evidence: Annex I mappings, product technical files, service information, EN 301 549 boundaries, harmonised-standard limits, and Article 14 exception records.
- [EAA WCAG evidence and procurement acceptance](/artifacts/eu/accessibility-act/wcag-evidence-and-procurement-acceptance.md): How to use EN 301 549 and WCAG evidence in EU Accessibility Act procurement acceptance without overstating presumption of conformity.
- [EN 301 549 clause mapping for the EU Accessibility Act | EAA FAQ](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md): How to map EN 301 549 and WCAG evidence to EU Accessibility Act Annex I requirements without overclaiming presumption of conformity.
- [EN 301 549 evidence matrix workflow for EAA readiness](/artifacts/eu/accessibility-act/en-301-549-evidence-matrix-workflow.md): Build an EN 301 549 evidence matrix for European Accessibility Act work: scope rows, clause mapping, test evidence, owner sign-off, exception records, and limits of standards evidence.
- [EN 301 549 vs WCAG for EAA evidence](/artifacts/eu/accessibility-act/en-301-549-vs-wcag.md): Compare EN 301 549 and WCAG for European Accessibility Act planning: ICT scope, web-content overlap, harmonised-standard limits, and evidence beyond WCAG-only tests.
- [EU Accessibility Act Applicability Test](/artifacts/eu/accessibility-act/applicability-test.md): Check whether the European Accessibility Act covers a product or consumer service, which role applies, which date matters, and what evidence to keep.
- [EU Accessibility Act authority request response FAQ](/artifacts/eu/accessibility-act/faq/authority-response.md): How to answer EU Accessibility Act checks from market surveillance or service authorities with technical documentation, service information, Article 14 records, and corrective actions.
- [EU Accessibility Act checklist for products and services](/artifacts/eu/accessibility-act/checklist.md): Checklist for EAA scope, operator role, Annex I mapping, product technical files, service information, Article 14 assessments, supplier evidence, release checks, and monitoring.
- [EU Accessibility Act compliance operating model](/artifacts/eu/accessibility-act/compliance.md): Build an EU Accessibility Act compliance file for covered products and services: scope, operator roles, Annex I mapping, conformity evidence, Article 14 assessments, corrective actions, and records.
- [EU Accessibility Act deadlines and compliance calendar](/artifacts/eu/accessibility-act/deadlines-and-compliance-calendar.md): Calendar for the EU Accessibility Act: 2022 transposition, 2025 application, 2027 emergency communications timing, 2030 transition rules, owner actions, and evidence records.
- [EU Accessibility Act deadlines and transition plan](/artifacts/eu/accessibility-act/deadlines-and-transition-plan.md): Plan for the European Accessibility Act application date, service-contract transition, self-service terminal transition, 112 derogation, and evidence gates.
- [EU Accessibility Act disproportionate burden decision](/artifacts/eu/accessibility-act/disproportionate-burden-decision.md): How to document an EU Accessibility Act Article 14 disproportionate burden decision with supported criteria, retained evidence, limits, notifications, and review triggers.
- [EU Accessibility Act exemptions and disproportionate burden](/artifacts/eu/accessibility-act/exemptions-and-disproportionate-burden.md): Article 14 EAA guide covering fundamental alteration, disproportionate burden, service microenterprise exemptions, content exclusions, transition limits, and documentation.
- [EU Accessibility Act FAQ: scope, dates, services, Article 14](/artifacts/eu/accessibility-act/faq.md): Clear answers on EU Accessibility Act scope, 28 June 2025 application, covered products and services, microenterprises, Article 14, service information, standards, and penalties.
- [EU Accessibility Act for ecommerce websites](/artifacts/eu/accessibility-act/accessibility-act-for-ecommerce-websites.md): Grounded guide for ecommerce teams applying the EU Accessibility Act to consumer checkout journeys, service information, accessibility evidence, and exceptions.
- [EU Accessibility Act microenterprise exemption and disproportionate burden FAQ](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md): FAQ explaining when EAA microenterprise relief applies, how Article 14 disproportionate-burden assessments work, what Annex VI requires, and what records to keep.
- [EU Accessibility Act penalties and enforcement](/artifacts/eu/accessibility-act/penalties-and-fines.md): How Directive (EU) 2019/882 handles penalties, Member State enforcement, market surveillance for products, and service compliance checks.
- [EU Accessibility Act procurement acceptance criteria | EAA FAQ](/artifacts/eu/accessibility-act/faq/procurement-acceptance.md): How to write EAA procurement acceptance criteria that ask suppliers for scoped accessibility evidence, standards mappings, declarations, and exception records without overclaiming conformity.
- [EU Accessibility Act Product and Service Scope](/artifacts/eu/accessibility-act/product-and-service-category-scoping.md): Scope products and services under the EU Accessibility Act using Article 2 categories, Article 3 definitions, limited content exclusions, microenterprise treatment, and evidence records.
- [EU Accessibility Act products and services in scope](/artifacts/eu/accessibility-act/products-and-services-in-scope.md): Article 2 scope guide for the European Accessibility Act: covered products, covered consumer services, economic-operator roles, Article 3 definitions, and evidence records.
- [EU Accessibility Act Requirements: Annex I, Products, Services](/artifacts/eu/accessibility-act/requirements.md): Map EU Accessibility Act requirements by Article 4, Annex I, product and service obligations, Article 13 evidence, standards, and Article 14 exceptions.
- [EU Accessibility Act service transition rules under Article 32 | EAA FAQ](/artifacts/eu/accessibility-act/faq/transition-services.md): FAQ on EU Accessibility Act Article 32 transition rules for service providers, pre-28 June 2025 contracts, 2030 limits, self-service terminals, evidence records, and change triggers.
- [EU Accessibility Act services: banking, transport, media and e-books](/artifacts/eu/accessibility-act/faq/banking-transport-and-media-services.md): FAQ on which consumer banking, transport, audiovisual media access, electronic communications, e-book, and e-commerce services fall under the EU Accessibility Act.
- [EU Accessibility Act vs ADA and Section 508: EAA-grounded comparison](/artifacts/eu/accessibility-act/accessibility-act-vs-ada-and-section-508.md): Compare the EU Accessibility Act with ADA and Section 508 planning boundaries, using grounded EAA scope, evidence, standards, procurement, and operator-duty points.
- [EU Accessibility Act vs Web Accessibility Directive](/artifacts/eu/accessibility-act/accessibility-act-vs-web-accessibility-directive.md): Compare the European Accessibility Act with the Web Accessibility Directive: scope, covered actors, services, standards, evidence, monitoring, enforcement, and key dates.
- [Which products and services does the EU Accessibility Act cover? | EAA FAQ](/artifacts/eu/accessibility-act/faq/product-and-service-categories.md): Article 2 and Article 3 scope summary for EU Accessibility Act covered products, services, exclusions, product-service boundaries, and records to keep.

*Recommended next step*

*Placement: after evidence section*

## Review your WCAG evidence before making EAA claims

Map test records to EN 301 549 and EAA Annex I before using them in product documentation, service accessibility information, procurement files, or authority responses.

- [Open Research Copilot](/solutions/research-copilot.md): Check EAA and EN 301 549 evidence questions with cited outputs.
- [Talk through implementation](/contact.md): Review WCAG reports, EN 301 549 mappings, evidence scope, and claim wording.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/accessibility-act/faq/wcag-evidence