European Accessibility Act: what your website needs.
Since 28 June 2025, the European Accessibility Act has required websites and apps that sell to consumers in the EU to be perceivable, operable, understandable and robust for people with disabilities, and the business has to publish how its service meets those rules. Micro-enterprises that provide services are exempt, and in practice a site is checked against WCAG. Below are the facts quoted from Directive (EU) 2019/882, then my offer: a technical readiness review with fixes, the 14-day Trial, $995, one time. None of this is legal advice.
By Badii Boutar · Updated
Illustration: a pair of round glasses.
- Applies from 28 June 2025
- Covers e-commerce and other consumer services
- Micro-enterprises providing services are exempt
European Accessibility Act
What the law says.
Quoted from the directive on EUR-Lex. The law that applies to you is your country’s version of it. Check that text, or ask a lawyer.
- 01
When it applies
Member States had to adopt their laws by 28 June 2022 and “apply those measures from 28 June 2025” (Article 31). Service contracts agreed before 28 June 2025 may continue unchanged until they expire, for at most five years (Article 32).
- 02
Which services
Services provided to consumers: electronic communications, access to audiovisual media, parts of passenger transport such as websites, apps and e-tickets, consumer banking, e-books, and e-commerce (Article 2(2)).
- 03
What counts as e-commerce
“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(30)). In plain words: an online shop that sells to consumers.
- 04
The micro-enterprise exemption
“Microenterprises providing services shall be exempt from complying with the accessibility requirements” (Article 4(5)). A microenterprise employs fewer than 10 persons and has an annual turnover or balance sheet total of at most €2 million (Article 3(23)).
- 05
What the website must do
The directive does not name WCAG. It asks for websites and apps made accessible “by making them perceivable, operable, understandable and robust” (Annex I, Section III, point (c)). Those are the four principles WCAG is built on. EN 301 549, the European standard for accessible ICT, takes its web requirements from WCAG: version 3.2.1 from WCAG 2.1 AA, and version 4.1.1, published in September 2026, from WCAG 2.2. That is why reviews use WCAG as the checklist.
- 06
Extra rules for online shops
For e-commerce the directive adds two things: accessibility information about the products sold, when the maker provides it, and identification, security and payment steps that are “perceivable, operable, understandable and robust” (Annex I, Section IV, point (g)). In plain words: the login and the checkout have to work for everyone, not only the product pages.
- 07
What you must publish
Information on how your service meets the requirements, in your general terms and conditions or an equivalent document, in an accessible format, kept for as long as the service runs (Article 13(2) and Annex V).
- 08
The other exceptions
The rules apply only as far as they do not fundamentally change the service or put a disproportionate burden on the business. That has to be assessed and documented, and the records kept for five years (Article 14). Some content is out of scope, such as pre-recorded video and office files published before 28 June 2025 (Article 2(4)).
- 09
Fines, country by country
The directive leaves penalties to each country, which must be “effective, proportionate and dissuasive” (Article 30). Germany: up to €100,000, including for offering a service that does not comply (BFSG § 37). Ireland: on indictment, a fine up to €60,000, up to 18 months in prison, or both (S.I. 636/2023, Regulation 32). Spain: breaches go to sector law first, otherwise to the general disability law, with fines from €301 up to €1,000,000 (Law 11/2023, Article 30, and Royal Legislative Decree 1/2013, Article 83).
Process
How it works.
- 01
30 min
Scope call
What you sell, to whom, and which pages carry the buying flow. Whether you are in scope is a legal question, so settle it with a lawyer before you buy.
- 02
Days 1 to 4
Review
The key pages or templates of your site against WCAG 2.2 AA, with keyboard, screen reader and axe checks.
- 03
Day 5
Statement and plan
A draft accessibility statement based on what the review found, and a fix plan in priority order. The statement describes the site as it is that day, gaps included.
- 04
Until day 14
Fixes
I fix what can be fixed in the 14 days and walk you through the plan for the rest. That work goes on a monthly plan, one task at a time, or to your team.
Proof
From my work.
On one client’s web app, I built the accessibility work myself: keyboard support, screen reader labels, colour contrast, the mobile layout, and text that follows the text size people set on their device, so the app still works when someone reads at a bigger or smaller size.
When not to hire me for this
- You need to know whether the law applies to your business. That is a legal question. Ask a lawyer first.
- You are a micro-enterprise that provides services. The directive exempts you from the accessibility requirements (Article 4(5)), though an accessible shop still sells to more people.
- You want a certificate. I review and fix. I do not certify compliance.
Price · USD
Price.
- 01
14-day Trial
I audit one app, codebase, site, store or cloud account, then fix what can be fixed in the 14 days.
Fee credited to your first month if you start a monthly plan within 14 days of the Trial ending.
- Findings ranked by risk, in the first 5 business days
- Fixes for what fits in the 14 days, at the Limited pace
- A written plan for the rest, and 1 walkthrough call
$995
14 days, one time
Start · $995Secure checkout via Stripe · Refund policy
- Monthly plans are billed from the day you start. Pause or cancel anytime before the next billing date.
- One task is a piece of work that fits in 1 to 5 working days. I size tasks and split bigger ones.
- Your queue is unlimited and you set the order. I work through it one task at a time.
- Messages are answered the same working day, Monday to Friday. All code and accounts stay yours.
- Not included: 24/7 emergency support, and your own tool bills (hosting, APIs, payment fees).
- The 14-day Trial is paid upfront and runs at the Limited pace. Fee credited to your first month if you start a monthly plan within 14 days of the Trial ending.
- The Trial does not renew. If you do not start a plan, it ends on day 14 and nothing else is charged.
- Prices exclude VAT. EU businesses with a valid VAT number pay no VAT on the invoice (reverse charge). Invoices come from Pan African Center for Entrepreneurship in the Netherlands.
- Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.
- All three prices, and what each plan covers
Market
Where my price sits.
Published prices, November 2026.
- Typical accessibility audit in the US: $1,250 to $2,750, or $100 to $250 per main page or screen. Source: Accessible.org (US), 17 Nov 2026
- Accessibility audit €600 to €1,200 in 1 to 2 weeks. Fixing the barriers from €1,500, online shops from €4,000. Source: Kopf & Stift (Germany), undated, seen Nov 2026
- A legal BFSG check of a website by a partner law firm: from €1,240 plus VAT. Source: eRecht24 (Germany), seen Nov 2026
My review is technical, not legal, and it includes the statement draft and the fix plan. At $995 it sits inside the German audit range, under the US one, and under the starting price of a legal check. They do different jobs, and some businesses need both. I sell this, so read it with that in mind.
FAQ
Questions.
Illustration: a statue of a seated man, deep in thought.
01 Does the EAA require WCAG 2.2?
The directive itself does not name a WCAG version. It sets the four principles and lets standards fill in the detail. EN 301 549, the European standard used for this, pointed to WCAG 2.1 AA for web content in version 3.2.1. Version 4.1.1, published in September 2026, is aligned with WCAG 2.2. I review against WCAG 2.2 AA because it is the current W3C version and includes every 2.1 criterion except 4.1.1 Parsing, which the W3C removed as obsolete.
02 Do I need an accessibility statement?
The EAA asks service providers to publish how their service meets the requirements (Annex V). A clear statement page is a practical way to do it. The guide below shows what goes in one.
03 Is this legal advice?
No. I quote the official texts and link them, and I review and fix your site. For what the law requires of your business, ask a lawyer in your country.
Related
Read next
Start
Tell me where the product is stuck.
In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.
Or email badii@badii.studio
How the call goes
- 01You tell me about the product, the team and the next 6 months.
- 02I ask about the code, the stack and what keeps breaking.
- 03We pick the option that fits, or agree that none does.
09:00 to 20:00 CET
Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.