01 / Guides
The Accessibility Act in one minute
The European Accessibility Act (EAA) sets common accessibility requirements for certain products, such as computers, smartphones, payment terminals and e-readers, and certain services. For website owners the key category is e-commerce services in Article 2(2)(f): services provided at a distance, through websites and mobile apps, by electronic means and at the request of a consumer with a view to concluding a consumer contract.
Because it is a directive, each member state wrote its own law. Germany uses the Barrierefreiheitsstärkungsgesetz (BFSG), Portugal the Decreto-Lei n.º 82/2022, and so on. The core rules are the same everywhere; enforcement bodies and fines differ. If consumers can buy, book or subscribe on your site, that journey has to be accessible.
02 / Guides
Does it apply to me? A quick check
This covers the most common situations for small and mid-sized businesses. Record your reasoning for borderline cases and get legal advice if in doubt.
| Situation | Covered? | Why |
|---|---|---|
| Online shop selling to consumers, 15 employees | Yes | E-commerce service for consumers, not a microenterprise |
| Online shop selling to consumers, 4 employees, €800,000 turnover | No (exempt) | Microenterprises providing services are exempt under Article 4(5) |
| Hotel or holiday rental with direct online booking, 12 employees | Yes | The booking is a consumer contract concluded through the website |
| Brochure website with a contact form only | Usually not | No consumer contract is concluded online; accessibility is still good practice |
| B2B shop for verified trade customers only | Usually not | The EAA protects consumers; the exclusion of consumers has to work in practice |
| Shop selling to businesses and consumers | Yes | As soon as consumers can order, the journey they use is covered |
| Business outside the EU selling online to EU consumers | Yes, unless a microenterprise | The rules apply to services offered on the EU market, wherever the business is based |
03 / Guides
The microenterprise exemption
Article 3(23) defines a microenterprise as 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. Both conditions must be met together.
Article 4(5) exempts microenterprises providing services from the accessibility requirements and the related obligations. A small online shop selling clothes or furniture counts as a service provider for its website. There is no general exemption for microenterprises that manufacture products covered by the Act.
Building accessibly still pays off. A growing business loses the exemption, fixing a site later costs more than doing it right the first time, and roughly one in four adults in the EU lives with some form of disability. Every barrier in a checkout is a lost order.
04 / Guides
Deadlines, transition rules and excluded content
There is no general grace period for shops that existed before 28 June 2025. The transitional rules in Article 32 are narrow:
- Service contracts agreed before 28 June 2025 may continue unchanged until they expire, but no longer than 28 June 2030.
- Products a service provider already used lawfully before 28 June 2025 may keep being used until 28 June 2030.
- Article 2(4) excludes some website content: pre-recorded video and audio and office files (for example PDF catalogues) published before 28 June 2025, online maps where essential information is provided accessibly, third-party content you neither fund nor control, and archived content that is no longer updated.
- Anything you publish after that date, including product videos, PDFs and new pages, has to be accessible.
05 / Guides
What a website or online shop has to meet
The Act describes functional requirements in Annex I and gives a presumption of conformity to harmonised standards. For websites that means EN 301 549, which includes WCAG 2.1 level AA. In everyday terms:
| Area | What is required | Typical failures in shops |
|---|---|---|
| Perceivable | Text alternatives for images, captions for video, contrast of at least 4.5:1 for normal text | Light grey prices on white, product photos without alt text, text baked into banners |
| Operable | Everything works by keyboard, visible focus, no time limits without extension, usable at 200 % zoom | Mouse-only mega menus, cookie banners that trap or skip focus, carousels that never stop |
| Understandable | Labelled form fields, clear error messages with a fix, page language set | Placeholder instead of label, “Invalid input” with no explanation |
| Robust | Valid HTML, correct roles and states for screen readers | Buttons built from divs, size and colour selectors that screen readers do not announce |
| E-commerce (Annex I, Section IV) | Accessible identification, security and payment functions; accessibility information about the products sold when the manufacturer provides it | CAPTCHA with no alternative, payment pop-ups without focus management, swipe-only login |
06 / Guides
WCAG 2.1 AA, EN 301 549 and what changed in 2026
Until now the reference for websites was EN 301 549 version 3.2.1 with WCAG 2.1 AA. EN 301 549 V4.1.1 was published on 2 September 2026. It adopts WCAG 2.2 AA and is written for the Accessibility Act. It only carries a presumption of conformity once the European Commission cites it in the Official Journal, which is expected around the end of 2026.
Our advice: if you build or rebuild now, aim for WCAG 2.2 AA straight away. The six new criteria, such as minimum target sizes, alternatives to dragging and login without cognitive tests, add very little effort to a new project.
07 / Guides
The accessibility statement: what Annex V requires
Service providers must publish information on how their service meets the accessibility requirements, as set out in Annex V. It can sit in the general terms and conditions or an equivalent document, has to be accessible itself and must stay available for as long as the service is offered. Most businesses use a dedicated page linked in the footer.
It should include, where applicable: a general description of the service in accessible formats, the descriptions and explanations needed to understand how the service operates, and a description of how the service meets the relevant accessibility requirements. National laws add details: Germany, for example, requires the competent market surveillance authority to be named. Add a contact route for reporting barriers.
A statement does not replace an accessible site. Claiming “fully compliant” without testing makes you more exposed, not less. An honest statement says what is met, what is not yet met and when it will be fixed.
08 / Guides
Seven steps to an EAA-ready website
- 01
Check whether you are covered, and write it down
Record headcount, turnover, balance sheet total and audience (B2C, B2B or mixed). If you rely on the microenterprise exemption, keep the figures with a date and review them every year.
- 02
Run automated tests
Run Lighthouse in Chrome, WAVE or axe DevTools on the home page, a category, a product page, cart, checkout and contact. Automated tools catch only part of the problems, but most contrast, alt text and label errors.
- 03
Test by hand
Complete a purchase using only the keyboard (Tab, Shift+Tab, Enter, Space). Then use a screen reader (NVDA on Windows, VoiceOver on Mac and iPhone) and check 200 % and 400 % zoom.
- 04
Fix what blocks a purchase first
Variant selectors, cart, forms, payment, login and cookie banner come first. A blog post with weak contrast is annoying; a checkout that cannot be used by keyboard is a dead end.
- 05
Fix it in the code, not with an overlay
Errors belong in the theme, the templates and the components. That way the fix applies to every page, including future ones.
- 06
Publish the statement
Annex V information on its own page, linked in the footer, with a contact route for reporting barriers and any details your national law adds.
- 07
Keep it compliant
Service providers must have procedures so the service stays compliant (Article 13). Set content rules for alt text and headings, test after every theme or plugin update and book a recurring review.
09 / Guides
Overlays and accessibility widgets: why a plugin is not enough
Scripts that add a menu with font size, contrast mode and read-aloud promise compliance with one line of code. They do not fix missing labels in a checkout or a variant picker that cannot be reached by keyboard. Many screen reader users already have better-configured tools and experience overlays as an extra barrier.
A widget can be a small extra, but it does not replace accessible code. If an authority audits your shop, an overlay will not count as conformity.
10 / Guides
Enforcement and penalties differ by country
Article 30 leaves penalties to the member states; they must be effective, proportionate and dissuasive. Two examples from the markets we work in:
| Country | Law and authority for online shops | Maximum fines (companies) |
|---|---|---|
| Germany | BFSG; joint market surveillance body of the federal states (MLBF), Magdeburg | Up to €100,000 for offering a non-accessible service, up to €10,000 for other breaches; competitors have also sent warning letters (Abmahnungen), whose legal basis is disputed |
| Portugal | Decreto-Lei n.º 82/2022; ANACOM for e-commerce services | €12,000 to €24,000 for serious breaches (e.g. no Annex information), €24,000 to €44,891.81 for very serious ones (e.g. a non-accessible service); convictions are published in two national newspapers |
| All EU countries | National market surveillance or consumer authorities | Before a fine, authorities normally order corrective action with a deadline; as a last resort they can stop the service |
11 / Guides
Disproportionate burden is not a way out
Article 14 lets businesses skip requirements that would fundamentally alter the service or impose a disproportionate burden. Anyone relying on it must document the assessment using the criteria in Annex VI, keep it for five years, inform the authority and repeat the assessment at least every five years or whenever the service changes.
If you received outside funding to improve accessibility, you cannot claim a disproportionate burden. For a normal online shop the argument rarely holds: an accessible checkout is state of the art, not a special project.
13 / Guides
What it costs and what drives the effort
Effort depends less on the number of pages than on the number of templates. A shop with 2,000 products often has a single product template: fix it once and all 2,000 pages are fixed. Costs rise with many different plugins, a bought theme with weak code or a third-party checkout.
On Shopify the checkout is built and maintained by Shopify; most issues sit in the theme and apps. On WooCommerce and custom systems the whole journey is yours. If a redesign is coming anyway, make accessibility a requirement rather than a retrofit. Our article on what an online shop costs covers the running costs.
14 / Guides
Note
This guide summarises the law as we understand it in November 2026 and is not legal advice. For your specific case, speak to a lawyer in the country you sell to; for the technical side, we can help.
FAQ
Common questions
01Does the European Accessibility Act apply to small businesses?
Yes, unless the business is a microenterprise: fewer than 10 employees and either turnover or balance sheet total of no more than €2 million. Microenterprises providing services are exempt under Article 4(5).
02When did the European Accessibility Act take effect?
Member states had to apply their national rules from 28 June 2025. Service contracts agreed before that date may run until they expire, but no later than 28 June 2030.
03Does the EAA apply to businesses outside the EU?
Yes. It applies to e-commerce services offered to consumers in the EU, wherever the business is based. A UK or US shop selling to customers in Germany or Portugal is covered unless it qualifies as a microenterprise.
04Does a website without a shop need to comply?
Under the EAA, usually not, as long as no consumer contract is concluded through the site. Once you take bookings, orders or paid sign-ups online, the journey is covered.
05Which standard do I need to meet?
In practice WCAG 2.1 level AA via EN 301 549. The new EN 301 549 V4.1.1, published in September 2026, moves to WCAG 2.2 AA, so new builds should target 2.2 AA.
06Is an accessibility overlay enough?
No. Overlays change the presentation but do not fix missing labels, focus traps or inaccessible checkout steps. Compliance comes from the theme and the code.