Discuss Your Project

Accessibility

Last updated July 16, 2026

Using this website

[To be supplied. What the site does to make itself usable, and what a visitor can change: text resizing, zoom, keyboard operation, screen reader support.]

How accessible this website is

[To be supplied. The conformance claim. State the standard and the level, and state honestly whether it is fully, partially or not compliant. This sentence cannot be written until the built site has been tested.]

Known issues

[To be supplied. Every issue found and not yet fixed, what it affects, and when it is expected to be fixed. An empty list here is a claim of perfection and reads as untested.]

Reporting a problem with this website

[To be supplied. How to report an accessibility problem, and how quickly a reply can be expected. Needs the resolved contact address.]

Enforcement procedure

[To be supplied. Who a visitor can escalate to if they are not satisfied with the response.]

How this website was tested

[To be supplied. When it was last tested, who tested it, and how: assistive technology, browsers, and whether testing was automated, manual or both.]

Start a conversation

Let's build something that lasts

Every meaningful partnership begins with a conversation. Tell us what you are trying to achieve and we will listen carefully.

Chat on WhatsApp