The European Accessibility Act (EAA): What Does It Mean for My Business in Practice?
From 28 June 2025, private companies must also make their digital products and services accessible to people with disabilities. This obligation stems from the European Accessibility Act (EAA), a directive that makes digital accessibility mandatory for a wide range of sectors, including e-commerce, banking, media, and transport.
In this blog post, we’ll break down the key questions and answers: what exactly does the EAA entail, who needs to comply, and what does this mean for your website or webshop?

What is the European Accessibility Act?
The European Accessibility Act (EU 2019/882) is a European directive that was approved in 2019 and comes into force in 2025. Its goal? To remove digital barriers for people with disabilities, while also harmonising the accessibility of products and services across the entire EU.
All EU member states, including Belgium, are required to transpose the directive into national law. The deadline for compliance is 28 June 2025.
Who does the EAA apply to?
The EAA applies not only to public bodies but also to private companies. Specifically, your company must comply if you:
- Offer products or services covered by the act (such as websites, apps, digital customer service, payment solutions, etc.).
- Are not a micro-enterprise (fewer than 10 employees AND less than €2 million in turnover).
Please note: micro-enterprises are currently exempt for their services until 2030, but they are covered by the rules for products (such as interactive kiosks or e-readers).
What does this mean for my business?
For example, if you run a webshop that sells furniture or you offer online booking services, your business is indeed covered by the EAA. You will need to ensure that:
- Your website or app complies with WCAG 2.1 AA (the international standard for digital accessibility).
- Users with disabilities can order, pay, and receive help through accessible means.
- You publish an accessibility statement.
- Your customer service is accessible (e.g., via text, voice, or alternative communication).
Physical devices such as payment terminals or ticket machines are also covered by the law and must be operable by people with visual or motor impairments.
Important Deadlines
Date |
What changes? |
28 June 2025 |
Enforcement of the EAA begins for most companies. |
28 June 2030 |
The exemption for micro-enterprises expires. |
Enforcement and Fines
In each member state, compliance is monitored by designated government bodies. In Belgium, for instance, this is handled by the FPS Economy and BIPT. In cases of non-compliance, companies risk fines ranging from €1,000 to €50,000, depending on the severity of the violation.
How can you prepare?
- Audit your existing digital channels for accessibility. A service like our European Accessibility Act Audit is the perfect first step to understanding where you stand.
- Align your processes with EN 301 549 (the technical standard that supports the EAA).
- Create an accessibility statement and document any exceptions.
- Integrate accessibility into your entire development process: from design and content to code and testing.
- Partner with an expert who has expertise in digital accessibility.
How Codana Can Help
At Codana, we provide practical help with:
- WCAG audits and accessibility consulting.
- UX and UI design that complies with the EAA.
- Development and optimisation of accessible websites and apps.
- Documentation and statement texts according to legal requirements.
Together, we'll ensure your digital platform is not only ready for the future but is also usable by everyone.
Get in touch
Want to know if your website or webshop complies with the new rules? Contact us for a no-obligation screening or consultation.
The EAA makes digital accessibility more of a priority than ever. It's no longer a technical luxury but a legal obligation and a social responsibility.
For those who want to dive deeper into the technical details, our developers have written down their findings from a recent Lightning Talk. You can read their analysis from a developer's perspective here.