Accessibility Statement

What we’re aiming for

Our target is WCAG 2.2 level AA across the whole site. That means perceivable, operable, understandable, and robust for keyboard, screen-reader, and assistive-tech users.

What should work well

• All content is reachable by keyboard. Focus states are visible and the tab order follows the visual reading order.
• Semantic HTML throughout. Headings are nested correctly, landmarks (nav, main, footer) are labelled, and links say where they go.
• Text contrast meets or exceeds 4.5:1 for body copy and 3:1 for large display type against our dark background.
• Every image has alt text. Decorative images are marked as such so screen readers skip them.
• The site works without a mouse. Every interactive element can be activated with Enter, Space, or the relevant arrow key.
• We respect prefers-reduced-motion. If you’ve turned reduced motion on in your OS, our scroll-triggered animations and smooth-scroll effects are toned down.

Known limitations

We’re honest about the places the site trades visual polish for accessibility. These are open issues we’ll improve where we can:

Custom cursor

On mouse-and-trackpad devices we replace the default OS cursor with a custom dot-and-ring cursor. Keyboard users, touch users, and anyone on a reduced-motion setting are not affected. If you rely on an enlarged or high-contrast OS cursor for visibility, the custom cursor may work against you. Disable JavaScript and you’ll get your native cursor back.

Smooth scrolling

We use a smooth-scroll library (Lenis) for momentum scrolling. Some users, especially on trackpads with reduce-motion enabled, find this disorienting. We honour the reduce-motion system preference, but the fallback is not identical to native scrolling.

Scroll-reveal animations

Several sections fade or translate into view as you scroll. This is driven by GSAP and requires JavaScript. We use CSS to hide these sections by default so they don’t “pop in” after the page loads; if JavaScript fails, they stay hidden. This is a deliberate trade-off for a smoother first paint, but it means JavaScript-off users lose some content. If you browse with scripts disabled and hit this, email us and we’ll send you the copy directly.

How to tell us about a problem

We want to know when we get it wrong. Email hello@webgro.co.uk with the page URL and a description of what’s not working. We aim to reply within one working day and fix confirmed issues within 30 days.

If we can’t fix something immediately, we’ll add it to this page as a known limitation and give an honest estimate of when it’ll be resolved.

Escalation

If you report an issue and you’re not happy with our response, you can contact the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com. Webgro is a private-sector company, so public-sector accessibility regulations don’t formally apply to us, but we try to meet their spirit anyway.

How this statement was prepared

This statement was prepared in April 2026 based on a self-review of the site against WCAG 2.2 level AA. We haven’t yet commissioned a formal external audit; when we do, we’ll update this page with the results and any new known issues.