--- title: "EN 301 549 vs WCAG for EAA evidence" canonical_url: "https://www.sorena.io/artifacts/eu/accessibility-act/en-301-549-vs-wcag" source_url: "https://www.sorena.io/artifacts/eu/accessibility-act/en-301-549-vs-wcag" author: "Sorena AI" description: "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." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "EU Accessibility Act" - "EAA" - "Directive (EU) 2019/882" - "EN 301 549" - "WCAG" - "accessibility evidence" --- **[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) --- # 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. *EN 301 549 vs WCAG* *EU Accessibility Act* ## EN 301 549 vs WCAG EAA evidence boundary EN 301 549 is a European ICT accessibility standard for products and services based on information and communication technologies; WCAG is a web content accessibility standard that EN 301 549 reflects for web, document, and software requirements. Use this comparison to avoid treating a WCAG-only website audit as a complete European Accessibility Act evidence file for ICT products, services, documentation, support, or non-web software. EN 301 549 and WCAG overlap, but they are not interchangeable. EN 301 549 V3.2.1 is structured around ICT products and services, including functional performance statements, hardware, web content, non-web documents, software, documentation, support services, and relay or emergency-service access. WCAG supplies web-content success criteria that EN 301 549 incorporates or adapts in specific clauses, so a WCAG test can be strong evidence for web content while still leaving EAA and ICT-standard questions unanswered. ## EN 301 549 vs WCAG for EU Accessibility Act evidence A point-by-point comparison for teams deciding when WCAG evidence is enough for a web surface and when EN 301 549 or EAA records need more. - **EN 301 549**: A European ICT accessibility standard for products and services, structured around functional performance statements and technical requirements for ICT features. - **WCAG**: A web content accessibility standard reflected by EN 301 549 in web, non-web document, and software clauses, but not a full substitute for every EN 301 549 or EAA evidence need. | Dimension | EN 301 549 | WCAG | Operational implication | Sources | | --- | --- | --- | --- | --- | | Scope boundary | EN 301 549 V3.2.1 specifies functional accessibility requirements for ICT products and services and includes conformance checks for applicable requirements. | WCAG provides accessibility success criteria for web content; EN 301 549 reflects WCAG 2.1 content in clauses 9, 10, and 11. | Use EN 301 549 as the ICT evidence framework and WCAG as a web-content evidence source inside that framework where the EN clause points to it. | [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the ICT standard scope and the WCAG relationship described on the ETSI EN 301 549 page. | | Covered actors | EN 301 549 covers web-based technologies, non-web technologies, hybrids, software, hardware, services, documentation, and support services where the relevant preconditions are met. | WCAG testing is strongest for web content and WCAG-derived checks, but it does not by itself test hardware interaction, closed functionality, support-service communication, or every software accessibility-service requirement. | Start the evidence plan by listing every ICT surface, then mark which surfaces are WCAG-testable and which require EN 301 549-specific assessment. | [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the ICT categories and EN 301 549 structure that extend beyond web-content testing. | | Trigger | Under the EAA, products and services conforming with harmonised standards or parts of harmonised standards cited in the Official Journal are presumed conforming only so far as those standards or parts cover the accessibility requirements. | WCAG can support the accessible web or mobile part of an EAA file, especially because the EAA uses perceivable, operable, understandable, and robust principles for websites and mobile services, but WCAG is not the EAA itself. | Check the EAA legal requirement, the harmonised-standard citation, and the standard clauses before claiming presumption of conformity. | [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the Article 15 presumption-of-conformity boundary and the EAA web/mobile accessibility principles.
[European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports the need to check harmonised standards and Official Journal publication context. | | Core obligations | EN 301 549 uses self-scoping requirements: when a precondition is true, the corresponding requirement and Annex C conformance check matter. | WCAG test results normally show pass, fail, not tested, or not applicable for selected success criteria on selected web content or software/content samples. | Attach WCAG results to the matching EN 301 549 clause, then separately record EN 301 549 applicability and any non-WCAG checks. | [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the self-scoping and conformance-check boundary for EN 301 549 evidence. | | Evidence record | EN 301 549 evidence should include clause applicability, test procedures or evaluation notes, functional-performance links, non-applicable reasoning, defects, fixes, and retest status. | WCAG evidence should include tested pages or components, WCAG version and level used by the project, manual and automated findings, assistive-technology notes, and defect closure. | Keep a shared evidence index, but tag each artifact as WCAG evidence, EN 301 549 evidence, EAA product documentation, EAA service information, or Article 14 assessment support. | [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports clause-based conformance and the wider ICT evidence set.
[Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports EAA product documentation, service information, and Article 14 assessment records. | | Timing and deadlines | EN 301 549 non-applicability can follow from a failed precondition, but that is different from an EAA fundamental-alteration or disproportionate-burden assessment. | WCAG not-applicable results only show that a success criterion was not relevant to the tested content; they do not resolve EAA Article 14 or EN 301 549 clauses outside the tested surface. | Do not use WCAG not-applicable rows as a legal exception record. Keep EN 301 549 applicability, WCAG test scope, and EAA Article 14 assessments separate. | [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the EN 301 549 self-scoping concept and non-applicability boundary.
[Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the Article 14 distinction between technical non-applicability and EAA fundamental-alteration or disproportionate-burden assessment. | | Enforcement | An EN 301 549 claim should identify the version, applicable clauses, assessed ICT boundary, exclusions, and whether the claim is for procurement, product documentation, service information, or conformity support. | A WCAG claim should identify the WCAG version, conformance level, tested scope, date, and known exclusions or open defects. | Use cautious wording: WCAG conformance for a web surface is not the same as full EN 301 549 conformity or EAA compliance for the whole product or service. | [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports versioned EN 301 549 scope and clause-based evidence.
[Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the need for product and service records that show how applicable accessibility requirements are met. | | Overlap and reuse | Use EN 301 549 when the work concerns ICT procurement, product or service accessibility evidence, non-web software, hardware, documentation, support, or a standard-based EAA conformity argument. | Use WCAG when the work concerns web content, page templates, web components, accessible documents or software content where EN 301 549 points to WCAG-derived requirements. | Most EAA teams need both: WCAG for detailed content testing and EN 301 549 for the wider ICT and evidence boundary. | [ETSI - EN 301 549 V3 ICT accessibility standard](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 across ICT product and service categories while recognising its WCAG-derived web, document, and software clauses.
[European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Supports the broader standards role for ICT accessibility, EAA, the Web Accessibility Directive, and procurement. | | Practical decision rule | EN 301 549 V3.2.1 specifies functional accessibility requirements for ICT products and services and includes conformance checks for applicable requirements. | WCAG provides accessibility success criteria for web content; EN 301 549 reflects WCAG 2.1 content in clauses 9, 10, and 11. | Use EN 301 549 as the ICT evidence framework and WCAG as a web-content evidence source inside that framework where the EN clause points to it. | [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the ICT standard scope and the WCAG relationship described on the ETSI EN 301 549 page. | Sources for Scope boundary: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the ICT standard scope and the WCAG relationship described on the ETSI EN 301 549 page. - Quote: "ICT products and services" Sources for Covered actors: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the ICT categories and EN 301 549 structure that extend beyond web-content testing. - Quote: "any type of ICT-based products and services" Sources for Trigger: - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the Article 15 presumption-of-conformity boundary and the EAA web/mobile accessibility principles. - Quote: "in so far as those standards" - [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports the need to check harmonised standards and Official Journal publication context. - Quote: "Harmonised Standards" Sources for Core obligations: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the self-scoping and conformance-check boundary for EN 301 549 evidence. - Quote: "Conformance is achieved" Sources for Evidence record: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports clause-based conformance and the wider ICT evidence set. - Quote: "test procedures" - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports EAA product documentation, service information, and Article 14 assessment records. - Quote: "assessment of whether compliance" Sources for Timing and deadlines: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the EN 301 549 self-scoping concept and non-applicability boundary. - Quote: "pre-condition is false" - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the Article 14 distinction between technical non-applicability and EAA fundamental-alteration or disproportionate-burden assessment. - Quote: "fundamental alteration" Sources for Enforcement: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports versioned EN 301 549 scope and clause-based evidence. - Quote: "V3.2.1" - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the need for product and service records that show how applicable accessibility requirements are met. - Quote: "how the relevant accessibility requirements" Sources for Overlap and reuse: - [ETSI - EN 301 549 V3 ICT accessibility standard](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 across ICT product and service categories while recognising its WCAG-derived web, document, and software clauses. - Quote: "web pages, mobile applications" - [European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Supports the broader standards role for ICT accessibility, EAA, the Web Accessibility Directive, and procurement. - Quote: "support accessibility" Sources for Practical decision rule: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the ICT standard scope and the WCAG relationship described on the ETSI EN 301 549 page. - Quote: "ICT products and services" ### How should teams decide what evidence is enough? - If the question is limited to a website or web component, run WCAG testing and map the result to the relevant EN 301 549 web-content clause where EN 301 549 is part of the assurance claim. - If the question involves a covered EAA product or service, add the EAA scope analysis, Annex I requirement mapping, harmonised-standard citation check, and product or service documentation evidence. - If the system includes non-web software, hardware, documents, support services, or closed functionality, add EN 301 549-specific applicability and conformance checks before making an ICT accessibility claim. - If an exception is being considered, keep WCAG non-applicability, EN 301 549 precondition results, and EAA Article 14 assessments in separate records. Sources for the practical decision rule: - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports separating EAA scope, Annex I requirements, harmonised-standard presumption, and Article 14 assessments. - Quote: "applicable accessibility requirements" - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the EN 301 549 ICT scope, self-scoping structure, and relationship to WCAG-derived clauses. - Quote: "requirements are self-scoping" - [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports checking whether a harmonised standard is the correct basis for presumption-of-conformity claims. - Quote: "Harmonised Standards" ## Where EN 301 549 and WCAG actually meet The clean boundary is this: WCAG is a content accessibility standard; EN 301 549 is an ICT accessibility standard. EN 301 549 V3.2.1 states that it reflects WCAG 2.1 content and uses WCAG-linked requirements in clauses 9, 10, and 11 for web, non-web documents, and software. It also contains requirements outside those WCAG-derived areas. For an EAA program, this means a WCAG audit can support the web or app part of the file, but it should be tied to the EN 301 549 clause, product boundary, and accessibility requirement it supports. Do not label WCAG results as EN 301 549 conformance unless the EN 301 549 self-scoping conditions, applicable clauses, and conformance checks have also been addressed. - Use WCAG results for web content and for EN 301 549 clauses that explicitly reflect WCAG success criteria. - Use EN 301 549 mapping for ICT boundaries beyond a website: hardware, closed functionality, software interfaces, documents, documentation, support services, relay services, and emergency-service access. - Keep EAA legal scope separate from standard conformance: Directive (EU) 2019/882 sets accessibility requirements for covered products and services, while harmonised standards can create presumption of conformity only for the requirements they cover. Sources for this answer: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the boundary that EN 301 549 is an ICT accessibility standard and that its current version supports the Web Accessibility Directive while an EAA-supporting revision is planned. - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the EAA scope, Annex I accessibility requirements, Article 14 exception framework, and Article 15 presumption-of-conformity rule. - [European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Supports the role of European accessibility standards, including EN 301 549 for ICT accessibility. *Recommended next step* *Placement: after evidence section* ## Build an EAA evidence file that does not overclaim WCAG coverage Use the comparison to label what WCAG proves, what EN 301 549 still requires, and which EAA product or service records need separate support. - [Open Research Copilot](/solutions/research-copilot.md): Compare accessibility sources and produce cited evidence notes. - [Talk through implementation](/contact.md): Review your EAA scope, EN 301 549 mapping, WCAG evidence, and claim wording. ## Why WCAG-only tests may be insufficient for EAA evidence A WCAG report usually answers whether sampled web pages, web components, or digital content meet selected WCAG success criteria. EAA evidence often has to answer a wider set of questions: whether the product or service is in scope, which Annex I requirements apply, whether harmonised standards or technical specifications were applied in full or in part, and whether product or service procedures keep accessibility conformity current. EN 301 549 also requires scoping discipline. Its requirements are self-scoping, so the precondition for each requirement matters. A payment terminal, ticketing kiosk, e-reader ecosystem, banking service, mobile app, help desk, or downloadable document can require evidence that a web-page-only WCAG audit will not cover. - Add an EN 301 549 clause matrix showing applicable, not applicable, pass, fail, and remediation status. - Keep WCAG test evidence, but label the tested pages, components, assistive-technology checks, browser/device combinations, defects, and closure evidence. - Add non-WCAG evidence where relevant: hardware interaction checks, closed-functionality review, software accessibility-service support, accessible product documentation, support-service communication, and service conformity procedures. - For products, keep technical documentation and any EU declaration of conformity evidence required by the EAA; for services, keep the general terms or equivalent accessibility information described for service providers. Sources for this answer: - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the EN 301 549 structure covering functional performance, ICT requirements, self-scoping requirements, and the relationship to WCAG-derived clauses. - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the need for product technical documentation, service accessibility information, conformity evidence, and Article 14 assessments where used. - [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports the standards and Official Journal context for presumption-of-conformity checks. ## Evidence pack fields for the comparison A useful comparison file should not ask whether the organisation is doing EN 301 549 or WCAG in the abstract. It should state what system is being assessed, which legal and standard boundaries apply, and what each evidence item proves. The most important review question is whether the evidence is overclaiming. A WCAG pass can support EN 301 549 web-content requirements, but it does not by itself prove conformity for hardware, software interoperability, documentation, support services, EAA product obligations, or an Article 14 fundamental-alteration or disproportionate-burden position. - Product or service boundary: covered EAA product or service, ICT components, web surfaces, non-web documents, native software, hardware, support services, and third-party dependencies. - Standard mapping: EN 301 549 clause, WCAG criterion where relevant, applicability precondition, test method, result, defect link, remediation owner, and retest date. - EAA link: Annex I requirement, harmonised standard or technical specification applied in full or in part, technical documentation or service information location, and any Article 14 assessment. - Claim control: approved wording for procurement, customer assurance, accessibility statements, declarations, and release notes so public claims do not exceed the tested scope. 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 EAA requirements for covered products and services, conformity evidence, and exception records. - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the clause-based EN 301 549 evidence structure and the ICT categories that go beyond WCAG-only web tests. - [European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Supports using European accessibility standards as implementation support for ICT and EAA-related accessibility work. ## Primary sources - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports separating EAA scope, Annex I requirements, harmonised-standard presumption, and Article 14 assessments. - Quote: "applicable accessibility requirements" - [ETSI - EN 301 549 V3 ICT accessibility standard](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the EN 301 549 ICT scope, self-scoping structure, and relationship to WCAG-derived clauses. - Quote: "requirements are self-scoping" - [European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Supports the broader standards role for ICT accessibility, EAA, the Web Accessibility Directive, and procurement. - Quote: "support accessibility" - [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports checking whether a harmonised standard is the correct basis for presumption-of-conformity claims. - Quote: "Harmonised Standards" ## Related 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. - [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. - [WCAG Evidence for the EU Accessibility Act and EN 301 549 | EAA FAQ](/artifacts/eu/accessibility-act/faq/wcag-evidence.md): 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](/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. --- [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/en-301-549-vs-wcag