Accessibility

Last updated 4 September 2026

1. Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the standard most commonly referenced in US accessibility practice.

We want to be honest about this rather than post a badge: we are working toward that standard, not certifying that we have fully met it. This site has not been through a formal third-party accessibility audit. Where we know we fall short, we say so in section 3.

2. What we have done

• Keyboard navigation — interactive elements can be reached and operated with a keyboard, with visible focus outlines throughout.
• Reduced motion — the site has a lot of animation, and all of it respects your operating system's "reduce motion" setting. Turn that on and the scroll effects, moving strands, and transitions stop.
• Semantic structure — headings, landmarks, and lists are marked up so assistive technology can navigate the page structure. Every page has a single top-level heading and a main landmark.
• Skip link — the first thing you reach with the Tab key is a "Skip to content" link, so keyboard and screen-reader users can jump past the navigation.
• Labelled form controls — every field in the project brief is programmatically tied to its visible label, so screen readers announce what each one is for.
• Readable text sizes — body and supporting text stays at a legible size at every screen width.
• Consent before tracking — the cookie banner is keyboard-operable, and its Accept and Decline buttons carry equal visual weight.
• Text alternatives — meaningful images carry descriptive alternative text; purely decorative graphics are hidden from screen readers so they do not add noise.
• Colour contrast — body text and interface colours are chosen for legibility against their backgrounds.
• Responsive layout — the site reflows for phones, tablets, and desktops, and supports browser zoom.

3. Known limitations

We would rather tell you where the gaps are than pretend there are none. As of the date above:

• Colour contrast in a few places. Some supporting text and muted labels sit close to the minimum contrast ratio rather than comfortably above it. We are reviewing these.
• Motion-heavy sections. Where "reduce motion" is not enabled, some sections animate substantially as you scroll. If this is uncomfortable, enabling reduced motion in your system settings will stop it.
• Demonstration sites. The sample builds linked from our home page are illustrative pieces and have not been held to the same accessibility review as this site.

These are on our list, and this page will be updated as they are resolved.

4. Turning on reduced motion

5. Tell us about a problem

If something on this site is difficult or impossible for you to use, please tell us. You do not need to know why it is broken or use any particular terminology — just describe what happened and what you were trying to do.

It helps if you can include the page address, what device or browser you were using, and any assistive technology involved, but send what you have.

We aim to respond within 3 business days, and to tell you either how we have fixed it or when we expect to. If you need information from this site in another format while we work on a fix, ask and we will get it to you another way.

6. Accessibility in the sites we build

Accessibility is part of how we build client websites, not an add-on: semantic markup, keyboard support, sensible contrast, and text alternatives are included as standard. If your project has specific accessibility requirements — a formal WCAG conformance target, or a public-sector obligation — tell us at the start and we will scope for it.

7. Changes to this statement

We update this page as the site changes and as known issues are resolved. The "last updated" date at the top tells you when this version was published.