European Accessibility Act: Dates, Scope and EN 301 549
The European Accessibility Act (EAA), Directive (EU) 2019/882, has applied in EU Member States since 28 June 2025. It requires a defined list of consumer-facing products and services, including e-commerce, consumer banking, e-books, passenger transport and electronic communications, to meet common accessibility requirements. Services supplied by microenterprises (fewer than 10 people and turnover or balance sheet of EUR 2 million or less) are exempt. For websites and apps, most teams use the European ICT accessibility standard, EN 301 549, as their technical benchmark. As of November 2026 it is moving from version 3.2.1 (WCAG 2.1) to version 4.1.1 (WCAG 2.2), and no version of it has yet been cited in the Official Journal under the EAA. Businesses answer to the national law of each country where they sell, which transposes the Directive.
Quick facts
| Question | Answer (as of November 2026) |
|---|---|
| Legal text | Directive (EU) 2019/882 of 17 April 2019, published in OJ L 151, 7.6.2019 |
| Applies from | 28 June 2025 (Article 31(2)) |
| Who enforces it | Each Member State, through its own transposing law, authorities and penalties |
| Who is covered | Economic operators placing in-scope products on the EU market or providing in-scope services to consumers in the EU |
| Microenterprise exemption | Services only: fewer than 10 persons and turnover or balance sheet not above EUR 2 million |
| Technical baseline for websites and apps | EN 301 549 V3.2.1 (WCAG 2.1 A and AA) is the current reference per the Commission’s AccessibleEU centre; V4.1.1 (WCAG 2.2 A and AA) was published in September 2026. No version is yet cited in the Official Journal under the EAA |
| Information duty | Services must publish how they meet the requirements (Article 13(2), Annex V) |
What the Directive covers
The EAA is a single-market law. Its aim is to remove the differences between national accessibility rules so that a product or service built to one set of requirements can be sold across the EU. Article 4(1) says economic operators may only place on the market products, and only provide services, that comply with the accessibility requirements in Annex I, subject to the fundamental alteration and disproportionate burden rules in Article 14. The Commission’s EAA page describes it as covering the products and services most important for people with disabilities, and notes that the Commission monitors national transposition.
A directive does not bind businesses directly. Each Member State wrote its own law, so the obligations, regulators, deadlines for paperwork and fines you face come from the national law of the country where the product is placed on the market or the service is provided.
Products in scope
Article 2(1) lists products placed on the market after 28 June 2025:
- consumer general-purpose computer hardware systems and their operating systems;
- payment terminals;
- self-service terminals dedicated to services covered by the Directive: automated teller machines, ticketing machines, check-in machines, and interactive self-service terminals providing information (except those built into vehicles, aircraft, ships or rolling stock);
- consumer terminal equipment with interactive computing capability used for electronic communications services;
- consumer terminal equipment with interactive computing capability used for accessing audiovisual media services;
- e-readers.
All products must meet Section I of Annex I (product information and instructions, user interface and functionality design, and support services), and all except self-service terminals must also meet Section II (packaging, and installation, maintenance, storage and disposal instructions) (Article 4(2)). Manufacturers also carry conformity-assessment, CE marking and documentation duties (Article 7).
Services in scope
Article 2(2) lists services provided to consumers after 28 June 2025:
- electronic communications services (except machine-to-machine transmission);
- services providing access to audiovisual media services;
- specified elements of air, bus, rail and waterborne passenger transport: websites, mobile services and apps, electronic tickets and ticketing services, travel information including real-time information, and interactive self-service terminals. For urban, suburban and regional transport only the self-service terminals are covered;
- consumer banking services;
- e-books and dedicated software;
- e-commerce services.
Article 2(3) adds the answering of emergency communications to the European emergency number 112. Member States may delay that element until 28 June 2027 at the latest (Article 31(3)).
The Directive defines e-commerce services in Article 3(30) as services provided at a distance, through websites and mobile device-based services, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract. Consumer banking in Article 3(28) means the following when provided to consumers: credit agreements under the consumer credit and mortgage credit directives (2008/48/EC and 2014/17/EU), certain investment services, payment services, services linked to a payment account, and electronic money.
What is out of scope
Article 2(4) removes five kinds of website and app content from the Directive:
- pre-recorded time-based media published before 28 June 2025;
- office file formats published before 28 June 2025;
- online maps and mapping services, if essential navigation information is provided in an accessible digital manner;
- third-party content that the operator neither funds, develops nor controls;
- archives, meaning content not updated or edited after 28 June 2025.
The services list is also limited to services provided to consumers. A business-to-business tool that no consumer uses is not named in Article 2(2), although procurement rules, other national law and customer contracts may still ask for accessibility.
The microenterprise exemption
Article 4(5) states that microenterprises providing services are exempt from the service accessibility requirements and from any obligations relating to compliance with them. Article 3(23) defines a microenterprise as an enterprise that employs fewer than 10 persons and has an annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million.
Three limits matter in practice:
- Services only. For products, microenterprises are not excused from the requirements. Article 14(4) only releases microenterprises dealing with products from documenting their Article 14 assessment, and they must still give a market surveillance authority the relevant facts on request.
- Group companies count. Recital 53 says microenterprises must genuinely fulfil Commission Recommendation 2003/361/EC, the EU’s general definition of micro, small and medium-sized enterprises, and the case law against circumventing it. That Recommendation adds in the staff and financial figures of partner and linked enterprises (Annex, Article 6), so a small subsidiary is measured together with its group.
- Guidance is promised. Article 4(6) requires Member States to provide guidelines and tools to microenterprises. Germany’s BFSG, for example, tasks the labour ministry with guidelines for microenterprises (section 3(3)).
Both Germany and Ireland repeat the exemption for services in their national laws (see the national examples below).
Transitional periods
The Directive gives limited extra time for existing arrangements (Article 32):
- Until 28 June 2030, service providers may keep providing their services using products they lawfully used to provide similar services “before that date” (Article 32(1)). National texts read that date differently: Germany’s BFSG (section 38(1)) says products used before 28 June 2025, while Ireland’s Regulation 38(1)(a) says before 28 June 2030.
- Service contracts agreed before 28 June 2025 may continue without alteration until they expire, but no longer than five years from that date.
- Member States may allow self-service terminals lawfully used before 28 June 2025 to continue until the end of their economically useful life, no longer than 20 years after entry into use.
None of these gives a grace period for a new website, a redesigned checkout or a new app launched after the application date. The 2025 date applies to new products and to services provided after it.
Dates table
| Date | Event | Source |
|---|---|---|
| 17 April 2019 | Directive (EU) 2019/882 adopted | EUR-Lex |
| 28 June 2022 | Member States had to adopt and publish national laws (Article 31(1)) | EUR-Lex |
| 28 June 2025 | National measures apply; in-scope products placed on the market and services provided to consumers after this date | EUR-Lex |
| 24 August 2026 | EN 301 549 V4.1.1 adopted by ETSI, CEN and CENELEC | ETSI (V4.1.1 foreword) |
| 2 September 2026 | EN 301 549 V4.1.1 published | Davis Wright Tremaine; ETSI document dated 2026-09 |
| 28 June 2027 | Latest date a Member State may start applying the 112 emergency-communications rules (Article 31(3)) | EUR-Lex |
| 28 June 2030 | Transitional period for products already used by service providers ends; pre-2025 service contracts can no longer continue unaltered (Article 32(1)); Commission’s first report due (Article 33) | EUR-Lex |
| Up to 20 years after entry into use | Optional extension for existing self-service terminals (Article 32(2)); Germany set 15 years, Ireland kept 20 | EUR-Lex, BFSG, S.I. 636/2023 |
The accessibility requirements, in practice
Annex I sets the requirements in functional terms. Section III applies to all services except urban, suburban and regional transport (Article 4(3)), and Section IV adds requirements for specific services. Section III in short:
- Products used to provide the service must meet the product requirements of Section I (and Section II where it applies).
- Information about how the service works, its link to any products used, and their accessibility and compatibility with assistive devices must be given through more than one sensory channel, in text that can be turned into other formats, with adequate font size, contrast and spacing, and with alternatives for non-text content.
- Websites, related online applications and mobile applications must be made accessible “in a consistent and adequate way” by being perceivable, operable, understandable and robust.
- Where support services exist (help desks, call centres, technical support, relay and training services), they must give information on the service’s accessibility and its compatibility with assistive technologies in accessible modes of communication.
Section IV then adds the requirements by service type. The table puts the Annex I wording next to the practical work it triggers; the right-hand column is an editorial reading of the text.
| Service | What Annex I Section IV asks for | Practical consequence |
|---|---|---|
| E-commerce | Accessibility information on the products and services sold, when the responsible economic operator provides it; identification, security and payment functionality, and identification methods, electronic signatures and payment services, that are perceivable, operable, understandable and robust | The sign-in, checkout, payment and confirmation steps must work with a keyboard and screen reader, and with error handling people can recover from. See form design for all users and keyboard navigation |
| Consumer banking | Identification methods, electronic signatures, security and payment services that are perceivable, operable, understandable and robust; information not above CEFR level B2 in complexity | Authentication flows and plain-language content are part of the requirement, not only the interface |
| E-books | Synchronised text and audio where both exist; files that do not stop assistive technology working; access to content, navigation and flexible presentation; alternative renditions that work with assistive technologies; accessibility metadata; DRM that does not block accessibility features | Publishers and e-book retailers need accessible files and metadata, not an accessible shop alone |
| Passenger transport (air, bus, rail, waterborne, except urban, suburban and regional) | Information on the accessibility of vehicles, the surrounding infrastructure and built environment, and on assistance; information on smart ticketing, real-time travel information and additional service information | Booking sites, apps, e-tickets and disruption notices all count |
| Urban, suburban and regional transport | Accessible self-service terminals, meeting the product requirements of Section I | Ticket machines and information terminals; Recital 35 relies on the e-commerce rules for websites that sell tickets online |
| Audiovisual media access | Electronic programme guides that are perceivable, operable, understandable and robust and show accessibility availability; subtitles, audio description, spoken subtitles and sign language fully transmitted, synchronised and under user control | See video captioning and audio description |
| Electronic communications | Real-time text alongside voice; total conversation where video is offered; emergency communications synchronised and passed to the most appropriate emergency answering point | Mainly relevant to telecoms operators and messaging providers |
How EN 301 549 relates to WCAG
Meeting a harmonised standard whose reference has been published in the Official Journal gives a presumption of conformity with the requirements it covers (Article 15(1)). The European standard for ICT accessibility is EN 301 549.
For web content the standard takes its requirements from WCAG. Version 3.2.1 (2021) is based on WCAG 2.1 Level AA, and the Commission’s AccessibleEU centre still names it as the current reference. EN 301 549 was first published in 2014 under Commission Mandate M 376, for the public procurement of ICT. V3.2.1 was prepared for the Web Accessibility Directive, which covers public-sector websites and apps, and the Commission cited it under that directive in Implementing Decision (EU) 2021/1339. As of 16 November 2026, EUR-Lex lists no implementing decision citing any version of EN 301 549 under the EAA.
Version 4.1.1, dated 2026-09, is the first prepared under the Commission’s standardisation request C(2022) 6456 to provide a voluntary means of conforming with the EAA. According to its foreword, it:
- updates clauses 9, 10 and 11 (web, non-web documents and software) to align with WCAG 2.2;
- revises and extends the real-time text requirements to cover total conversation;
- adds Annex ZB, which shows how the standard relates to the essential requirements of Directive (EU) 2019/882;
- adds clause A.2, which allows conformance of specific ICT products and services with the EAA requirements to be evaluated.
The foreword adds that the presumption of conformity arises only once the document is cited in the Official Journal under the EAA. AccessibleEU said on 7 September 2026 that the Commission had not yet cited V4.1.1, and EUR-Lex showed no citation as of 16 November 2026. A single Official Journal notice will change that, so check EUR-Lex before relying on V4.1.1 for the presumption. The foreword gives 24 August 2026 as the date the three European standards bodies adopted V4.1.1, and law firm commentary (Davis Wright Tremaine, 18 September 2026) dates its publication to 2 September 2026.
What this means for a website team:
- WCAG 2.2 AA is a sensible working target, because it builds on WCAG 2.1 AA, the basis of V3.2.1, and is the basis of V4.1.1. The WCAG 2.2 guide lists the additions.
- EN 301 549 goes beyond WCAG. It also covers closed functionality, real-time text and total conversation, video features, hardware, and information about products and services. A web shop mostly needs clause 9 (web), but clause 12 (information about products and services) also applies to the service, and clause 11 (non-web software) covers native apps.
- Using the standard is voluntary. V4.1.1 gives no presumption until it is cited, and V3.2.1 is cited only under the Web Accessibility Directive, so a business should be able to show directly that it meets the Annex I requirements; a dated test record against a named version of the standard is the clearest way to do that.
- An accessibility conformance report (ACR) records testing against the standard. See VPAT and ACR.
Publishing service information
Article 13(2) requires service providers to prepare the information in Annex V and to explain how their services meet the applicable requirements. The information must be made available to the public in written and oral format, including in a manner accessible to people with disabilities, and be kept for as long as the service operates.
Annex V says the information is to be included in the general terms and conditions or an equivalent document. It must contain, where applicable, a general description of the service in accessible formats, the explanations needed to understand how the service operates, and a description of how the Annex I requirements are met. Providers may apply harmonised standards in full or in part, and must also provide information showing that their delivery process and monitoring ensure compliance.
The Directive does not use the term “accessibility statement” for this. National laws and regulators decide the form, and many businesses publish a separate accessibility page linked from the terms. Other duties in Article 13 include procedures to keep the service in conformity as it changes (Article 13(3)), corrective measures and notice to authorities where a service is not compliant (Article 13(4)), and providing information to authorities on a reasoned request (Article 13(5)).
Fundamental alteration and disproportionate burden
Article 14 limits the requirements to the extent that compliance does not fundamentally alter the basic nature of the product or service and does not impose a disproportionate burden. The operator must assess both, judging the burden against the Annex VI criteria, document the assessment and keep the results for five years after the product was last made available or the service last provided (Article 14(2) and (3)). Service providers relying on disproportionate burden must renew the assessment when the service changes, when the authority checking compliance asks, and in any event at least every five years (Article 14(5)). An operator that receives outside funding, public or private, for improving accessibility cannot rely on disproportionate burden (Article 14(6)). An operator relying on either exception for a specific product or service must inform the relevant authorities of the Member State where it is sold or provided; microenterprises are exempt from that notice (Article 14(8)).
Does the EAA apply to my business?
This table applies Articles 2, 3 and 4 and the national texts to common situations. Edge cases, such as group structures and mixed consumer and business customers, need a lawyer who knows the national law.
| Situation | Likely result | Why |
|---|---|---|
| Online shop selling to consumers in the EU; 25 staff, EUR 6 million turnover | In scope | E-commerce service (Article 2(2)(f)); not a microenterprise |
| Online shop; 8 staff, EUR 1.4 million turnover | Exempt from the service requirements | Microenterprise (Article 4(5)), provided it is not part of a larger group; still watch national guidance and whether the shop sells in-scope products |
| Online shop; 8 staff, EUR 2.8 million turnover and EUR 1.9 million balance sheet | Exempt on the Directive’s wording | Definition uses turnover or balance sheet; check how the national law words it |
| Online shop based outside the EU, selling to consumers in the EU | In scope unless a microenterprise | A service provider includes anyone making offers to provide a service to consumers in the Union (Article 3(4)) |
| Software sold only to businesses | Usually outside Article 2(2) | Services list covers services provided to consumers |
| Informational site or blog with no sales and no booking | Not named in Article 2(2) | E-commerce services are provided with a view to concluding a consumer contract (Article 3(30)) |
| Bank or payment provider offering consumer accounts online | In scope | Consumer banking services (Article 2(2)(d), defined in Article 3(28)) |
| E-book publisher or reader-app provider | In scope unless a microenterprise | E-books and dedicated software are a service (Article 2(2)(e)), so the microenterprise exemption can apply; it does not cover e-readers, which are products |
| Maker of e-readers or payment terminals | In scope for products | The service exemption does not remove the product requirements; microenterprises only skip documenting the Article 14 assessment (Article 14(4)) |
| Regional bus operator | Self-service terminals under the transport heading; online ticket sales may count as e-commerce | Article 2(2)(c) limits urban, suburban and regional transport to terminals, but Recital 35 relies on the e-commerce rules for operators’ ticket-selling websites, and public operators already fall under the Web Accessibility Directive |
| Archive pages not edited since 28 June 2025 | Excluded content | Article 2(4)(e) |
Market surveillance and penalties
Enforcement belongs to national authorities. Article 29 requires adequate and effective means of ensuring compliance, including the right for consumers to act before courts or administrative bodies, and for organisations with a legitimate interest to engage on a complainant’s behalf. Article 30 requires penalties to be effective, proportionate and dissuasive, with effective remedial action, and to reflect the seriousness of the non-compliance, the number of units or services concerned and the number of people affected. The Directive sets no fine amounts, so the figures differ by country.
Germany: Barrierefreiheitsstärkungsgesetz (BFSG)
Germany’s BFSG applies to products placed on the market and services provided to consumers after 28 June 2025 and mirrors the Directive’s lists. Section 3(3) exempts microenterprises that provide services. Section 14 requires service providers to prepare the Annex 3 information and make it publicly available in accessible form. The Länder (federal states) run market surveillance (section 20). Under section 37, certain violations, including placing a non-compliant product on the market or offering a service in breach of section 14(1), can be fined up to EUR 100,000, and other listed violations up to EUR 10,000. Section 38 lets self-service terminals already in use stay in service until the end of their economic life, but not longer than 15 years after first use, shorter than the Directive’s 20-year ceiling.
Ireland: S.I. No. 636 of 2023
Ireland’s European Union (Accessibility Requirements of Products and Services) Regulations 2023 came into operation on 28 June 2025. The Competition and Consumer Protection Commission (CCPC) is the market surveillance authority for products and also checks e-books and e-commerce services, while other named compliance authorities, including the Central Bank of Ireland and the Commission for Communications Regulation, check services in their sectors (Regulation 4). The microenterprise exemption for services appears in Regulation 5(4), and the market surveillance authority must provide guidelines and tools to microenterprises (Regulation 5(6)). Under Regulation 32(6), an offence can lead, on summary conviction, to a class A fine or up to 6 months in prison or both, and on conviction on indictment to a fine up to EUR 60,000 or up to 18 months in prison or both. Ireland kept the Directive’s 20-year ceiling for self-service terminals already in use (Regulation 38(2)).
What the two examples show
The same Directive produces different consequences: Germany uses administrative fines through Länder authorities, while Ireland uses criminal offences split across sector authorities. Both copy the exemption, scope lists and 28 June 2025 start date, but they part ways on the transitional rules: 15 against 20 years for existing self-service terminals, and different cut-off dates for products already in use. A business selling in several countries must therefore check each national law as well as the law of its home state.
Practical checklist
- Establish whether any of your products or services is on the Article 2 lists and whether it is offered to consumers in the EU.
- Test the microenterprise exemption against the Article 3(23) definition and your national law, using the latest accounts.
- Choose a technical target. WCAG 2.2 AA through the checkout, sign-in, payment, account and support journeys is a defensible target; record the version and level.
- Write the Annex V information, include it in the terms or an equivalent document, and make the page itself accessible.
- Keep a dated assessment if you rely on fundamental alteration or disproportionate burden, inform the national authority when you rely on it for a specific product or service (unless you are a microenterprise), and renew a burden assessment at least every five years.
- Set up a route for accessibility complaints and a process for corrective action when something fails.
- Re-check the Official Journal for a notice citing EN 301 549 V4.1.1.
Sources
- Directive (EU) 2019/882 (European Accessibility Act), EUR-Lex
- European Accessibility Act, European Commission
- The European accessibility standard EN 301 549 has been updated, AccessibleEU (7 September 2026)
- ETSI EN 301 549 V4.1.1 (2026-09)
- Commission Implementing Decision (EU) 2021/1339, EUR-Lex
- EAA ICT standards update, Davis Wright Tremaine (18 September 2026)
- Commission Recommendation 2003/361/EC on the definition of micro, small and medium-sized enterprises, EUR-Lex
- BFSG sections 1, 3, 14, 20, 37 and 38, Gesetze im Internet
- S.I. No. 636/2023, Irish Statute Book