What the European Accessibility Act Means for Businesses in the Netherlands
A practical guide for Dutch businesses explaining scope, standards, timelines and enforcement for the European Accessibility Act. Includes a step-by-step checklist, common mistakes and short real-world examples to help companies prepare.
The European Accessibility Act in the Netherlands affects how businesses must make certain products and services accessible to people with disabilities. This article explains scope, practical steps, standards to use and what to expect from enforcement so you can plan next steps.
What the European Accessibility Act in the Netherlands covers
The Act is an EU directive that sets common accessibility requirements across member states. It targets specific goods and services where accessibility barriers create large market problems. Typical categories are digital products and services, consumer electronics, payment terminals and services, e-books and some transport and banking services. This list is not exhaustive; check whether your product or service falls in scope.
Key dates and legal mechanics
Member states had to transpose the directive into national law by the EU deadline. Businesses will face compliance obligations once national rules take effect and transitional deadlines expire. The most commonly cited EU compliance date for businesses is 28 June 2025. Confirm the exact Dutch transposition text and any sector-specific timelines for final dates and exceptions.
Standards and technical references you should use
Two technical standards you are likely to rely on are:
- WCAG 2.1 Level AA for web and app user interfaces.
- EN 301 549 as the European harmonised ICT accessibility standard. It maps to WCAG for web content and adds requirements for other ICT.
Use these standards as the baseline for testing, documentation and vendor contracts.
Who in the Netherlands must prepare
Prepare if you are a supplier, developer or service provider offering goods or services in the Dutch market that fall in scope. That includes small and medium enterprises as well as larger firms. Public administrations already have separate obligations, but private suppliers often face new duties when selling covered goods or services.
How enforcement usually works
Enforcement is handled by national authorities designated by each member state. Expect requirements for:
- an accessibility statement for each covered product or service
- a documented complaints handling procedure
- technical documentation and testing records available on request
Authorities may use market surveillance powers, order corrective measures or impose fines. The exact sanctions and procedures depend on the Dutch implementing law.
Step-by-step compliance checklist for businesses
-
Inventory
List all products, services and digital assets offered in the Netherlands. Include websites, mobile apps, e-books, terminals and customer-facing kiosks.
-
Prioritise by risk and usage
Rank items by frequency of use and impact on customers with disabilities. Tackle high-impact systems first, such as e-commerce, payment flows and service portals.
-
Gap analysis
Compare each item to WCAG 2.1 AA and EN 301 549 requirements. Record failures and remediation effort.
-
Assign ownership
Appoint a named person responsible for accessibility, with authority over development and procurement decisions.
-
Fix and test
Remediate issues using both automated tools and manual tests. Include real users with disabilities in usability testing.
-
Document
Keep technical documentation, test reports and decision logs. Prepare the accessibility statement required for covered goods and services.
-
Contract and procurement
Update supplier contracts and procurement specs to require compliance with the standards and supply of evidence.
-
Train staff
Give developers, designers and content editors basic training in WCAG basics, accessible PDF practices and testing methods.
-
Operate and monitor
Integrate accessibility into release checklists. Review and update the accessibility statement when changes occur.
What to include in an accessibility statement
- Scope: which products or services the statement covers
- Standards used: list WCAG 2.1 AA and EN 301 549 where applicable
- Known limitations and planned fixes, with expected timelines
- How to submit an accessibility complaint or request
- Contact details for responses and escalation
Common mistakes businesses make
- Relying only on automated scans. These find about 30 to 50 percent of issues but miss many usability problems.
- Ignoring non-web content, especially PDFs, Office documents and video captions.
- Not updating procurement clauses, so third-party services remain non-compliant.
- Failing to document testing and remediation decisions. Lack of records weakens your position if a complaint arises.
Real-world scenarios
E-commerce retailer
Fix checkout and product pages first. Ensure keyboard navigation, clear form labels, accessible error messages and properly labelled images. Keep receipts and test payment terminal flows used in stores.
Software vendor or app developer
Map UI components against WCAG criteria. Use EN 301 549 for non-web ICT elements and keep component-level test reports. Offer accessible configuration by default.
Bank or payment service
Prioritise ATMs, online banking, mobile apps and POS terminals. Make sure authentication flows do not block assistive technology and provide accessible alternatives for critical tasks.
Practical next steps for a Dutch business today
- Run a short inventory and gap scan covering your most-used customer journeys.
- Start accessibility fixes on the highest-risk items identified.
- Prepare a public accessibility statement even if work continues.
- Update procurement templates to include accessibility clauses and acceptance tests.
When to get external help
Call in specialist testers when you lack internal expertise in WCAG or EN 301 549. Use accessibility consultants for complex ICT, assistive-technology compatibility testing and formal documentation needed for enforcement queries.
Final practical notes
Meeting the European Accessibility Act is both a legal and a product-quality task. Work iteratively, document everything and involve users with disabilities. That approach reduces risk, improves customer reach and makes compliance sustainable.