Contentoren

Websites & web design

European Accessibility Act 2026: Website Compliance Guide

European Accessibility Act website requirements in 2026: who is in scope, how national authorities enforce, what fines apply and a 25-point checklist to comply.

18 min readby Contentoren Editorial Team
Share
A blind man wearing headphones orders groceries on a laptop with a screen reader at his kitchen table, his white cane leaning beside him.

Key takeaways

In short:

  • The European Accessibility Act (EAA), Directive (EU) 2019/882, has applied in all EU member states since 28 June 2025. Websites and apps that let consumers conclude a contract (shops, bookings, subscriptions) must be accessible.
  • Exempt: microenterprises providing services (fewer than 10 staff and at most €2 million turnover or balance sheet) and purely B2B offerings.
  • Enforcement and fines are national. Germany's MLBF checks websites without a specific trigger and can fine up to €100,000; other countries set different authorities and amounts.
  • The technical baseline today is WCAG 2.1 AA via EN 301 549. The new EN 301 549 V4.1.1 (WCAG 2.2) was published in September 2026 but, as of November 2026, is not yet cited in the Official Journal.
  • Overlays and widgets do not make a website compliant. Fixed code, accessible content and published accessibility information do.

The European Accessibility Act is one directive, but it reaches you through 27 national laws. If you run an online shop in Germany and sell to customers in Austria, France or Ireland, the same technical work satisfies all of them, but authorities, procedures and fines differ. This guide explains who is in scope, how enforcement works in practice, which standard to build against and how to plan the work. Germany's law, the BFSG, serves as the detailed example because its market surveillance authority has published how it checks websites. This is not legal advice.

What is the European Accessibility Act?

The European Accessibility Act is Directive (EU) 2019/882 on accessibility requirements for products and services. Under Article 31, member states had to transpose it by 28 June 2022 and apply it from 28 June 2025. According to the European Commission, it covers products and services such as computers and operating systems, ATMs and ticketing machines, smartphones, banking services, e-books, passenger transport services and e-commerce.

For most businesses with a website, the decisive category is e-commerce services: "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" (Article 3 of the directive). The products you sell do not matter. Germany's federal accessibility agency confirms in its e-commerce FAQ that a shop is in scope even when its goods are not themselves listed in the law. The German labour ministry's guidelines use a hair salon with online appointment booking as an example: the "entire website including check-out" must be accessible.

Does the EAA apply to my website?

Decision tree

  1. Can consumers conclude a contract on your website or app? That includes purchases, bookings, subscriptions or account openings. If not, your site is usually not an e-commerce service under the EAA. Go to step 5.
  2. Do you sell exclusively to businesses? A "consumer" is a natural person acting outside their trade, business or profession. A genuinely B2B-only shop is outside scope. If private individuals can easily order, that position is hard to defend.
  3. Are you a microenterprise? That means fewer than 10 employees and annual turnover or balance sheet total of no more than €2 million. Under Article 4(5), microenterprises providing services are exempt. The exemption does not cover products.
  4. Are you in another listed sector? Banking, telecoms, passenger transport and e-books carry additional sector-specific requirements.
  5. Even without an obligation, accessibility pays off if you are growing past the thresholds, supply public-sector buyers or are planning a redesign. Building it in costs far less than retrofitting.

Typical cases

Situation EAA obligation for the website?
B2C online shop, 25 employees Yes
Clinic, salon or garage with online booking, 12 employees Yes, booking counts as e-commerce per German guidance
Hotel with its own booking engine, 8 employees, €1.5 million turnover No, microenterprise providing a service
B2B-only shop, orders require a business ID Usually no
Brochure website with contact form, no contract online Usually no; check edge cases
Online course or subscription for consumers, 40 employees Yes

A firm with ten or more employees cannot use the microenterprise exemption, however small its turnover. Whether an enquiry form that leads to an offer later counts as "with a view to concluding a consumer contract" has not been settled by the courts.

Does it cover the whole site or just the checkout?

The EAA requires services to be "perceivable, operable, understandable and robust". German guidance reads this as covering the whole website or app, not just the purchase path. The German law's monitoring method (BFSG Annex 1) shows what inspectors look at: home page, login, sitemap, contact, help and legal pages; at least one page per service, including search; the accessibility information page; pages with a distinct layout; downloadable documents; every step of a process once one step is sampled; plus at least 10% randomly selected pages.

