The European Accessibility Act (EAA) has applied since 28 June 2025. If you run a small webshop, booking site or app for EU customers, you may have heard it affects you. Below is what the directive itself says about scope, the exemption for very small businesses and the dates, followed by a 30-minute check you can do yourself. It is a technical guide, not legal advice. Your national authority or a lawyer can tell you how it applies to your company.
Short answer: the EAA covers e-commerce services offered to consumers. Businesses with fewer than 10 people and a turnover or balance sheet of at most €2 million are exempt for services. Everyone else selling to consumers online should make sure keyboard, screen reader and low-vision users can browse, order and pay.
1. What the directive covers
Directive (EU) 2019/882 lists what is in scope in Article 2. For services, it names electronic communications, access to audiovisual media, parts of air, bus, rail and waterborne passenger transport (websites, apps and e-ticketing), consumer banking, e-books and e-commerce services. The European Commission's EAA page gives the same overview.
For a webshop or booking site, the relevant part is the definition in Article 3: e-commerce services are "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". Two things follow:
- Consumers. The directive applies to services provided to consumers, meaning people buying outside their trade or profession. A tool sold only to businesses does not fit this definition.
- A contract is concluded. A webshop, a paid booking flow or an app where users buy something fits. A brochure site with no ordering does not match the definition. If unsure, ask.
The Dutch government's page for entrepreneurs uses the same reading: an e-commerce service is a website or app where you offer a product or service to consumers.
2. The exemption for very small businesses
Article 4(5) says: "Microenterprises providing services shall be exempt from complying with the accessibility requirements referred to in paragraph 3 of this Article and any obligations relating to the compliance with those requirements."
Article 3 defines a microenterprise as "an enterprise which employs fewer than 10 persons and which has an annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million". So you need both: fewer than 10 people, and either turnover or balance sheet at or under €2 million.
- The exemption is for services, as the article is written for microenterprises providing services.
- Dutch sources describe the size limit in slightly different words. The Rijksoverheid page says small businesses with fewer than 10 employees and a turnover of at most €2 million are not required to comply, while the ACM page speaks of "10 or more employees" and/or a turnover above €2 million. When your numbers are close to a limit, read the directive and the Dutch law, or ask.
3. Dates and transition rules
Member States had to adopt the rules by 28 June 2022 and apply them from 28 June 2025 (Article 31). Article 2(2) applies the directive to services provided to consumers after that date. Article 32 adds transition rules: service contracts agreed before 28 June 2025 may continue without alteration until they expire, but no longer than five years. Service providers may keep using products they lawfully used before that date until 28 June 2030. A webshop you build or redesign today should simply meet the requirements.
There are also limits. Article 14 says the requirements apply only as far as they do not fundamentally alter the service or impose a disproportionate burden. You must assess and document that, and report it to the authority.
4. What "accessible" means in practice
The directive's requirements in Annex I are general. The Annex examples for websites include text descriptions of pictures, all functionality available from a keyboard, enough time to read, predictable behaviour and compatibility with assistive technologies. It lists no technical tests.
The technical reference is the European standard EN 301 549, whose web part is built on WCAG (the Web Content Accessibility Guidelines). Under Article 15, products and services that conform to a harmonised standard whose reference is published in the Official Journal are presumed to meet the requirements. I could not confirm from official sources which version of the standard has that status for the EAA today. The older version, 3.2.1, is built on WCAG 2.1, and the newer 4.1.1 from ETSI is aligned with WCAG 2.2. It states that the presumption applies once it is cited in the Official Journal. In practice, aiming for WCAG 2.2 level AA is a sensible target, but it is a yardstick, not a legal guarantee.
5. Who enforces it
Enforcement is national. Article 30 leaves penalties to each Member State and requires them to be "effective, proportionate and dissuasive". In the Netherlands, the ACM checks webshops and communication services; the Commissariaat voor de Media covers e-books and audiovisual services. The Rijksoverheid page says the supervisor can give a warning or impose a fine, and does not state amounts. ACM says that in the first period it focuses mainly on critical problems. Elsewhere, look up your own country's authority.
6. The 30-minute self-check
These steps follow the W3C's easy checks. Test the home page, a product page, the cart, sign-in and payment.
- Keyboard only (5 min). Unplug the mouse and use Tab, Shift+Tab, Enter and Space. Can you reach every link, menu and button, add to cart and pay? Can you leave every popup?
- Visible focus (2 min). You should always see where you are on the page. CSS resets often remove the outline.
- Alt text (3 min). Product and informative images need a text alternative that says what the image is for. Decorative images should have an empty alt. A tool can tell you that alt text is missing, but not whether it is any good.
- Form labels and errors (5 min). Every field needs a real label, not only placeholder text. Submit the checkout empty and read the errors: they should say what is wrong and be easy to find.
- Colour contrast (3 min). The W3C gives 4.5:1 as the minimum for normal-size text. Check grey text and text on photos.
- Zoom to 200% (3 min). Zoom the browser and check on a phone. Nothing should be cut off or overlap, and the checkout must still work.
- Video (2 min). Videos need captions, and controls that work with a keyboard.
- Run a tool (5 min). The Lighthouse accessibility audit is built into Chrome DevTools. WAVE and the axe DevTools extension also flag many common errors. They find some problems, not all, so they come after the manual checks, not instead of them. The W3C warns that a page can pass quick checks and still have significant barriers.
7. Tell customers how you meet the requirements
Article 13 requires service providers to prepare information on how their service meets the requirements and to make it public. Annex V says this information goes in the general terms and conditions or an equivalent document. It should give a general description of the service and a description of how the relevant accessibility requirements are met. Write it only after you have checked the site, and keep it honest and short.
If you find a service that does not meet the requirements, Article 13(4) says you must take corrective measures and tell the competent national authority.
Not legal advice
This post explains the directive's text as I read it on 10 November 2026. Whether the law applies to your company, and how your country has written it into national law, depends on your size, your activity and your country. Check with your national authority or a lawyer. For the data-protection side of the same kind of site, see the GDPR checklist for a small app. For a wider pre-launch review, see the launch-ready checklist for AI-built apps.
Want this checked on your site?
I run the technical side of this check on webshops, booking sites and apps, whatever they are built with: keyboard paths, focus, labels, errors, contrast and the checkout. I then fix what fails. Send me the details on the hire page and I'll reply within 24 hours.