EMPIREYO
← Insights
Web designupdated 12 November 202617 min read

The European Accessibility Act: is your site ready?

Since 28 June 2025, most businesses that sell to consumers through a website or app must make that service accessible. Microenterprises are exempt. This article sets out what the law and the regulators in the Netherlands say.

In short

Since 28 June 2025, businesses that let consumers buy, book or sign up for something through a website or app must make that service accessible. In the Netherlands the rules are in the Dutch Civil Code, and the ACM supervises them. According to the ACM your site must meet WCAG 2.1 at level AA, and it recommends working with WCAG 2.2 now. Microenterprises are exempt.

Checked on 3 November 2026 against the sources listed at the end. This article sets out what the law and the regulators say about the rules in the Netherlands; it is general information, not legal advice.

What is the European Accessibility Act?

The European Accessibility Act (EAA) is a European directive from 2019, Directive (EU) 2019/882, which has applied since 28 June 2025. Its aim is to make the products and services people use every day, from webshops to banking apps, usable for everyone, including people with a visual, hearing, motor or cognitive impairment. How we build a shop with that in mind is on ecommerce website design.

Every member state had to transpose the directive into its own law, so the details differ from country to country. In the Netherlands this was done by the Implementation Act on accessibility requirements for products and services (Implementatiewet toegankelijkheidsvoorschriften producten en diensten, Bulletin of Acts and Decrees 2024, 87). For webshops and other e-commerce, the rules are in Book 6 of the Dutch Civil Code (Burgerlijk Wetboek, BW), articles 6:230fa to 6:230fd. This article covers those Dutch rules.

Does the law apply to your website?

The Dutch Civil Code describes e-commerce services as services provided at a distance, through websites and services on mobile devices, by electronic means and at the individual request of a consumer, with a view to concluding a contract. The Netherlands Authority for Consumers and Markets (ACM) gives webshops, booking platforms, ordering apps and subscriptions as examples, and writes that the rules also apply when consumers pay with their personal data. According to the ACM this covers every kind of website or app with an offer for consumers, even if that offer is only on part of the site.

Your situationWhat the sources say
Consumers buy, book or sign up for something through your website or appThat is e-commerce. The rules apply, with the ACM as the supervisor.
You have fewer than ten employees, and your annual turnover or balance sheet total does not exceed the limit in article 6:230fc(1) of the Dutch Civil CodeAccording to that article, the obligation does not apply to you.
You have ten or more employeesThe rules apply. Note: the ACM only names annual turnover as a limit; the law names annual turnover or balance sheet total.
You provide banking services or financial e-commerceSupervised by the Dutch Authority for the Financial Markets (AFM).
You provide e-books, or services that give access to audiovisual media servicesSupervised by the Dutch Media Authority (Commissariaat voor de Media).
You provide passenger transport by air, bus, rail or waterSupervised by the Human Environment and Transport Inspectorate (Inspectie Leefomgeving en Transport, ILT).
You make or sell products such as computers, routers or e-readersAccording to the ACM, the Dutch Authority for Digital Infrastructure (Rijksinspectie Digitale Infrastructuur, RDI) supervises these.
You are a government organisationGovernment websites have their own rules, which this article does not cover.

The rules in the Dutch Civil Code concern services to consumers: natural persons who use a service outside their business or profession. Whether you fall under the exemption depends on your number of employees and your financial figures, so that can change as you grow. According to the ACM you remain responsible for accessibility as the provider, even if you hire another company to build your website or app. If you are unsure whether your site is covered, read the ACM page or ask a lawyer.

What does the law require of your website?

Under article 6:230fb you design and provide the service in line with the accessibility requirements in the annexes to the directive. You draw up the required information, explain how your service meets the requirements, and make that information available in writing and orally, in a form that is also accessible to people with a disability.

