WCAG obligation: is your digital environment ready for it?

A digital environment is ready for the WCAG obligation if it complies with the WCAG 2.1 guidelines at levels A and AA. Among other things, this means: good color contrast, keyboard navigation, screen reader support, and clear structure. In addition, an up-to-date accessibility statement is mandatory.
From June 28, 2025, commercial organizations must make their digital services accessible. The obligation applies to companies with more than ten employees or an annual turnover of at least two million euros. The standard is clear: WCAG 2.1, levels A and AA.
Yet we see that many organizations are not ready yet. Sometimes knowledge is lacking, sometimes capacity. Often the subject gets stuck between departments, without anyone being truly responsible.
Accessibility requires clear choices. It requires people who understand what is needed and ensure that it is properly arranged. That starts with overview and management.
What the law requires and to whom this applies
The obligation applies to commercial organizations that offer digital services to consumers. Think of webshops, booking systems, payment apps, and self-service environments. Anyone with more than ten employees or an annual turnover of at least two million euros must comply with the WCAG 2.1 guidelines at levels A and AA from June 28, 2025.
Among other things, this means that users must also be able to use a website or app with a keyboard or screen reader. That texts are easy to read, contrasts are correct, and navigation is logically structured. It is also required to record what you have already done, what still needs to be done, and how you approach that. In many cases, a WCAG check or audit is necessary to map out the status of your digital environment properly.
The requirements are clear. But how to work towards them is still unclear in many organizations.
A design system helps to structurally secure accessibility, because components are tested centrally. Read more about this in our article on design systems for large organizations.
Why many organizations have not sorted it out yet
Accessibility affects multiple parts of an organization. It begins with design, continues into technical development, and requires anchoring in the process. In practice, it is therefore often neglected. Not because the subject is not considered important, but because no one knows exactly where it belongs.
We see teams that want to proceed but do not know where to start. Or where the conversation about digital accessibility is being held, but is not translated into concrete actions. Without ownership and experience, it remains difficult to determine what is needed and how to tackle it.
That is precisely where delays occur. Whereas arranging accessibility on time in accordance with the WCAG guidelines requires focus, collaboration, and professional expertise.
What we see in practice and what our people do
We regularly join organizations that want to work on accessibility but get stuck on the execution. Sometimes there is awareness, but no structure. Or something has already been attempted technically, but there is a lack of coherence between teams.
Our people bring overview. They make it clear what the law requires, what the current status is, and what is needed to move forward. They do this in collaboration with the team, not alongside it.
We deliver UX designers who design with an eye for user-friendliness and inclusion. Front-end developers who make websites accessible according to WCAG 2.1. And product owners who ensure that digital accessibility is structurally included in priorities, choices, and documentation. Always with an eye for the context in which they work. And always focused on sustainably strengthening the team.
Accessibility is part of quality
The law makes accessibility mandatory. But regardless of what must be done, it also brings benefits: better digital services, broader usability, and more grip on your process.
Designing and building accessibly forces you to make clear choices. You look more closely at the structure of your page, the readability of your text, and how your navigation works. By doing so, you improve the experience not only for people with a disability, but for all users.
That requires professionals. People who understand how to integrate digital accessibility from the start. And who ensure that it keeps working, even as your platform continues to develop.
Accessibility is part of a broader issue regarding your digital platforms and the experience they offer. Read more about this on our page about digital platforms and user experiences.
Accessibility starts with clear choices and experienced people
The obligation is here. The question is whether your organization is ready for it. Not on paper, but in practice.
Digital accessibility according to WCAG 2.1 requires knowledge, experience, and ownership. It requires people who understand what is needed and bring it into the work process in the right way. Our professionals help with this. Not as an external project, but as part of your team.
Curious about what we can do for your organization? Get in touch with Maarten.
Anything to amaze you.
Frequently asked questions about the WCAG obligation
What does the accessibility obligation from 2025 entail?
Organizations with more than ten employees or a turnover starting from two million euros must comply with the WCAG 2.1 guidelines. This obligation applies to websites, apps, and digital services such as booking systems and webshops.
What does WCAG 2.1 concretely require from my digital environment?
The directive sets requirements for keyboard navigation, color contrast, semantic HTML, screen reader support, and an understandable structure, among other things. In addition, an up-to-date statement on the status of accessibility is required.
How can Koodin help with digital accessibility?
We provide UX designers, front-end developers, product owners, and digital consultants with experience in WCAG 2.1. They ensure structure, collaboration, and an approach that fits your organization and continues to work in the long term.












