Accessibility statement.

How accessible is this site?

Partially conformant. The site meets most of WCAG 2.2 AA. Every limitation we know of is listed below.

What works well

• The whole site can be operated by keyboard. Every page starts with a link that skips the navigation, and the mobile menu keeps focus inside it until you close it.
• All text on the site has been calculated and reaches at least 4.5:1 contrast, the AA threshold for body text.
• Every form field has an associated label, and required fields are announced as required by a screen reader. The fields are visibly distinguishable from the background (border 3.9:1), and the browser may autofill your name, email address and company name.
• Images carry a text alternative. Images that only add atmosphere are skipped by screen readers.
• If you have “reduce motion” enabled in your system settings, animations are switched off. Content stays fully visible, also without JavaScript.

Known limitations

• English pages without JavaScript. The document language is then set to Dutch and the skip link stays Dutch too. With JavaScript on both are corrected immediately, and the English content is separately marked up as English, so a screen reader reads it with the right pronunciation rules. Fixing this properly requires restructuring the site and is planned.
• The contact form confirmation leads in Dutch. Submitting the form from the English site takes you to a page where the Dutch text sits above the English.
• A server-side rejection gives no message. If the server rejects a submission you return to the form without an explanation and without the text you typed. In practice your browser catches missing or malformed fields before sending, with a message at the field itself.
• The contact form requires JavaScript. Since 4 August 2026 the form runs a spam check (Cloudflare Turnstile). Without JavaScript you cannot submit through the form; it shows the email address as an alternative. If JavaScript is on but the spam-check script is blocked — for example by a strict privacy extension — you return to the form after submitting, without an error message. Email always works.

How we tested

This statement was prepared on 4 August 2026 and re-tested on 26 August 2026 after five sections were rebuilt. Both reviews went through the code and the rendered page, measuring contrast, focus, keyboard operation and the information passed to a screen reader, across several screen widths. What we have not done yet: a test with an actual screen reader, an automated audit tool, and a test at 200% zoom. Those three are scheduled for when the site runs on its own address. The site has not been certified by an external party.