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

EU Accessibility Act FAQ EN 301 549 clause mapping

EN 301 549 is an ICT accessibility standard that can help structure technical evidence for products and services covered by the European Accessibility Act.

Use it as a clause applicability and evidence map, then tie the result back to the EAA's Annex I requirements and Article 15 presumption limits.

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

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

Map evidence to the EU Accessibility Act by starting with the EAA obligation, not with a generic WCAG checklist. Identify the covered product or service, the relevant Annex I accessibility requirement, the ICT features in scope, the clauses whose preconditions are true, and the test evidence for those clauses. Use the exact edition: V3.2.1 is a published standard, while ETSI's June 2026 V4.1.0 document is a final draft and does not by itself establish EAA . Treat WCAG as part of the web, document, and software evidence boundary, not as a complete EAA answer by itself.

Search this module

Find a question or answer quickly

5 of 5 questions
Question 1

How should EN 301 549 and WCAG evidence be mapped for the EU Accessibility Act?

Use a two-layer map. The legal layer should identify the covered product or service, the economic operator role, the applicable EAA Annex I requirement, and any Article 14 fundamental-alteration or disproportionate-burden position. The technical layer should then show which clauses apply to the ICT features being assessed and what test or review evidence supports each result.

is self-scoping: many requirements begin with a precondition. If the precondition is true, assess the requirement and record the result; if it is false, record why the clause is not applicable. That is more useful than marking every clause pass or fail without explaining the product or service feature being assessed.

Keep WCAG in its correct boundary. reflects WCAG 2.1 content and uses WCAG-based requirements especially for web pages, non-web documents, and software, but an EAA record still needs the Annex I requirement, product or service facts, and any product/service documentation required by the Directive.

  • Start each row with the EAA Annex I outcome or information requirement, then add the clause or clause family used as ICT evidence.
  • Record clause applicability separately from pass/fail status so non-applicable clauses are traceable to a feature precondition, not silently dropped.
  • For web content, documents, and software, separate WCAG-derived findings from other evidence such as functional performance statements, hardware, closed functionality, two-way voice, video, documentation, support, and relay-service requirements where relevant.
  • Do not use V3.2.1 Annex A as an EAA Annex I crosswalk. Annex A identifies requirements relevant to the Web Accessibility Directive, whose OJEU reference has a different legal basis.
  • For products, connect the mapping to technical documentation, applied harmonised standards or technical specifications, and any EU declaration of conformity content.
  • For services, connect the mapping to the information explaining how the service meets the applicable accessibility requirements.

Does automatically prove EU Accessibility Act compliance?

No. Under Article 15 of the EAA, applies only to harmonised standards or parts of standards whose references have been published in the Official Journal of the European Union, and only so far as those standards or parts cover the relevant accessibility requirements. Use as structured ICT evidence, but do not claim a blanket EAA pass unless the OJEU citation and coverage support that specific requirement.

Is a WCAG 2.1 AA report enough for an EAA mapping?

A WCAG 2.1 AA report can support the clauses that reflect WCAG for web content and, through EN 301 549, related document or software checks. It is not enough by itself for the whole EAA because Annex I covers product and service accessibility requirements beyond a web page score, and EN 301 549 also includes non-WCAG areas such as functional performance, hardware, closed functionality, two-way voice, video, documentation, and support where those features exist.

Citations
Recommended next step

Turn the clause map into reviewable EAA evidence

Keep each EAA Annex I requirement, EN 301 549 clause, WCAG finding, exception, owner, and retest result in one evidence record so product, accessibility, legal, quality, and procurement teams can review the same facts.

Research workflow
Open Research Copilot

Answer EAA scope, standards, and evidence questions with cited outputs.

Explore next step
Talk to Sorena
Talk through implementation

Review your EAA scope, clause map, WCAG evidence, exceptions, and next actions.

Explore next step
Question 2

What should the clause mapping table contain?

A useful mapping table should let a reviewer see both the legal boundary and the technical evidence without reconstructing the project. It should not be a raw accessibility test export. It should explain why each clause was in scope, which EAA requirement it supports, what evidence was reviewed, and what remains unresolved.

Use separate columns for applicability, result, and presumption status. A passed test is evidence. A presumption claim needs the additional Article 15 condition that the relevant harmonised standard or part has an OJEU reference and covers the specific EAA requirement.

  • EAA reference: product or service category, Article 4/Annex I requirement, and any Article 14 exception relied on.
  • ICT boundary: user journey, component, platform, hardware, software, document, web page, support channel, or service information being assessed.
  • reference: clause number or clause family, precondition, applicability conclusion, test result, and link to the test procedure or evidence file.
  • WCAG reference: success criterion, test method, assistive-technology notes, defect ID, remediation status, and retest result where the EN clause uses WCAG evidence.
  • Conformity boundary: whether the row is evidence only, a partly applied standard, a harmonised-standard presumption claim, or a non-standard technical solution.
  • Owner and review trigger: accountable product, engineering, design, content, procurement, quality, or legal owner plus triggers such as design change, supplier change, standard update, release, complaint, or authority request.