The ACM translates that into practice:

  • The benchmark is WCAG 2.1 at level AA. The ACM writes that WCAG 2.2 level AA will become the new standard during 2026, and advises working with it now.
  • An accessibility statement that is easy to find and accessible itself. In it you describe how the service works, how it works with assistive technology and how you meet the rules. The statement must also be available orally, for example as an audio clip.
  • A helpdesk that can give information about accessibility.
  • No certificate or audit required. You have to comply, not hold a quality mark.

Ondernemersplein, the Dutch government's information portal for businesses, and the ACM name two extra rules for e-commerce: give information about the accessibility of what you sell, and make sure that signing digitally, logging in and paying are accessible. Under article 6:230fb you also put procedures in place so the service stays accessible.

How do you write a good accessibility statement?

The sources say what has to be in it; how you make it useful is up to you. What we recommend including:

  • Which guideline you follow and at what level, for example WCAG 2.2 AA.
  • How you test: yourself or with an outside party, with which tools and when you last did so.
  • What does not work well yet, named honestly, and when you will fix it.
  • How someone reports a problem, and how quickly you respond.
  • How the most important route works with assistive technology, such as a screen reader or a keyboard alone.
  • The date of the last review.

Put the statement in a fixed place, for example in the footer of every page, and make sure your helpdesk knows it exists.

WCAG itself rests on four principles. In practice that means, among other things:

  • Perceivable: enough colour contrast, text alternatives for images, captions for video.
  • Operable: everything works with a keyboard alone, focus is visible, no content that can only be reached with a mouse.
  • Understandable: clear labels on forms, error messages that explain exactly what is wrong, predictable navigation.
  • Robust: the code of the page is correct, so screen readers and other assistive technology can read it.

WCAG 2.1 or 2.2: which version applies?

Behind the WCAG requirement is a European standard, EN 301 549. According to Ireland's National Disability Authority (NDA), which worked on the new version, version 4.1.1 of that standard was published on 2 September 2026, based on WCAG 2.2 at level AA. The NDA writes that this version only applies legally once the European Commission references it in the Official Journal of the EU, expected on 16 December 2026, and that until then version 3.2.1 from 2021, based on WCAG 2.1, is the version that applies.

Article 6:230fd of the Dutch Civil Code says that a service is presumed to meet the requirements if it complies with harmonised standards for this directive that have been published in the Official Journal. According to the W3C, the requirements from WCAG 2.0 and 2.1 have stayed almost the same in WCAG 2.2, with one exception: success criterion 4.1.1 Parsing has been removed. WCAG 2.2 has been a W3C Recommendation since 5 October 2023 and adds six requirements at level A and AA:

RequirementLevelWhat it asksHow to test it yourself
2.4.11 Focus Not Obscured (Minimum)AAWhatever has keyboard focus stays at least partly visibleTab through the page: does the focus ever disappear behind a sticky bar or a cookie banner?
2.5.7 Dragging MovementsAAAnything you drag can also be done without dragging, by tapping or clickingSliders, maps, sortable lists: do they also work without dragging?
2.5.8 Target Size (Minimum)AAClick targets are at least 24 by 24 CSS pixels, or have enough space around themOn your phone, can you hit every button without touching the one next to it?
3.2.6 Consistent HelpAHelp that appears on several pages is always in the same orderAre phone, chat or contact always in the same order on the pages where they appear?
3.3.7 Redundant EntryAInformation you already gave in a process is filled in or can be selectedDoes your checkout ask for the same address twice?
3.3.8 Accessible Authentication (Minimum)AALogging in does not require a memory test or a puzzle without an alternativeCan you log in by pasting or with a password manager, without a puzzle?

How we build sites to these requirements and test them is described on our page about web accessibility.

What did the ACM find at webshops?

On 24 March 2026 the ACM published the results of tests at around 100 of the largest Dutch webshops and the websites of the largest telecom and energy providers. At 61 percent it was impossible to place an order using assistive technology. At 33 percent there were serious problems: ordering was possible, but took considerably more effort. As examples the ACM mentions an order button that does not work with the keyboard, and an inaccessible puzzle that checks whether you are human (a CAPTCHA).

