We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQEU 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.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Questions
4

Structured answer sets in this page tree.

Primary sources
6

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

evidence is useful for EU Accessibility Act work when it is scoped, versioned, and mapped through . It can show that specific web content, non-web documents, or software screens satisfy WCAG-derived 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.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

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 where products or services conform with harmonised standards or parts whose references have been published in the Official Journal of the European Union, or with technical specifications or parts established by a Commission implementing act under Article 15, and only so far as those standards, technical specifications, or parts cover the relevant EAA requirements.

is a practical ICT evidence 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. EN 301 549 V3.2.1 is harmonised for the Web Accessibility Directive. ETSI published the final draft of V4.1.0 in June 2026 with EAA relationship tables, but a final draft is not an OJEU citation, so do not transfer either the Web Accessibility Directive reference or final-draft status into an EAA presumption claim.

V3.2.1 reflects 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. Write a WCAG report as evidence for those EN 301 549 requirements, not as a standalone EAA conclusion.

  • Use evidence for web pages, documents, and software user interfaces where the relevant clause points to WCAG-derived criteria.
  • Keep a separate EAA mapping from the covered product or service to Annex I and to any clauses relied on.
  • Before using presumption-of-conformity language, check whether the harmonised standard or part has an OJEU reference, or whether the technical specification or part was established by a Commission implementing act under Article 15, and confirm that it covers the relevant EAA requirement.
  • Record the law supported by each standards reference. A V3.2.1 Annex A result may support a Web Accessibility Directive conclusion, but it is not an EAA Annex I crosswalk.
  • Avoid saying that 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.

Is evidence useful for EU Accessibility Act and work?

Yes, but only for the parts it actually tests. evidence is useful when it is mapped to requirements for web content, non-web documents, or software interfaces and then connected to the relevant EAA Annex I requirement. It should not be used as a broad EAA compliance claim for the whole product, service, organisation, or market placement.

Can a audit prove EAA compliance?

No. A audit can support specific accessibility requirements, especially where uses WCAG-derived criteria, but EAA compliance also depends on product or service scope, Annex I coverage, technical documentation or service information, conformity assessment language, operator responsibilities, complaints or authority requests, and any Article 14 fundamental-alteration or disproportionate-burden assessment.

Citations
Recommended next step

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.

Research workflow
Open Research Copilot

Check EAA and EN 301 549 evidence questions with cited outputs.

Explore next step
Talk to Sorena
Talk through implementation

Review WCAG reports, EN 301 549 mappings, evidence scope, and claim wording.

Explore next step
Question 2

What the evidence record should contain

A useful 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 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. 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: version, 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.
Citations
Question 3

What WCAG cannot prove by itself

is not the same thing as , 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 test into unsupported claims such as 'EAA compliant', ' 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.

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

Review checklist for WCAG evidence

Review this checklist before relying on a report in an EAA evidence pack. State what the test proves, what it does not prove, and what additional EAA or evidence is still needed.

  • State the claim in narrow language: for example, 'tested checkout pages against listed 2.1 success criteria mapped to clause 9', not 'EAA compliant'.
  • Map each finding to the 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.
Citations
Primary sources

References and citations

Directive (EU) 2019/882 (European Accessibility Act)
eur-lex.europa.eu
Referenced sections
  • Supports the need to keep EAA records tied to applicable accessibility requirements, technical documentation, service information, and exceptions.
"explain how the services meet the applicable accessibility requirements"
European Commission - Harmonised standards
single-market-economy.ec.europa.eu
Referenced sections
  • Supports escalation before using presumption-of-conformity language because harmonised-standard references must be published in the OJEU for that legal effect.
"published in the Official Journal"
Related guides

Explore more topics

EAA Accessibility Conformance Statement Template
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
A cited 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
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
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
EU Accessibility Act guide for e-commerce checkout scope, payment and identification requirements, evidence, standards mapping, and customer information.
EAA EN 301 549 and WCAG mapping
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
EU Accessibility Act guide for ecommerce teams covering consumer checkout journeys, service information, accessibility evidence, and exceptions.
EU Accessibility Act microenterprise exemption and disproportionate burden FAQ
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
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
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
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
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
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
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
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
Compare EAA product and consumer-service duties with ADA Title II and III accessibility duties and US federal Section 508 ICT requirements.
EU Accessibility Act vs Web Accessibility Directive
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
Article 2 and Article 3 scope summary for EU Accessibility Act covered products, services, exclusions, product-service boundaries, and records to keep.