The directive excludes some content. Prerecorded media and office file formats published before 28 June 2025 are out, as are online maps whose essential information is provided accessibly, archives that are no longer updated, and third-party content that you neither fund, develop nor control. Tools you choose and pay for, such as cookie banners, chat widgets or booking plugins, will in our view rarely fall under that exclusion.

Is there a transition period until 2030?

Not for your website. Article 32 lets service providers keep using products they lawfully used before 28 June 2025 until 28 June 2030. It also allows service contracts agreed before 28 June 2025 to continue unchanged until they expire, but for no longer than five years from that date. Member states may let self-service terminals run for up to 20 years; Germany chose 15 (§ 38 BFSG). New sales, bookings and contracts through your website have been covered since 28 June 2025.

Who enforces the EAA, and what are the fines?

Article 30 only says penalties must be "effective, proportionate and dissuasive" and accompanied by remedial action. The table shows what we could verify in the primary legal texts or official government sources. We have deliberately left out amounts we could not confirm.

Country Transposition Authority for e-commerce Maximum fine (verified)
Germany Barrierefreiheitsstärkungsgesetz (BFSG) MLBF, joint authority of all 16 states, Magdeburg Up to €100,000 for offering a non-compliant service; up to €10,000 for other breaches (§ 37)
Austria Barrierefreiheitsgesetz (BaFG), BGBl. I Nr. 76/2023 Sozialministeriumservice (§ 21) Up to €80,000; up to €50,000 for micro and SMEs (§ 36)
Ireland S.I. No. 636/2023 Competition and Consumer Protection Commission (Reg. 4) Up to €60,000 and/or 18 months on conviction on indictment
France Loi n° 2023-171, art. 16; Décret n° 2023-931 (France Num summary) DGCCRF €7,500 per legal person (€15,000 if repeated), cumulative per e-commerce service and per obligation
Netherlands Implementatiewet toegankelijkheidsvoorschriften producten en diensten ACM for e-commerce (Ondernemersplein) Not verified
Spain Ley 11/2023, Title I Authorities designated by the autonomous communities (Art. 27) Set by sector legislation, otherwise RDL 1/2013 (Art. 30); not quantified here

Two practical differences matter for cross-border sellers. In the Netherlands, according to Ondernemersplein, businesses must report non-accessible e-commerce services to the ACM within one week or one month, depending on the impact. France also expects SMEs to declare non-conformities to the DGCCRF. Check each market you sell into.

How Germany's MLBF checks websites

Germany offers the most detailed public view of enforcement. The MLBF (Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen) moved into its offices in Magdeburg at the start of 2026, and its board adopted the market surveillance strategies on 29 January 2026 (MLBF news). Its services strategy (dated 8 January 2026) states:

  • Proactive checks without a trigger use automated pre-screening software for web services, so that many sites can be covered. Risk factors include reach and market share, company size, relevance for independent living, complexity, automated test results and public user feedback.
  • Reactive checks follow consumer and association requests under § 32 BFSG, third-party tips and companies' own reports, and take priority.
  • Companies with past failings or poor cooperation are monitored with higher priority.

The sequence follows § 29 BFSG: a request to fix within a deadline, a second request with the threat of prohibition, then an order to stop offering the service until conformity is proven. Missing accessibility information is a "formal non-conformity" (§ 30), the easiest finding for any inspector.

In Germany, competitors could in theory also pursue breaches via unfair competition law. Whether courts treat the BFSG as a market conduct rule had not been reliably settled as of November 2026.

Which standard applies: WCAG 2.1, WCAG 2.2 or EN 301 549?

The EAA uses a presumption of conformity: services that meet harmonised standards whose references are published in the Official Journal are presumed compliant.

  • Today: EN 301 549 V3.2.1 is the central technical reference. Clause 9 covers the web and incorporates WCAG 2.1 (in practice level AA). Clause 10 covers documents.
  • New: EN 301 549 V4.1.1 (2026-09) is the first edition prepared for Directive (EU) 2019/882. It aligns clauses 9 to 11 with WCAG 2.2 and adds an annex mapping its requirements to the EAA.
  • Legal status: According to AccessibleEU (7 September 2026), V4.1.1 only becomes the legal reference once the Commission cites it in the Official Journal; until then V3.2.1 (WCAG 2.1 AA) remains the reference. We could not confirm a citation as of 6 November 2026.

