Digital accessibility
Building for accessibility isn't an extra layer. The European Accessibility Act has applied since 28 June 2025. For many websites, accessibility has gone from a good idea to a legal requirement. I map out where your site stands, fix the issues in the code, and keep it that way.
When should you start an accessibility project?
Government websites already fell under the earlier web accessibility directive. If the new law applies to you, the question is no longer whether you need to comply, but how you demonstrably get there.
- You sell online, or offer banking, transport, telecom or e-book services, and you're not sure whether your site complies.
- You work for or with government and need to substantiate an accessibility statement.
- An external audit produced a list of issues and no one is fixing them in the code.
- You're building a new platform and want to bring accessibility in from the architecture stage.
My approach: measure, fix, document
Accessibility is code work, not a plugin. Overlay tools that promise to make a site accessible with a single line of JavaScript don't fix the underlying problems.
Audit
Tools cover the basics, manual work covers the rest. I go through the entire site using only the keyboard, test the main flows with a screen reader, and check contrast and focus order. Result: findings per WCAG success criterion, ranked by impact.
Fix it in the code
Fixed where it originates: in the theme, the templates and the components. Semantic HTML, ARIA only where it's actually needed, visible focus, and full keyboard operability.
Document it
The principles built into the components themselves, an editor where the accessible choice is the easiest one, and the evidence you need for your accessibility statement.
Why Drupal and accessibility go well together
Drupal has had accessibility as a core principle for years, which saves a lot of work.
- The admin environment works too: operable with keyboard and screen reader, so your editorial team keeps moving.
- Correct semantics out of the box: the core components deliver the right HTML, so you're not starting from zero.
- No automatism: the theme, custom components and content determine most of the result.
- Experience that counts: applied on sites for universities, government and industry. Take a look at the cases.
Frequently asked questions
Does the European Accessibility Act apply to my website?
The European Accessibility Act, Directive 2019/882, has applied since 28 June 2025 and covers a defined group of products and services: e-commerce, consumer banking services, electronic communications, passenger transport, e-books and access to audiovisual media services. Micro-enterprises that provide services are exempt: fewer than ten employees and an annual turnover or balance sheet total of at most two million euros. Whether your site falls under it depends on what you offer, so have that checked legally.
What is the difference between WCAG 2.2 and EN 301 549?
WCAG 2.2 is the international guideline with the concrete success criteria, EN 301 549 is the European standard that references it and adds requirements for hardware, software and documents. For a website, in practice you work towards WCAG 2.2 level AA.
What are the four principles of accessibility?
Perceivable, operable, understandable and robust. Every success criterion in WCAG falls under one of those four. They apply to the entire interface, so also to forms, error messages, video and dynamic components.
What is an accessibility statement and do I need one?
An accessibility statement sets out to what extent your site complies, which parts do not yet comply and why, and how visitors can report a problem. It is mandatory for government organisations in Belgium and the Netherlands. For private parties under the EAA there is no identical statement requirement, but it is how you demonstrate you're taking it seriously.
How can I get my website tested for accessibility?
With a combination of automated tools and manual testing, because tools only find part of the problems. You can get a first impression yourself with Lighthouse or axe DevTools, then go through the entire site using only the keyboard. A substantiated judgement per success criterion requires manual testing with a screen reader.
Who supervises this?
In Belgium, the FPS Economy is designated as the supervisory body for the European Accessibility Act. For government sites, supervision runs through the existing channels of the web accessibility directive. The concrete enforcement practice is still being built up at this time.
Does your site meet the accessibility requirements?
Not sure whether the European Accessibility Act applies to you, or do you have an audit report nobody is acting on? Let me know where you stand. I'll review your request and give you an honest picture of what's needed within 24 hours.
Want to know first whether the legislation applies to you? Read when the European Accessibility Act applies to your website (Dutch).
Does your site meet the accessibility requirements?
Not sure whether the European Accessibility Act applies to you, or do you have an audit report nobody is acting on? Let me know where you stand.
I'll review your request and give you an honest picture of what's needed within 24 hours.