The ACM points the largest companies that perform worst to the issues they need to fix, and companies that do not improve enough risk enforcement. In research commissioned by the ACM, companies often cited a lack of time, money and technical knowledge, and uncertainty about their obligations.

What exceptions and transitional rules are there?

  • No transition period for the service itself. According to the ACM, the rules for services have applied since 28 June 2025.
  • Older content. According to the ACM, you do not have to adapt videos, audio recordings and documents you published before 28 June 2025; what you publish from that date must be accessible. Archives you no longer update after that date, and third-party content you did not commission, did not pay for and do not manage, are also excluded. For a map, an accessible description of the route is enough.
  • Existing contracts. Service contracts concluded through an e-commerce service before 28 June 2025 may continue unchanged until they expire, but no longer than five years after that date (article 190aa(3) of the Transitional Act for the new Civil Code, Overgangswet nieuw Burgerlijk Wetboek).
  • Products supplied with your service. If you supply a product with your service, such as a modem with an internet subscription, the ACM says you do not have to replace it straight away if it does not yet meet the rules; that can wait until 28 June 2030.
  • Fundamental alteration or disproportionate burden. A requirement does not apply to the extent that meeting it would fundamentally alter the service or impose a disproportionate burden (article 6:230fc(2)). You must still meet as many of the rules as you can. According to the ACM, a lack of time or knowledge does not count, and a business that receives outside funding to become more accessible cannot claim a disproportionate burden. You record your assessment in a document; the ACM can ask to see it.
  • Reassessing. If you claim a disproportionate burden, article 8a.1 of the Consumer Protection Enforcement Act (Wet handhaving consumentenbescherming) requires a new assessment at least once every five years, and also when your service changes or the ACM asks for one. You keep the results for five years.

What if your site does not comply?

According to the ACM, you report a problem with a critical or serious impact within a week, and a problem with a moderate or minor impact within a month. If you solve it within that period, you do not have to report it. In a report you state which parts are not accessible and how serious the problem is, and you include a plan to make the service accessible. If you rely on an exception, you report that too. If you operate in several EU countries, you report to each regulator.

Consumers can file complaints, and the ACM also selects sites to investigate on its own initiative. How the ACM acts depends on the scale of the problems and on the steps a company takes. The ACM does not mention the amount of any fines on that page.

There is more to this than enforcement. An inaccessible site shuts out some of your visitors. The ACM also writes that an accessible website or app improves the experience for everyone. Many requirements, such as a clear structure, good contrast and logical headings, make a site clearer for every visitor.

Where do you start?

Start with an honest baseline, not a tool. Can you operate your site entirely with the keyboard? Is the heading structure right? Do images have meaningful alternative text? Are forms labelled? Only then automate. A sequence that works:

  1. Choose your most important routes. For a webshop: find a product, add it to the basket, check out. For a booking site: choose a date, fill in your details, confirm.
  2. Do the self-test below on those routes, on a computer and on a phone.
  3. Run an automated check alongside it, such as the free testing tool axe-core. It finds many technical errors, but not whether a text is understandable or an order is logical.
  4. Fix problems at the source. In the design and the code itself, so it stays right as new pages are added.
  5. Write your accessibility statement, with what works and what does not yet, and when you will fix it.
  6. Keep it up. Every new feature, campaign or page can break something. Make the check part of your regular maintenance.

How do you test your own site?

A full audit takes more, but with these checks you will find the biggest problems yourself. Take your most important route: from the homepage to an order, a booking or a request.

