Accessibility of this website

Last reviewed on 11 August 2026

This page describes how we build this website to be accessible, what we checked, and where the limits of that check are. We do not put a seal on it that we cannot back up.

1. The guidelines we use

We use WCAG 2.1, level AA as the technical reference when designing and building. For websites, the European standard EN 301 549 v3.2.1 for accessible ICT closely follows those guidelines. A new version of that standard, moving to WCAG 2.2, is in preparation and we are following it.

No full accessibility audit has been carried out for this website. We therefore make no formal claim that every page and every component fully meets WCAG 2.1 AA. Below is what we checked ourselves.

2. What we checked

  • Keyboard operation. The site can be operated entirely with the keyboard: menus, buttons, form fields and links are reachable with Tab, and the focus position is always visible.
  • Contrast. Text colours are measured against their actual background, including where text sits on a photo or a block of colour, at a minimum of 4.5:1 for regular text and 3:1 for large text.
  • Structure. Pages use real headings that rise in order, and the standard landmarks for navigation, content and footer. Every page starts with a link that jumps straight to the content.
  • Motion. Anyone who has set their system to see less motion does not get the animations.
  • Touch targets. Our own design rule is at least 44 by 44 CSS pixels for buttons, menu items and form fields. That is stricter than WCAG 2.1 requires at level AA, where that size only appears at level AAA. A link inside a running sentence follows the height of that line of text.
  • Images. Images that carry meaning have a description; images that are purely decorative are skipped by screen readers.
  • Forms. Every field has a linked label, error messages appear in text and are announced, and fields support autofill where that makes sense.
  • Zoom and reflow. Content reflows down to a width of 320 CSS pixels without you having to scroll horizontally. Measured on the home page, services, portfolio, contact and this page. On this point WCAG also requires that no information or functionality is lost along the way. That part has not yet been measured on every page.

3. Known limitations

  • Scope of the check. The checks above were carried out internally. An audit by an external party and a test with people who use a screen reader or other assistive technology daily go on top of that, and have not been done for this site.
  • Third-party components. Google Maps and the spam protection on the contact form are built by external suppliers. We check our integration of them; the internal workings of those components sit with those suppliers.
  • Documents outside this website. Documents you receive from us separately from this site are assessed case by case.

4. Something does not work for you

If you get stuck on this site, or need something in a different form, let us know. Mention which page it happened on and which browser or assistive technology you use, and we can look into it properly.

Anything you need from this site can also be obtained by phone or email, without using the website.

5. Legal context

We publish this page voluntarily, for transparency. It describes the measures we take ourselves and the limitations we know about. It is not a certification and not a legal assessment of which rules apply to Cloudpage.

The European Accessibility Act (Directive (EU) 2019/882) sets accessibility requirements for a defined list of products and services, including certain e-commerce services. Which obligations apply in a specific case depends on the service offered and on the Belgian legislation transposing the directive.

We also publish this page because we build websites for others. What we recommend to our clients, we should be doing ourselves.

6. Contact details