Our recommendation: audit existing sites against WCAG 2.1 AA and build new projects to WCAG 2.2 AA. According to the W3C, WCAG 2.2 adds nine success criteria. In practice the important ones are: focus must not be hidden behind sticky headers or cookie banners, targets need a minimum size, dragging needs an alternative, help must be consistently placed, users should not have to enter the same data twice, and login must not rely on a memory test.

What accessibility information must you publish?

Annex V requires service providers to describe, in their terms and conditions or an equivalent document, how the service meets the accessibility requirements. The description must cover a general description of the service in accessible formats, explanations needed to understand how it works, and how the Annex I requirements are met. Germany additionally requires naming the competent market surveillance authority (BFSG Annex 3). Our accessibility statement template covers the required elements.

The 25-point EAA website checklist

The WebAIM Million 2026 found detectable WCAG failures on 95.9% of the top one million home pages. The most common were low contrast text (83.9%), missing alt text (53.1%) and missing form labels (51%). Start with those.

Structure

  1. Page language is set in code (lang), and language changes within text are marked.
  2. Headings (H1 to H3) reflect the real structure, with no skipped levels used for styling.
  3. Landmarks (header, nav, main, footer) and a "skip to content" link exist.
  4. Page titles are unique and descriptive.
  5. Link text makes sense out of context, with no "click here" and no empty links or buttons.

Perceivable

  1. Text contrast is at least 4.5:1, or 3:1 for large text (WCAG 2.1, 1.4.3).
  2. Controls, focus indicators and input borders reach at least 3:1 against adjacent colours (1.4.11).
  3. Informative images have meaningful alt text; decorative images have empty alt.
  4. Information is never conveyed by colour alone, for example in required fields or stock status.
  5. The page works at 200% zoom and at 320 px width without horizontal scrolling.
  6. Videos have captions, and audio-only content has a transcript.

Operable

  1. Every function works by keyboard alone, with no keyboard traps.
  2. Focus is always visible and never hidden by sticky elements.
  3. Focus order follows reading order, including in menus, modals and sliders.
  4. Carousels and animations can be paused, and time limits can be extended.

Forms and processes

  1. Every field has a visible label that is programmatically linked.
  2. Error messages name the field and the fix and are announced to screen readers.
  3. Required fields and formats (dates, phone numbers) are explained up front.
  4. Login and sign-up avoid memory tests, and CAPTCHAs have an accessible alternative.
  5. Checkout from basket to confirmation, including payment methods, works with keyboard and screen reader.
  6. Booking flows (calendars, time slots) work without a mouse.

Third parties, documents, information

  1. The cookie banner is keyboard-reachable, does not trap focus and makes sense to screen readers.
  2. Chat widgets, embedded maps and booking plugins are tested or have an accessible alternative.
  3. New PDFs and office documents are accessible (tags, reading order, alt text) or offered as HTML.
  4. The accessibility information is reachable from every page and names the competent authority where required.

How to test properly

Method Examples Catches Misses
Automated testing axe DevTools, WAVE, Lighthouse, Pa11y Contrast, missing alt attributes and labels, empty links, missing language Whether alt text is meaningful, focus order, comprehension, broken processes
Expert manual review WCAG-based review, keyboard-only run Keyboard traps, invisible focus, illogical structure, form logic errors Real users' experience
Assistive technology NVDA, JAWS, VoiceOver, TalkBack, zoom Whether a checkout can actually be completed with a screen reader —

The W3C is explicit: evaluation tools "can not determine accessibility, they can only assist in doing so". A perfect Lighthouse score is not evidence of conformity. Because Germany's authority itself uses automated pre-screening, though, automatically detectable errors are the first thing to clear.

Why overlays do not make you compliant

Overlays are scripts that add a toolbar for font size, contrast modes or read-aloud, sometimes promising AI-based automatic repair. They fall short for three reasons:

  • The cause remains. Missing labels, wrong focus order or an unusable checkout live in your source code and content, and a layer on top does not reliably fix them. The Overlay Fact Sheet, signed by many accessibility practitioners, advises against relying on them.
  • Users bring their own tools. Screen readers, zoom and contrast settings are already on the user's device, and an extra toolbar can conflict with them.
  • The claims attract regulators. The US Federal Trade Commission alleged that accessiBe advertised its widget as able to make any website WCAG-compliant. The settlement required a $1,000,000 payment, according to the Federal Register of 6 January 2025.