Citations
Question 3

Where does WCAG fit inside EN 301 549?

WCAG evidence belongs inside the mapping where EN 301 549 incorporates or aligns with WCAG requirements. For web pages, EN 301 549 treats WCAG 2.1 Level AA conformance as equivalent to conforming with clauses 9.1 to 9.4 and the clause 9.6 conformance requirements. EN 301 549 also has separate requirements for non-web documents and non-web software.

That means a WCAG audit should be normalized into clauses instead of pasted into the EAA file as a standalone pass/fail list. The mapping should show which WCAG findings support which EN 301 549 rows, and which non-WCAG EN 301 549 clauses still need evidence.

  • Use clause 9 for web content evidence and keep page-level WCAG findings traceable to the assessed URLs or templates.
  • Use clause 10 for non-web document evidence where documents are part of the product or service information.
  • Use clause 11 for non-web software evidence, including native applications and embedded software where relevant.
  • Do not let a WCAG pass hide unresolved areas outside web content, documents, and software.
  • When AAA criteria are considered, label them as additional criteria unless the applicable requirement or procurement specification actually requires them.
Citations
Question 4

How should presumption of conformity be stated?

State presumption narrowly. The EAA says products and services conforming with harmonised standards or parts of standards whose references are published in the Official Journal are presumed to conform only so far as those standards or parts cover the Directive's accessibility requirements. Technical specifications or parts established by a Commission implementing act under Article 15 carry the same presumption only for the requirements they cover.

Avoid broad wording such as ' compliant equals EAA compliant'. EN 301 549 V3.2.1 is referenced for the Web Accessibility Directive. ETSI published the final draft of EN 301 549 V4.1.0 in June 2026 with EAA relationship tables, but a final draft is not an OJEU citation. Record which standard version or part was applied, whether it has the required EAA legal status for the requirement at issue, which EAA requirement it covers, and what evidence demonstrates implementation.

  • Use 'evidence mapped to ' when the standard supports the technical assessment but the OJEU presumption claim has not been verified for the relevant EAA requirement.
  • Use ' claimed for this requirement' only when the cited harmonised standard or part is published for that legal effect and covers the specific Annex I requirement.
  • If a harmonised standard is applied only in part, identify the applied parts and describe other solutions used for the remaining accessibility requirements.
  • If Article 14 is used, identify the affected accessibility requirements and keep the fundamental-alteration or disproportionate-burden assessment with the mapping.
  • For service files, keep the explanation of how the service meets applicable accessibility requirements in the terms and conditions or equivalent document.
Citations
Question 5

Common mapping mistakes to avoid

Do not treat accessibility evidence as interchangeable across laws, standards, products, and versions. The EAA file should show the exact product or service, the exact Annex I requirement, the exact ICT feature, and the exact clause or WCAG criterion being relied on.

Keep exceptions and unresolved scope questions visible. If a clause is not applicable, record the precondition that makes it not applicable. If an accessibility requirement is not fully met because of Article 14, keep that assessment separate from the test result.

  • Do not cite WCAG alone as proof that a payment terminal, e-reader, transport information service, banking service, or e-commerce service meets every applicable EAA requirement.
  • Do not mark a clause 'not applicable' without naming the feature precondition and the product or service evidence behind that conclusion.
  • Do not claim for an entire product or service when only selected clauses or parts of a standard were applied.
  • Do not mix Web Accessibility Directive evidence, EAA evidence, and procurement evidence unless each row says which legal requirement it supports.
  • Do not leave supplier VPATs, accessibility conformance reports, design tickets, and manual test results disconnected from the EAA Annex I requirement they are meant to support.
Citations
Primary sources

References and citations

Directive (EU) 2019/882 (European Accessibility Act)
eur-lex.europa.eu
Referenced sections
  • Supports keeping EAA Annex I requirements, Article 14 exceptions, conformity documentation, and service information distinct in the evidence record.
"shall state which accessibility requirements are subject to that exception"
ETSI - EN 301 549 V3 standard overview
etsi.org
Referenced sections
  • Supports checking EN 301 549 clause applicability by ICT feature and precondition rather than assuming all clauses apply.
"If the precondition is met"
ETSI - Final draft EN 301 549 V4.1.0 (2026-06)
etsi.org
Referenced sections
  • Official ETSI final draft showing the June 2026 V4.1.0 revision and EAA relationship tables; final-draft status does not itself create Article 15 presumption.
European Commission - Harmonised standards
single-market-economy.ec.europa.eu
Referenced sections
  • Supports avoiding overclaiming because harmonised standards can be used to demonstrate compliance but remain voluntary.
"free to choose another technical solution"
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 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.
WCAG Evidence for the EU Accessibility Act and EN 301 549 | EAA FAQ
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.
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.