Legal

Accessibility

A firm that sells websites ought to be able to account for its own. This page says what has actually been done to make these pages work with a keyboard, a screen reader, or motion turned off, and where the work isn’t finished. No outside auditor has been through it, so nothing here claims a certified level. It is a plain description of how it was built and a direct way to tell us when something gets in your way.

Last updated 3 August 2026

The standard we build to

WCAG 2.2 Level AA, on this site and on every site we build. It is what most accessibility law points at, and it is specific enough to test against rather than wave at.

What has been done

Every page is server-rendered as complete HTML, so content is available without waiting for JavaScript and is read correctly by assistive technology.
Headings run in order and describe the structure of the page rather than being chosen for their size.
All interactive elements are reachable and operable by keyboard, with a visible focus ring that is not suppressed anywhere.
Body and interface text is tested against the background for at least 4.5:1 contrast; large display text meets at least 3:1.
The decorative graphics are hidden from assistive technology, so they don’t interrupt reading: the 3D scene behind the headings, the lattice behind the closing panel, and the case-study tile art.
Every animation stops when your system asks for reduced motion, including the 3D scene, which draws one still frame and never starts. Nothing moves unless you have allowed it to.
Text reflows without horizontal scrolling down to a 320-pixel viewport and survives zooming to 200%.
Links are written to make sense out of context, so a screen-reader user listing the links on a page hears something more useful than "click here".

Known limitations

No outside specialist has audited it, and no automated tool catches everything. There will be problems nobody has found yet.
It has been tested with a keyboard and browser tooling, not end to end with every screen reader and browser combination people actually use.
The sticky header reduces available vertical space at very high zoom levels on short screens.

Reporting a barrier

If any part of this site is hard or impossible to use, email hello@businessesthatwin.com and say what happened. Which page, what you were trying to do, and what browser and assistive technology you’re using if you know it. You will get a reply within five business days telling you whether it can be fixed and when. Simple fixes usually go live the same week.

If you need information from a page in a different format, ask for it and we will send it over.

Accessibility in client work

Same standard on client sites. Keyboard use, contrast, visible focus, motion preferences and proper structure are part of the build, not an upgrade we quote for separately. If a client asks for something that would shut people out, we say so and offer something that does the same job without it.