Accessibility statement
Accessibility is one of the things I sell as a studio, so I take this page seriously. Here is what I do, and what can still improve.
My ambition
I build this site against WCAG 2.1, level AA, as a guideline. That is not a legal requirement for a site like this one, that only applies to government websites, but I apply the standard anyway because accessibility is one of the four things I offer as a studio.
What is already in place
A few concrete measures on this site:
- Every form field has a real associated label, and grouped fields sit in a fieldset with a legend
- A visible focus state on keyboard navigation, everywhere you can click
- A working skip link to the main content
- Motion and animation respect prefers-reduced-motion
- Headings follow a logical, ascending order
- The active page in the navigation is marked with aria-current
- Alt text describes what is in an image, rather than repeating its caption
- The menu on small screens works fully with the keyboard, and Escape closes it and puts you back on the menu button
- Contact form errors sit next to the field itself, in the language of the page, and focus moves to the first field that needs attention
What is still in progress
This site is still growing. Not every page is equally developed yet, and I regularly retest with keyboard and screen reader to find spots that need work. If you run into something that is not accessible, let me know.
Found something that is not accessible
Email bertlempens@gmail.com with a description of the problem and, if possible, the page it happened on. I reply within two working days.
About this statement
Last updated: 26 September 2026.
Tested on that date with axe-core and Lighthouse on every page, in both languages, at desktop and phone width, and with keyboard navigation. No automated errors.