--- title: "EU Accessibility Act FAQ: scope, dates, services, Article 14" canonical_url: "https://www.sorena.io/artifacts/eu/accessibility-act/faq" source_url: "https://www.sorena.io/artifacts/eu/accessibility-act/faq/items" author: "Sorena AI" description: "Clear answers on EU Accessibility Act scope, 28 June 2025 application, covered products and services, microenterprises, Article 14, service information, standards, and penalties." published_at: "2026-05-09" updated_at: "2026-05-17" keywords: - "EU Accessibility Act" - "EAA" - "Directive (EU) 2019/882" - "Article 14" - "microenterprises" - "EN 301 549" - "accessible services" - "accessibility compliance" --- **[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) --- # 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. *FAQ* *EU* ## EU Accessibility Act FAQ Answers to practical EAA questions about scope, dates, covered products and services, accessibility requirements, microenterprise treatment, Article 14, standards, and enforcement. Use this page to check what the Directive actually says before turning an accessibility question into product, service, legal, procurement, or support work. The European Accessibility Act is Directive (EU) 2019/882 on accessibility requirements for certain products and services. These FAQ answers focus on the legal scope and operating questions most likely to affect consumer-facing digital products, self-service terminals, e-commerce, banking, transport information, electronic communications, audiovisual access services, and e-books. ## Browse sub-FAQ modules ### [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. - 4 items ### [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. - 4 items ### [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. - 5 items ### [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. - 4 items ### [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. - 4 items ### [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. - 4 items ### [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. - 4 items ### [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. - 4 items ### [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. - 4 items ### [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. - 4 items Browse all indexed questions: [/artifacts/eu/accessibility-act/faq/items](/artifacts/eu/accessibility-act/faq/items.md) ## All FAQ items *Page 1 of 3. Showing 20 of 41 items.* ### [What should an EU Accessibility Act conformance statement include?](/artifacts/eu/accessibility-act/faq/conformance-statements.md#what-should-an-eu-accessibility-act-conformance-statement-include) *Module: [EAA conformance statements: products, services, EN 301 549 evidence](/artifacts/eu/accessibility-act/faq/conformance-statements.md)* Start with the legal posture of the thing being documented. A product statement should not replace the EU declaration of conformity: manufacturers must draw up technical documentation, carry out the Annex IV conformity assessment procedure, draw up an EU declaration of conformity when compliance is demonstrated, and keep the technical documentation and declaration for five years after placing the product on the market. - Identify the covered product or service, economic-operator role, market, version, release date, and owner of the statement. - Map the statement to applicable EAA requirements, especially Annex I outcomes for information, instructions, user interface, functionality, service information, websites, mobile apps, identification, security, payment, and support where relevant. - For products, reference the technical documentation, applied harmonised standards or technical specifications, conformity assessment result, EU declaration of conformity status, CE marking basis, and any Article 14 exception. - For services, explain the accessible public information required by Annex V, the service channels covered, the operating procedures that keep the service conformant, and the trigger for updating the information. - Separate verified compliance, partial conformance, known nonconformance, planned remediation, and fundamental-alteration or disproportionate-burden positions. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019L0882&ref=sorena.io) - Primary EAA source for product technical documentation, EU declarations, service information, Article 14 exceptions, and Annex IV/V records. - [European Commission - European Accessibility Act policy page](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en?ref=sorena.io) - Commission policy context for the EAA as accessibility requirements for selected products and services. ### [How should EN 301 549 and WCAG be used without overclaiming?](/artifacts/eu/accessibility-act/faq/conformance-statements.md#how-should-en-301-549-and-wcag-be-used-without-overclaiming) *Module: [EAA conformance statements: products, services, EN 301 549 evidence](/artifacts/eu/accessibility-act/faq/conformance-statements.md)* Use EN 301 549 and WCAG as scoped evidence, not as a blanket EAA certificate. The EAA creates a presumption of conformity only for products and services that conform 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 cover the relevant EAA requirements. - Do not write 'EAA compliant because WCAG passed' unless the assessed scope is only the requirements WCAG actually covers and the remaining EAA requirements are separately addressed. - Do not imply EN 301 549 automatically creates EAA presumption of conformity unless the relevant standard reference or part has the required OJEU status for the requirement being claimed. - For ICT, keep a requirement matrix that links Annex I requirements to EN 301 549 clauses, WCAG checks where relevant, manual test results, assistive-technology checks, and remediation evidence. - For product documentation and ICT support services in electronic format, check the EN 301 549 clauses for web or non-web documents as appropriate instead of relying only on the main product interface test. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019L0882&ref=sorena.io) - Article 15 source for presumption of conformity from OJEU-published harmonised standards or parts that cover the relevant requirements. - [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Commission source explaining that harmonised standards are used to demonstrate compliance and require OJEU publication for legal effect. - [ETSI - EN 301 549 V3 overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - ETSI source for EN 301 549 scope, its current Web Accessibility Directive support, and planned EAA-oriented revision. ### [What evidence should support the statement?](/artifacts/eu/accessibility-act/faq/conformance-statements.md#what-evidence-should-support-the-statement) *Module: [EAA conformance statements: products, services, EN 301 549 evidence](/artifacts/eu/accessibility-act/faq/conformance-statements.md)* The evidence pack should let a market-surveillance authority, service compliance reviewer, customer, procurement team, or support lead understand what was assessed and why the claim is limited the way it is. Keep public wording, technical files and service operating records aligned so the statement does not promise more than the underlying evidence shows. - Product evidence: product description, design and operation records, applied standards or technical specifications, parts applied, alternative solutions where standards were not applied, test reports, conformity assessment record, EU declaration of conformity, CE marking decision, and change-control history. - Service evidence: service description, covered channels, public accessibility information, Annex I requirement mapping, procedures that keep the service conformant, web/mobile/document/software tests, support-process evidence, supplier inputs, complaint handling, and update history. - Exception evidence: Article 14 assessment, affected requirements, reasoned analysis against the relevant criteria, evidence of partial accessibility where full application is not claimed, authority notification or response record where relevant, and review date. - Standards evidence: EN 301 549 version and clause mapping, WCAG success-criteria results where relevant, non-web document/software checks, hardware or closed-functionality checks, assistive-technology notes, and unresolved failures. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019L0882&ref=sorena.io) - Primary source for Annex IV technical documentation, Annex V service information, and Article 14 exception documentation. - [ETSI - EN 301 549 V3 overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Standards source for the distinction between ICT requirements, functional performance statements, web, documents, software, hardware, and support-service evidence. - [Commission Notice - Blue Guide on EU product rules (2022)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A52022XC0629%2804%29&ref=sorena.io) - General EU product-rules guidance for manufacturer responsibility, CE marking, EU declaration and technical documentation concepts. ### [Common drafting mistakes](/artifacts/eu/accessibility-act/faq/conformance-statements.md#common-drafting-mistakes) *Module: [EAA conformance statements: products, services, EN 301 549 evidence](/artifacts/eu/accessibility-act/faq/conformance-statements.md)* Most poor EAA conformance statements fail because they are too broad. They describe an accessibility ambition instead of a tested product or service boundary, or they reuse a WCAG accessibility-statement template for EAA product and service obligations that need different records. - Do not call a service statement an EU declaration of conformity; reserve that term for the product declaration where the EAA requires it. - Do not claim that a supplier VPAT, accessibility statement, certificate or test report covers the EAA unless it matches the exact version, component, service journey, requirement and market being assessed. - Do not hide known nonconformities, temporary workarounds, partial standard application, or Article 14 reliance behind generic 'compliant' language. - Do not cite EN 301 549 or WCAG without naming the version, clauses, success criteria, test date, scope limits and unresolved failures. - Do not forget product documentation and support information; EN 301 549 includes requirements for electronic product documentation and ICT support-service documentation where applicable. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019L0882&ref=sorena.io) - EAA source for separating product documentation and EU declarations from service information and for documenting exceptions. - [ETSI - EN 301 549 V3 overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Source for EN 301 549's broader ICT scope beyond web-only WCAG statements. ### [What does the EAA cover in an e-commerce checkout?](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md#what-does-the-eaa-cover-in-an-e-commerce-checkout) *Module: [EAA e-commerce checkout accessibility](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md)* Directive (EU) 2019/882 defines e-commerce services as services provided at a distance, through websites or mobile device-based services, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract. - Confirm that the tested flow is consumer-facing and is used to conclude a consumer contract. - Include website and mobile app checkout variants when both are offered to consumers. - Include accessibility information about the products or services being sold when the responsible economic operator provides that information. - Do not treat physical point-of-sale payment terminals as the same fact pattern as online checkout; the Directive defines payment terminals as physical point-of-sale devices, not virtual environments. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Defines e-commerce services, lists e-commerce in Article 2 scope, and separates physical payment terminals from virtual payment environments. - [European Commission - European Accessibility Act policy page](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en?ref=sorena.io) - Commission policy page used for the public EAA context and covered-products-and-services framing. ### [What should the checkout test cover?](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md#what-should-the-checkout-test-cover) *Module: [EAA e-commerce checkout accessibility](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md)* Use the EAA service requirements as the control map. Annex I requires service information to be provided through accessible channels, websites and mobile services to be perceivable, operable, understandable, and robust, and available support services to provide accessibility and assistive-technology compatibility information in accessible communication modes. - Product and service information: names, prices, variants, delivery choices, accessibility information supplied by the responsible operator, and terms needed before purchase. - Controls and navigation: keyboard path, focus order, labels, headings, state changes, modals, cart updates, and status messages. - Forms and errors: required fields, input purpose, validation messages, error suggestions, address lookup, coupon fields, and order review. - Identification and security: sign-in, account creation, password reset, multi-factor prompts, biometric alternatives where relevant, session timeout, and fraud checks. - Payment and confirmation: card fields, hosted payment frames or redirects, wallet flows, electronic signatures where used, failure messages, receipts, and order-status pages. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Annex I sets the general service accessibility requirements and the specific e-commerce requirements for accessibility information, identification, security, and payment. - [ETSI - EN 301 549 accessibility standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Official ETSI overview for EN 301 549, the ICT accessibility standard useful for mapping web, mobile, software, and assistive-technology test evidence. ### [What evidence should be kept for an EAA checkout review?](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md#what-evidence-should-be-kept-for-an-eaa-checkout-review) *Module: [EAA e-commerce checkout accessibility](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md)* Service providers must prepare information explaining how covered services meet applicable accessibility requirements, make that information publicly available in written and oral format including accessible formats, and keep it for as long as the service is in operation. - Scope record: consumer-facing checkout URL or app screen set, countries or markets covered, service provider owner, and whether the flow concludes a consumer contract. - Requirement map: Annex I general service requirements, e-commerce-specific identification, security and payment requirements, and any standards clauses used as technical evidence. - Test evidence: automated findings, manual keyboard and screen-reader notes, mobile app checks where relevant, payment-provider test evidence, screenshots or recordings, defect tickets, fixes, and retests. - Service information: general description of the service in accessible formats, explanation of checkout operation, accessibility statement or equivalent terms content, and support-service accessibility information. - Change control: review trigger for checkout redesigns, payment provider changes, new authentication methods, mobile app releases, harmonised-standard updates, complaints, incidents, or authority requests. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Article 13 and Annex V support the service-provider evidence model for public information, service-operation descriptions, monitoring, and authority response. - [European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Commission source for the role of common European accessibility standards in ICT and internal-market accessibility implementation. ### [Common checkout documentation mistakes](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md#common-checkout-documentation-mistakes) *Module: [EAA e-commerce checkout accessibility](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md)* The main risk is producing a generic accessibility statement that does not prove the checkout can actually be completed. Evidence is stronger when it follows the money path and the account path from start to finish. - Do not cite EN 301 549 or WCAG as a standalone EAA conclusion without mapping the checkout to EAA service and e-commerce requirements. - Do not exclude payment-provider frames, redirects, authentication prompts, fraud checks, or wallet flows if they are necessary to complete the purchase. - Do not remove accessibility support during security steps; if security requirements constrain assistive-technology access, record the constraint and the accessible alternative tested. - Do not publish product or service accessibility information only in an inaccessible PDF, image, modal, or account-only area if consumers need it before purchase. - Do not let release evidence go stale after checkout redesigns, new payment providers, mobile app changes, or updates to the standards used in the conformance claim. 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 services conforming after changes and to make service information accessible. - [ETSI - EN 301 549 accessibility standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports treating EN 301 549 as ICT accessibility test evidence across web pages, mobile applications, software, hardware, and combinations. ### [How should EN 301 549 and WCAG evidence be mapped for the EU Accessibility Act?](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md#how-should-en-301-549-and-wcag-evidence-be-mapped-for-the-eu-accessibility-act) *Module: [EN 301 549 clause mapping for the EU Accessibility Act](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md)* 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 EN 301 549 clauses apply to the ICT features being assessed and what test or review evidence supports each result. - Start each row with the EAA Annex I outcome or information requirement, then add the EN 301 549 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 EN 301 549 evidence such as functional performance statements, hardware, closed functionality, two-way voice, video, documentation, support, and relay-service requirements where relevant. - 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. 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 tie evidence back to Article 4, Annex I accessibility requirements, Article 14 limits, Article 15 presumption, product documentation, and service information. - [ETSI - EN 301 549 V3 standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports EN 301 549 as the ICT accessibility standard and explains self-scoping requirements, the clause structure, and the planned EAA-supporting revision. - [European Commission - Harmonised standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports the rule that harmonised standards are voluntary and that OJEU publication is the relevant trigger for presumption of conformity or other legal effect. - [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, in implementing accessibility policy across the internal market. ### [What should the clause mapping table contain?](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md#what-should-the-clause-mapping-table-contain) *Module: [EN 301 549 clause mapping for the EU Accessibility Act](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md)* 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. - 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. - EN 301 549 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. 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 documentation boundary for products and services, including applied harmonised standards, alternative solutions, Article 14 assessment, and service accessibility information. - [ETSI - EN 301 549 V3 standard overview](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 clauses by ICT feature rather than by commercial product category. - [European Commission - Harmonised standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports separating voluntary standard use from mandatory legal requirements and OJEU-based legal effects. ### [Where does WCAG fit inside EN 301 549?](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md#where-does-wcag-fit-inside-en-301-549) *Module: [EN 301 549 clause mapping for the EU Accessibility Act](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md)* WCAG evidence belongs inside the EN 301 549 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. - Use EN 301 549 clause 9 for web content evidence and keep page-level WCAG findings traceable to the assessed URLs or templates. - Use EN 301 549 clause 10 for non-web document evidence where documents are part of the product or service information. - Use EN 301 549 clause 11 for non-web software evidence, including native applications and embedded software where relevant. - Do not let a WCAG pass hide unresolved EN 301 549 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. Sources for this answer: - [ETSI - EN 301 549 V3 standard overview](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 for ICT requirements and the relationship to WCAG-based web, document, and software evidence. - [European Commission - Accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Supports EN 301 549 as the European ICT accessibility standard used in accessibility standardisation. ### [How should presumption of conformity be stated?](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md#how-should-presumption-of-conformity-be-stated) *Module: [EN 301 549 clause mapping for the EU Accessibility Act](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md)* 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. The same logic applies to technical specifications adopted under the Directive. - Use 'evidence mapped to EN 301 549' when the standard supports the technical assessment but the OJEU presumption claim has not been verified for the relevant EAA requirement. - Use 'presumption of conformity 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. 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 limits on presumption of conformity, partial standards use, Article 14 exceptions, and documentation duties for 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) - Supports OJEU publication and voluntary use of harmonised standards as distinct concepts. - [ETSI - EN 301 549 V3 standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports the caution that EN 301 549 V3.2.1 supports the Web Accessibility Directive and is planned to be revised to support Directive (EU) 2019/882. ### [Common mapping mistakes to avoid](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md#common-mapping-mistakes-to-avoid) *Module: [EN 301 549 clause mapping for the EU Accessibility Act](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md)* The main mistake is treating 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 EN 301 549 clause or WCAG criterion being relied on. - 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 presumption of conformity 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. 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 keeping EAA Annex I requirements, Article 14 exceptions, conformity documentation, and service information distinct in the evidence record. - [ETSI - EN 301 549 V3 standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports checking EN 301 549 clause applicability by ICT feature and precondition rather than assuming all clauses apply. - [European Commission - Harmonised standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Supports avoiding overclaiming because harmonised standards can be used to demonstrate compliance but remain voluntary. ### [Separate product checks from service checks](/artifacts/eu/accessibility-act/faq/authority-response.md#separate-product-checks-from-service-checks) *Module: [EU Accessibility Act authority request response](/artifacts/eu/accessibility-act/faq/authority-response.md)* For products, prepare the file a market surveillance authority would need to evaluate the product against the EAA: product identification, role in the supply chain, applicable accessibility requirements, conformity assessment, EU declaration of conformity where relevant, CE-marking evidence where relevant, technical documentation, and any Article 14 assessment relied on. - Route product requests to the owner of the technical file, conformity assessment, EU declaration of conformity, and accessibility test evidence. - Route service requests to the owner of the service description, user-facing accessibility information, support process, complaint log, and remediation plan. - If the same journey includes a product and a service, answer both parts separately so the authority can see which evidence belongs to which obligation. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Articles 19 and 23 distinguish product market surveillance from procedures for checking service compliance, complaints, reports, and corrective action. - [European Commission - European Accessibility Act policy page](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en?ref=sorena.io) - Commission overview confirming that the EAA covers selected products and services and aims to remove barriers caused by divergent Member State rules. - [ETSI - EN 301 549 accessibility standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - ETSI overview for the ICT accessibility standard often used to structure technical evidence for digital products and services. ### [Prepare the evidence authorities can actually review](/artifacts/eu/accessibility-act/faq/authority-response.md#prepare-the-evidence-authorities-can-actually-review) *Module: [EU Accessibility Act authority request response](/artifacts/eu/accessibility-act/faq/authority-response.md)* The response should show the authority how the conclusion was reached. For products, keep the technical documentation complete enough to identify the product, the applied requirements, the conformity assessment route, the standards or technical specifications used, and the test or design evidence supporting the declaration. - Keep product technical documentation, conformity assessment evidence, EU declaration of conformity, CE-marking evidence where relevant, supplier evidence, and test results together. - Keep service accessibility information, terms or equivalent service document, support-process evidence, complaint or report log, remediation tickets, and release evidence together. - Map accessibility claims to Annex I requirements and, where used, harmonised standards or technical specifications instead of relying on broad labels such as accessible by design. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Articles 13, 16, 19, 22, and 23 support service information, product declarations, technical documentation, and authority compliance checks. - [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Commission overview for how harmonised standards support presumption-of-conformity analysis when their references are published for the relevant requirements. - [ETSI - EN 301 549 accessibility standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - ETSI overview for EN 301 549, the ICT accessibility standard used to organize evidence for many web, software, document, support, and ICT functions. ### [Handle Article 14 assessments carefully](/artifacts/eu/accessibility-act/faq/authority-response.md#handle-article-14-assessments-carefully) *Module: [EU Accessibility Act authority request response](/artifacts/eu/accessibility-act/faq/authority-response.md)* Article 14 is not a shortcut for missing evidence. If an economic operator relies on fundamental alteration or disproportionate burden, the response should include the documented assessment, the criteria applied, the result, and the accessibility requirements still implemented to the extent required. - State whether Article 14 is being used for a specific product, service, feature, element, or function. - Attach the documented assessment and supporting evidence for fundamental alteration or disproportionate burden. - Show what accessibility requirements remain implemented and what remediation remains open. - Do not claim disproportionate burden based only on lack of priority, time, or knowledge. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Article 14 sets the fundamental-alteration and disproportionate-burden assessment rule; Articles 19 and 23 let authorities check those assessments. - [AccessibleEU - guidance on European accessibility legislation](https://accessible-eu-centre.ec.europa.eu/guidelines-and-support-materials_en?ref=sorena.io) - AccessibleEU guidance explains that fundamental alteration and disproportionate burden require documented assessment and that lack of priority, time, or knowledge is not a legitimate reason. ### [Respond to corrective action without inventing penalties](/artifacts/eu/accessibility-act/faq/authority-response.md#respond-to-corrective-action-without-inventing-penalties) *Module: [EU Accessibility Act authority request response](/artifacts/eu/accessibility-act/faq/authority-response.md)* If an authority identifies non-compliance, the response should focus on the corrective action the EAA framework actually describes: what is non-compliant, which requirement is affected, what action will bring the product or service into compliance, who owns it, and how completion will be evidenced. - Acknowledge the authority request and preserve the request, response deadline, product or service scope, and named contact. - Send only evidence that matches the requested product, service, version, market, and requirement. - Track corrective action by requirement, owner, release or process change, verification evidence, and authority correspondence. - Avoid stating EU-wide fine amounts, penalty bands, or enforcement deadlines unless the verified national law for the relevant Member State supports them. Sources for this answer: - [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Articles 20, 22, 23, and 30 support corrective-action handling, withdrawal or restrictions for unresolved product non-compliance, service corrective-action verification, and Member State penalty rules. - [AccessibleEU - guidance on European accessibility legislation](https://accessible-eu-centre.ec.europa.eu/guidelines-and-support-materials_en?ref=sorena.io) - AccessibleEU guidance summarizes authority checks for products and services, including corrective action and withdrawal for products where appropriate. ### [When does the EAA microenterprise exemption apply to services?](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md#when-does-the-eaa-microenterprise-exemption-apply-to-services) *Module: [EU Accessibility Act microenterprise exemption and disproportionate burden](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md)* Article 4(5) exempts microenterprises providing services from complying with the EAA accessibility requirements for services and obligations relating to compliance with those requirements. The exemption is tied to service provision and microenterprise status; it is not a general group-company, product, or supply-chain exemption. - Use the service exemption only for a covered service provider that genuinely meets the EAA microenterprise definition. - Keep evidence for the headcount and financial status used for the conclusion, plus the covered service category being assessed. - Do not extend the service exemption to covered products without a separate product analysis. Sources for this answer: - [Directive (EU) 2019/882 - European Accessibility Act](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Defines microenterprise status and states the Article 4(5) exemption for microenterprises providing services. - [European Commission - European Accessibility Act](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en?ref=sorena.io) - Commission overview explaining that the EAA is a directive for accessible products and services in the internal market. ### [How does Article 14 work for fundamental alteration or disproportionate burden?](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md#how-does-article-14-work-for-fundamental-alteration-or-disproportionate-burden) *Module: [EU Accessibility Act microenterprise exemption and disproportionate burden](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md)* Article 14 limits EAA accessibility requirements only to the extent that compliance would require a significant change resulting in fundamental alteration of the product or service's basic nature, or would impose a disproportionate burden on the economic operator. The operator must still apply the accessibility requirements that do not create that result. - Assess each product or service and each affected accessibility requirement; do not treat Article 14 as a company-wide opt-out. - Use Annex VI categories for the burden file: organisational costs, training, process changes, guidance material, accessibility design, production, testing, documentation, benefits, use frequency, and turnover ratio. - Exclude unsupported reasons. Recital 66 says lack of priority, time, or knowledge should not be considered legitimate reasons for a disproportionate-burden conclusion. - If accessibility funding from public or private sources is provided for improving accessibility, Article 14(6) says the operator is not entitled to rely on disproportionate burden. Sources for this answer: - [Directive (EU) 2019/882 - Article 14 and Annex VI](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Sets the Article 14 limits for fundamental alteration and disproportionate burden and lists Annex VI assessment criteria. ### [What records and reassessments are required?](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md#what-records-and-reassessments-are-required) *Module: [EU Accessibility Act microenterprise exemption and disproportionate burden](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md)* Article 14(3) requires economic operators to document the Article 14 assessment and keep all relevant results for five years from the last making available of the product on the market or after the service was last provided, as applicable. Authorities may request a copy of that assessment. - For non-microenterprise product operators: keep the Article 14 assessment results for five years from last market availability of the product. - For product microenterprises relying on Article 14: keep enough facts to answer an authority request, even though Article 14(4) removes the formal documentation duty in Article 14(3). - For service providers relying on disproportionate burden: track service category or type, last assessment date, service changes, authority requests, and the five-year reassessment backstop. - For products using Article 14: identify the excepted accessibility requirements in the EU declaration of conformity. Sources for this answer: - [Directive (EU) 2019/882 - Article 14 records and reassessment](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the five-year retention rule, product microenterprise documentation derogation, authority-request duty, service reassessment triggers, and Article 14 authority notification limits. - [Directive (EU) 2019/882 - product conformity documentation](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports the EU declaration and technical-documentation treatment when a product operator relies on Article 14. ## FAQ Pagination - Canonical index (page 1): [/artifacts/eu/accessibility-act/faq/items](/artifacts/eu/accessibility-act/faq/items.md) - Page 1 rule: `/page/1` is intentionally not generated; use the canonical index markdown URL. - Current page: 1 of 3 Pages: [1](/artifacts/eu/accessibility-act/faq/items.md) | [2](/artifacts/eu/accessibility-act/faq/items/page/2.md) | [3](/artifacts/eu/accessibility-act/faq/items/page/3.md) [Next page](/artifacts/eu/accessibility-act/faq/items/page/2.md) *Recommended next step* *Placement: after evidence section* ## Check EAA scope before planning remediation Map the product or service to Article 2, Annex I, applicable standards evidence, service information, and any Article 14 assessment before setting release or remediation work. - [Open Research Copilot](/solutions/research-copilot.md): Answer EAA scope, timing, and interpretation questions with cited outputs. - [Talk through implementation](/contact.md): Review your EAA scope, standards map, evidence file, and release risks. --- [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/items