Nederland · EAA-nalevingsgids

EAA in the Netherlands — Implementatiewet toegankelijkheid

The Netherlands transposed the European Accessibility Act through the Implementatiewet toegankelijkheidsvoorschriften producten en diensten (Implementation Act for accessibility requirements of products and services), entering into force on 28 June 2025. Market surveillance sits primarily with the Autoriteit Consument & Markt (ACM) for most consumer services, with sector authorities (DNB, AFM, RDI) covering banking, financial services, and telecoms respectively. Penalties via the ACM's general enforcement powers reach up to €900,000 per breach or 1% of annual turnover, whichever is higher.

Legal framework

The Dutch legal stack:

  • Tijdelijk besluit digitale toegankelijkheid overheid (2018) — transposed Directive 2016/2102 for public-sector bodies; requires conformance with EN 301 549 and published toegankelijkheidsverklaring.
  • Implementatiewet toegankelijkheidsvoorschriften producten en diensten (2024) — transposes EAA to the private sector, effective 28 June 2025.
  • EN 301 549 v3.2.1 — the harmonised technical standard; embeds WCAG 2.1 Level AA for web content.
  • Wet handhaving consumentenbescherming (Whc) — the consumer-protection enforcement act that ACM uses to impose fines.

The Dutch government-sector registry Dashboard Digitoegankelijk (dashboard.digitoegankelijk.nl) publishes status per public-sector site. Private-sector operators are not required to register there, but the Dashboard is useful to study what a conformant toegankelijkheidsverklaring looks like in practice.

Who it applies to

In-scope services for consumers in the Netherlands:

  • E-commerce, online marketplaces, booking platforms.
  • Consumer-facing banking and financial services (payment accounts, credit).
  • E-books, e-readers, and associated software.
  • Consumer-facing electronic communications (messaging, VoIP, 112 emergency calling).
  • Passenger transport ticketing, real-time information, check-in services.
  • Consumer hardware terminals (ATMs, ticket machines, check-in kiosks) and their operating systems.

Microenterprise exemption per Article 4(5) EAA as transposed: fewer than 10 employees and annual turnover / balance sheet under €2M, providing services. Product manufacturers are not exempt regardless of size.

Scope is determined by where consumers are served, not by where the company is registered. A non-Dutch operator selling to Dutch consumers falls within ACM's reach.

Technical requirements — EN 301 549

The Dutch transposition references EN 301 549 v3.2.1 directly. For web content, WCAG 2.1 Level AA is the de facto conformance target. The key technical expectations:

  • Perceivable — alt text, captions for prerecorded video, 4.5:1 body contrast, 3:1 for large text.
  • Operable — full keyboard operability, no flashing above 3 Hz, visible focus indicator.
  • Understandable — <html lang="nl">, predictable navigation, explicit form labels and error messaging in Dutch (or the user's selected language).
  • Robust — valid HTML, ARIA used consistently with DOM semantics.

Note: the government sector is already piloting WCAG 2.2 Level AA via updates to the Besluit digitale toegankelijkheid overheid. Private-sector operators should expect WCAG 2.2 AA to become the reference target within the next harmonised-standard update.

Penalties and enforcement

  • ACM administrative fines up to €900,000 per breach or 1% of annual turnover, whichever is higher.
  • Last bod (periodic penalty payments) per day of continued non-compliance until remediation.
  • Public naming via ACM's decision database (acm.nl/nl/publicaties) — reputational cost is significant for consumer brands.
  • Sector regulators apply their own fining regimes — DNB / AFM for banking and investment services can exceed ACM ceilings by multiples.
  • Consumer / disability-organisation complaints — Ieder(in), the Oogvereniging, and similar DPOshave established escalation pathways to the ACM.

ACM enforcement historically escalates: informal contact → formal warning → last-onder-dwangsom → fine. Early remediation signalled through a credible toegankelijkheidsverklaring + CI scan evidence usually stops escalation at the warning stage.

Toegankelijkheidsverklaring — the statement

The Dutch accessibility statement (toegankelijkheidsverklaring) is expected to follow the template established for the government sector — which in turn follows the EU model. Required elements:

  1. Conformance status — voldoet volledig / voldoet gedeeltelijk / voldoet niet to EN 301 549.
  2. List of non-accessible content with reason (disproportionate burden, pending remediation, exemption).
  3. Named accessibility contact (email, ideally phone).
  4. Escalation procedure — reference to ACM (consumer sector) or the relevant sector regulator.
  5. Assessment methodology (self-assessment, third-party audit, or combination) with date.
  6. Preparation and last-review dates.
  7. The statement itself must be accessible. Published in Dutch (mandatory); English secondary version recommended for international operators.

How to comply — CI-first approach

  1. Baseline scan — run axe-core 4.11 against the homepage and 10 critical consumer flows. Most untuned Dutch DTC sites return 30-80 violations.
  2. Fix at source — overlay widgets (accessiBe, UserWay, EqualWeb) do not satisfy EN 301 549; ACM evaluates the served HTML, not what a runtime script overlays.
  3. CI gate — fail PRs that add serious-severity regressions. Prevents drift between audits.
  4. Annual human audit — axe-core catches ~57% of WCAG issues; commission a IAAP-certified auditor for the remainder.
  5. Publish the toegankelijkheidsverklaring with ACM escalation details, named contact, date, methodology.
  6. Retain evidence — per-PR axe-core scan history is the most defensible ongoing-diligence record in an ACM proceeding.
Install the GitHub Action →Statement generator← EU-wide EAA overview