WorkflowEU

European Accessibility Act EN 301 549 evidence matrix workflow

Use EN 301 549 evidence carefully: the standard is an ICT accessibility reference, while Directive (EU) 2019/882 sets the legal accessibility requirements for covered EAA products and services.

This workflow shows how to map EAA scope, EN 301 549 clauses, test evidence, owners, exceptions, and authority-ready records without treating one standard citation as a complete compliance file.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
4

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

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

An EN 301 549 evidence matrix should connect product or service facts to the EAA requirement being assessed, the applicable ICT accessibility clause, the test or inspection evidence, the accountable owner, and any unresolved limitation. It is strongest when it shows both what was tested and why a requirement was not applicable.

Section 1

Start with the EAA scope row, not the test result

Create one matrix row for each covered product, service, feature, or supplier component. The first row should answer whether the item is one of the EAA product or service categories, which economic operator or service provider owns it, and which accessibility requirement or service information duty is being evidenced.

Do not start by pasting WCAG or EN 301 549 results into a spreadsheet. A test result is useful only after the record explains whether the EAA applies, which user-facing function is in scope, and whether the evidence is for a product conformity file, a service conformity explanation, procurement assurance, or remediation.

  • Scope field: product, service, software, hardware, document, support channel, self-service terminal, or supplier-controlled component.
  • EAA field: covered category, applicable Annex I accessibility requirement, product role or service-provider responsibility, and any Member State implementation assumption that needs legal review.
  • Owner field: product owner for scope, engineering or accessibility lead for tests, procurement owner for supplier evidence, legal or regulatory owner for Article 14 exceptions, and release owner for final sign-off.
  • Status field: in scope, out of scope, partially applicable, not applicable because the EN 301 549 precondition is false, or escalated because the source does not answer the fact pattern.
Section 2

Map EN 301 549 clauses as applicability evidence

For ICT products and services, use EN 301 549 as a clause-by-clause evidence structure. Each row should record the clause, the precondition, the user-facing function, the applicable requirement, and the result. The standard is self-scoping, so a row that is not applicable should explain the failed precondition instead of being deleted.

A practical matrix separates functional performance from technical tests. Clause 4 describes user needs; clauses 5 to 13 contain specific technical criteria; Annex B helps connect requirements to functional performance statements; Annex C gives the means to determine conformance for individual requirements but does not supersede a complete testing methodology.

  • Web content: map relevant clause 9 rows and the underlying WCAG 2.1 result, including pass, fail, not applicable, tested URL or state, tester, tool, assistive technology where used, and defect link.
  • Non-web documents: map clause 10 rows for PDFs, office files, e-book content, downloadable statements, and customer documents that are part of the service journey.
  • Software and apps: map clause 11 rows for mobile apps, desktop software, embedded software, and non-web interaction states that support the covered product or service.
  • Hardware, voice, video, documentation, and support: add rows from clauses 5 to 8, 12, and 13 when the product or service has closed functionality, hardware controls, two-way voice, video, support documentation, or support services.
Recommended next step

Turn clause evidence into a defensible EAA record

Use this workflow to align product, service, engineering, procurement, legal, and release teams around the same EAA scope rows, EN 301 549 clause evidence, exception records, and authority-response package.

Section 3

Record evidence, owners, and release decisions in the matrix

Treat the matrix as a release and audit record, not a checklist of accessibility slogans. Every applicable row should identify the evidence file, the tester or reviewer, the finding, the defect or remediation record, and the owner who accepted the result.

For products, link the matrix to the technical documentation and EU declaration workstream where relevant. For services, link it to the public or customer-facing information that explains how the service meets the applicable accessibility requirements, and keep the record current when the service, requirement, harmonised standard, or technical specification changes.

  • Evidence fields: source requirement, EN 301 549 clause, test date, environment, sample, tool or manual method, result, defect ID, remediation evidence, retest result, and retained file location.
  • Decision fields: release allowed, release blocked, accepted with documented remediation plan, exception under Article 14 escalated, supplier evidence missing, or authority response required.
  • Supplier fields: product or service component, supplier assertion, test report, accessibility conformance statement, contractual accessibility requirement, evidence date, and decision owner.
  • Change triggers: new release, major user-flow change, supplier substitution, new or changed standard reference, complaint, incident, non-conformity, authority request, or Article 14 reliance.
Section 4

Show the limits of standards evidence before relying on it

The matrix should make standards reliance explicit. Under the EAA, conformity with harmonised standards or parts of standards creates a presumption of conformity only to the extent the cited standards cover the relevant accessibility requirements and their references have been published in the Official Journal of the European Union.

Do not write 'EN 301 549 compliant' as the only conclusion. Record which version, clause, precondition, test result, and EAA requirement are being relied on. Also record what the standard evidence does not cover, such as legal scope, market role, service information duties, national implementation assumptions, or an Article 14 fundamental alteration or disproportionate burden assessment.

  • Presumption field: standard or technical specification, version, OJEU reference check, clauses applied in full or in part, and EAA requirement covered.
  • Limit field: rows not covered by the standard, failed tests, untested states, supplier assertions without evidence, national-law questions, and any reliance on Article 14.
  • Article 14 field: requirement affected, reason asserted, Annex VI criteria considered, evidence retained, authority-notification status where reliance is used, and renewal trigger for service-provider assessments.
  • Authority-ready field: product identification, service description, non-conformity and corrective action record, matrix export, test evidence, technical documentation or service information, and responsible contact.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Supports the limits of standards evidence, Article 14 documentation, presumption of conformity, technical documentation, EU declaration content, and market-surveillance records.
"in so far as those standards"
etsi.org
Referenced sections
  • Supports the caution that EN 301 549 V3.2.1 currently supports the Web Accessibility Directive and is planned to be updated to support Directive (EU) 2019/882.
"planned to be updated"
commission.europa.eu
Referenced sections
  • Supports the page's scope framing: the EAA covers identified products and services such as computers, ATMs, smartphones, electronic communications, banking, e-books, transport-related services, and e-commerce.
"products and services covered"
single-market-economy.ec.europa.eu
Referenced sections
  • Commission source for the harmonised-standards context used when a matrix relies on a standard as evidence rather than as a standalone legal conclusion.
"Harmonised standards"
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 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
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
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
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 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
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
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: EAA-grounded comparison
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
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.