Our Commitment

We want to be straightforward about what is not yet working. These are the issues we have identified, with the WCAG 2.2 success criteria they relate to and when we plan to fix them.

 

1. Alternative text on images (WCAG 1.1.1 Non-text Content). Some images have no alternative text, and others use file-name style text such as "virtual office.jpg" or "home_page_img" instead of a description of what the image shows. Screen reader users hear either nothing useful or a file name. Purely decorative images should be marked as decorative so they are skipped.

Planned fix: by 31 January 2027.

 

2. No "skip to main content" link (WCAG 2.4.1 Bypass Blocks). Keyboard and switch users have to tab through the full navigation on every page before reaching the main content. We will add a skip link that appears when it receives keyboard focus.

Planned fix: by 31 December 2026.

 

3. Carousel without a pause control (WCAG 2.2.2 Pause, Stop, Hide; 2.4.3 Focus Order). The carousel on our homepage has next and previous controls, but we have not yet confirmed that it can be paused or stopped, and we have not verified that keyboard focus stays in a sensible order as it changes. Content that moves on its own can be difficult for people with low vision, cognitive impairments or screen readers to follow.

Under review — we will add a pause control or make the carousel advance only when the visitor chooses. Planned fix: by 31 January 2027.

 

4. Colour contrast (WCAG 1.4.3 Contrast (Minimum)). We have not yet completed a full contrast audit. Some text — including form placeholder text and small print in the footer — uses grey on white and may fall below the required 4.5:1 contrast ratio.

Contrast audit: by 30 November 2026. Fixes: by 31 January 2027.

 

5. Focus visibility (WCAG 2.4.7 Focus Visible). The appearance of the keyboard focus indicator depends on the underlying website components. We have not yet checked it everywhere, in particular in the mobile menu and the carousel.

Under test, fixes by 31 January 2027.

 

6. Form error messages (WCAG 3.3.1 Error Identification; 3.3.3 Error Suggestion). Our forms show validation errors on screen, but we have not yet confirmed that screen readers announce them promptly and clearly, or that each message explains how to correct the problem.

Under test, fixes by 31 January 2027.

 

7. Mobile menu focus handling (WCAG 2.1.1 Keyboard; 2.1.2 No Keyboard Trap). The full-screen mobile menu should keep focus inside it while open and return focus to the menu button when closed. We have not yet verified this behaviour with a keyboard or screen reader.

Under test, fixes by 31 January 2027.

 

8. Spam protection on forms. Our forms include an automated spam check. If you cannot complete it, you can contact us by email instead — see "Contact us about accessibility" below.

 

9. Content we do not control (partial compliance). Our site is built and hosted on the Wix platform, and our forms are provided by Wix Forms. Some of the markup and behaviour generated by that platform is outside our direct control, including parts of the mobile menu and form validation. We declare **partial compliance** with WCAG 2.2 AA for those components, and we raise issues with our provider where an alternative is available. We have deliberately not embedded third-party tools such as live chat, advertising or tracking widgets, which reduces the number of inaccessible components on the site.

 

Content outside the scope of this statement. If we link to a document or to another organisation's website, that content may have been produced by someone else and may not meet the same standard. If you need help with any linked content, contact us and we will provide the information directly.