What to expect if you want to do it right (and without unnecessary mistakes). As of June 28, 2025, Act No. 424/2023 Coll. will come into effect, requiring companies to ensure digital accessibility for new websites and online services.
What to expect if you want to do it right (and without unnecessary mistakes). From June 28, 2025, Act No. 424/2023 Coll. will come into force, requiring companies to ensure digital accessibility for new websites and online services.
This applies to companies with more than 10 employees or a turnover of more than €2 million.
You may already know that the law applies to you. You may suspect that your website is not accessible. And you may be planning a redesign or a new project.
The question is: How do you go about it in practical terms – step by step?
Here are 5 key stages that will prepare you for auditing, development, and testing. No chaos. No unnecessary costs.
Not sure who the law applies to?
Read: EAA 2025: What the new accessibility law brings and who needs to take action.
Step 1: Quick screening
Before you start planning anything, you need basic certainty:
- Do you have a legal obligation?
- Does your website have fundamental shortcomings?
- Are you planning changes that will "trigger" the law?
An initial consultation or mini-audit can help here. You will get a quick answer as to whether (and what) needs to be addressed—and to what extent.
Not sure how to test your website yourself?
Find out step by step: 3 ways to find out if your website is accessible.
Step 2: Accessibility audit
The purpose of the audit is not just to find errors. It is a strategy for deciding:
- what exactly is not compliant
- what can be fixed
- what would be better to rebuild
The output is a clear report with priorities — not just a score without context.
Step 3: Decision – modify or rebuild?
A common question after an audit:
"Does it make sense to fix it or build a new website?"
It depends on:
- the extent of the errors
- the state of the code and technology
- planned changes
- deadlines and budget
Redesign is not a shame. It is often more effective and faster than "patching problems" on an old website.
Want to see the real benefits of an accessible website?
Read: Why does an accessible website earn more? Here's the proof.
Step 5: Development, testing, and preparation for review
Accessibility is reflected in:
- HTML, CSS, JS (valid tags, roles, ARIA)
- keyboard, screen reader, and touch controls
- documentation for development and tenders
It also includes:
- testing on real devices
- checking according to WCAG 2.1 AA
- accessibility statement
- reaudit after development is complete – verifies that everything really works without barriers
What happens if you ignore the law?
Read: What you risk if you ignore the accessibility law
What do you gain if you do it right?
- A website that complies with the law and UX standards
- A technically clean solution without barriers
- Better SEO and comprehensibility
- Higher conversion rates
- Peace in mind during inspections, tenders, and operation
How we can help you
Initial consultation
We will evaluate your project and needs
Arrange a consultation with an expert
Website accessibility audit
Clear report – both technical and for management
Get an accessibility audit
Accessible website design and development
From design to launch – accessible and effective
Design an accessible website
Accessibility is a journey – not a one-time task.
We will help you navigate it effectively, professionally, and smoothly.