TestHowGood if
KeyboardPut the mouse aside and go through your whole route with Tab and EnterYou reach everything, including the order button, and never get stuck
Visible focusWatch where you are with every TabYou always see a clear outline or highlight, not hidden behind a bar
ContrastCheck text and buttons with a contrast checkerAt least 4.5 to 1 for normal text, 3 to 1 for large text
FormsClick the text next to a field and submit an empty formEvery field has a label, and the error message says what is wrong
ImagesLook at the descriptive text (alt text) of images that carry informationThe text says what the image shows; decoration has no description
HeadingsLook at how the headings on a page are structuredThe main title is at the top and the headings follow each other logically
ZoomZoom in the browser until the text is twice as largeEverything stays readable and usable, without scrolling sideways for normal text
Logging in and payingTry to log in and check out with the keyboardNo puzzle without an alternative, and pasting into the password field works
StatementLook for your accessibility statement, starting from the homepageFound within a few clicks, and honest about what is not right yet

Record what you find. An accessibility statement that describes where you stand is more honest and more credible than one that claims everything passes. The ACM has a page with common problems and possible solutions (in Dutch), and a UX audit also covers the accessibility of your most important routes.

When this does not apply

This article covers the Dutch rules for e-commerce aimed at consumers. Other member states have their own national law and regulators. If you operate in several EU countries, the ACM says you report to the regulator in each country. Government websites, banking services, e-books, passenger transport and physical products have different or additional rules, which are not worked out here.

What we don't know: whether your business falls under the exemption for microenterprises, whether a claim of disproportionate burden would succeed in your case, and whether the new version of EN 301 549 will actually appear in the Official Journal on 16 December 2026; that is an expectation of the NDA. This is general information, not legal advice. If in doubt, ask a lawyer or read the ACM pages.

Frequently asked questions

Does the European Accessibility Act also apply to small businesses?+
Not to microenterprises. According to article 6:230fc of the Dutch Civil Code, the obligation does not apply to businesses with fewer than ten employees and an annual turnover or balance sheet total not exceeding the limit in that article. The ACM puts it the other way round: the rules apply if you employ ten or more people or have an annual turnover above that limit.
Does my website have to meet WCAG 2.2?+
The ACM names WCAG 2.1 at level AA as the requirement and advises working with WCAG 2.2 now. A new version of the European standard, based on WCAG 2.2, was published on 2 September 2026 and, according to Ireland's NDA, applies once the European Commission references it in the Official Journal.
What goes in an accessibility statement?+
According to the ACM, you describe how the service works, how it works with assistive technology and how you meet the rules. The statement is easy to find, accessible itself and also available orally, for example as an audio clip.
Who enforces the accessibility rules in the Netherlands?+
The ACM for e-commerce and electronic communications services, the AFM for banking services and financial e-commerce, the Dutch Media Authority for e-books and services that give access to audiovisual media, and the ILT for passenger transport. For products the ACM names the RDI, and for the emergency number 112 the Inspectorate of Justice and Security.
Do I need an audit or a certificate?+
No. According to the ACM, a certificate or audit is not mandatory. You do have to meet the requirements and have an accessibility statement.

Want to know where you stand? Let us walk through your most important route with you. More on our page about web accessibility. You work directly with Nawid, with a fixed team of five specialists.

Sources

Consulted on 3 November 2026.

NR
Nawid RasaFounder of Empireyo · in design, development & strategy since 2014

Also worth reading: The UX mistakes that cost you customers in 2026.

Written with the help of AI, reviewed and edited by Nawid Rasa, who is responsible for the content. Sources are listed below the article. Spotted an error? Email hi@empireyo.com.

Want to know where your site stands?

We review your site on exactly the points the law covers (structure, contrast, operation and forms) and tell you honestly what's solid and what isn't. Findings with a source, no scaremongering.

What do you have in mind?
What budget do you have in mind?
When do you want to launch?
Almost there. How do we reach you?
Request sent.

Your request has reached us. You will usually hear back within two working days. Prefer direct contact? Email hi@empireyo.com or message us on WhatsApp with the chat button at the bottom right.

Reply within two working days · No obligation · privacy