Remediate or redesign?

Flat prices for "EAA compliance" are not credible, because effort depends on the starting point.

Factor Remediating the existing site Accessible redesign
Makes sense when … the codebase is sound and findings are mainly content, contrast and individual components the theme, page builder or shop system creates barriers at its core, or a redesign is due anyway
Effort drivers number of templates and custom components, forms, third-party widgets, legacy documents concept, design system, content migration, redirects
Duration weeks, often in prioritised stages months, depending on scope
Risk new barriers from updates and plugins; patchwork higher upfront cost; SEO risk during migration
Sustainability holds only with editorial guidelines and re-testing accessibility built into components from the start

An audit gives you the numbers for this decision. If you are rebuilding anyway, combine accessibility with our website redesign SEO checklist: clean semantics, alt text and clear structure help search engines and AI search systems just as they help screen readers.

Six-step plan

  1. Confirm scope for every market you sell into, using the decision tree and legal advice where needed.
  2. Audit the sample pages listed above and every purchase, booking and login flow, both automated and manual.
  3. Prioritise blockers in conversion flows first, then frequent errors, then cosmetic issues.
  4. Fix code, design and content, including third-party components such as consent banners and payment providers.
  5. Document by publishing the accessibility information and filing test results. If you rely on the disproportionate-burden exception (Article 14), document the assessment, renew it at least every five years and notify the authorities concerned.
  6. Keep it compliant by training editors and re-testing with every release; the obligation is ongoing.

While you are reviewing your shop, check the other 2026 consumer-law changes too, such as the new EU withdrawal button.

Conclusion: scope it, fix the flows, keep testing

The EAA does not cover every website, but it covers almost every shop, booking flow or online contract aimed at consumers once a company has ten or more employees or exceeds the turnover and balance-sheet thresholds. Enforcement is national and now active, at least in Germany, where the authority pre-screens automatically. The fastest risks to close are missing accessibility information and automatically detectable errors such as contrast, alt text and form labels. New builds should target WCAG 2.2 AA now.

We audit websites against WCAG and EN 301 549, remediate existing systems or build accessible sites from scratch, including the accessibility statement and editor training. See Accessible Websites for the scope. If a fresh start is more economical, accessibility is part of our website relaunch work. After the audit scoping you receive a fixed-price quote. Send us your URL for a no-obligation call.

This article is general information, not legal advice. Whether your service falls under national EAA legislation should be checked with a lawyer where in doubt.

Sources

All sources accessed 6 November 2026.

Frequently asked questions

Does the European Accessibility Act apply to my website?

It applies if your website or app lets consumers conclude a contract with you, for example an online shop, a booking flow or an online subscription, and you are not a microenterprise. Purely B2B sites and microenterprises providing services are outside the obligation. National transposition laws can differ in detail, so check the law of each country you sell into.

What counts as a microenterprise under the EAA?

An enterprise that employs fewer than 10 persons and has an annual turnover not exceeding €2 million or an annual balance sheet total not exceeding €2 million (Article 3 of Directive (EU) 2019/882). Microenterprises providing services are exempt from the accessibility requirements. The exemption does not cover products such as computers or e-readers.

What are the fines for an inaccessible website under the EAA?

The directive leaves penalties to the member states, so they differ. Germany allows fines of up to €100,000, Austria up to €80,000 (€50,000 for SMEs), Ireland up to €60,000 on conviction on indictment, and France applies fifth-class fines of €7,500 per legal person, cumulative per service and obligation. Authorities usually demand corrective action first.

Is an accessibility overlay or widget enough to comply?

No. Overlays add a script on top of the page but do not reliably fix missing form labels, broken keyboard flows or inaccessible PDFs. The requirements are met by correcting code and content against WCAG via EN 301 549, then testing manually and with assistive technology.

Is WCAG 2.2 now required under the EAA?

EN 301 549 V4.1.1, published in September 2026, aligns with WCAG 2.2. According to AccessibleEU it only becomes the legal reference once cited in the Official Journal of the EU. Until then WCAG 2.1 AA via EN 301 549 V3.2.1 remains the practical baseline, but new builds should already target WCAG 2.2 AA.