Accessibility

This site is built to be usable by everyone — by keyboard, by screen reader, on a slow connection, and with motion turned down. This page describes what that means concretely, where the limits are, and how to tell us when something gets in your way.

The standard we build to

The target is WCAG 2.2 Level AA, and it is checked automatically rather than asserted. An accessibility engine (axe) runs against the real conversion, search, demonstration, and console flows on every change, testing the WCAG 2.0, 2.1, and 2.2 A and AA rule sets — not a marketing page built for the audit, but the pages you actually use.

Keyboard and focus

Everything works without a mouse. A “Skip to main content” link is the first thing in the tab order on every page, so you are never forced through the navigation to reach what you came for. Focus is always visible, and the order it moves in follows the order things are read.

Screen readers and structure

The accessibility of a page is designed into its structure, not painted on afterward. Each page has one banner, one main region, and one footer; headings descend in order without skips; the current page is marked in the navigation; and controls are labelled by what they do rather than by how they look. Anything decorative — brand tiles, background video — is hidden from assistive technology so it never reads as content.

Motion

If your device is set to reduce motion, the site honours it: the background videos hold on a still frame and entrance animations are dropped rather than played. Nothing important is ever conveyed by movement alone, so turning motion off costs you no information.

Works without JavaScript, and on a slow connection

The portfolio, the guided project inquiry, and the expandable sections are built from elements the browser already knows how to operate, so they keep working when JavaScript is slow to arrive or blocked entirely — the enhancements layer on top rather than being the only path. Pages are kept light and images and video are streamed at the size actually needed, because on limited hardware or bandwidth, speed is accessibility.

Colour and contrast

Text and interface colours are drawn from a single palette whose combinations are held to the AA contrast ratio by an automated test — including the coloured service tiles, whose letters are checked against their own background. Colour is never the only thing carrying a meaning; a status or a state always has a word or a shape beside it.

Where the limits are

Automated testing catches a great deal, but it cannot prove that a real person using a real assistive tool can comfortably finish what they came to do. Some third-party embedded demonstrations are not under the studio’s direct control and may not meet the same bar. This page describes a genuine, tested commitment — not a certificate of perfection.

Found a barrier?

If any part of this site was hard or impossible to use, that is something the studio wants to fix, and a specific report is the most useful thing you can send. Get in touch — tell us the page, your device or assistive tool, and what happened, and you will get a real reply.