Accessibility

The target

WCAG 2.1 Level AA, on every page, in every language this site ships. That is the standard written into the studio's own brief, and the same standard applied to client work — accessibility is part of the build, not an option priced separately.

What is built in

Keyboard, everywhere

Every link, button, field and menu works without a mouse, in reading order, with a skip link to jump the navigation.

A focus ring you cannot miss

Two pixels, offset, and re-coloured on dark sections so it stays visible against the ground it lands on.

Targets you can hit

Buttons and pill controls hold a 44-pixel minimum height even where the visible shape looks smaller.

Text you can zoom

Pinch-zoom is never disabled, and the layout is built in relative units so browser text sizing works instead of breaking the page.

Motion you can switch off

Turn on reduced motion and every reveal, drift and scroll animation stops. Nothing is hidden waiting for an animation that will not run, so the page reads exactly as it should with no motion at all.

Structure, not decoration

One h1 per page, headings in order, real lists and landmarks, images described where they carry meaning and hidden from screen readers where they are ornament.

Contrast that was checked

Body text and interface colours are set from one token file and were chosen against their backgrounds, including the reversed dark sections.

Built on logical properties

Spacing and alignment are written as start and end rather than left and right, and a linter rejects the physical ones. It is the discipline that keeps a layout intact when text is resized or zoomed.

What is not done yet

Claiming full conformance without saying this would be the least accessible thing on the page.

• This site has not been independently audited. The claims above are our own testing, not a third party's certificate.
• It has not been tested end to end across every screen reader and browser pairing — testing so far is keyboard, zoom, reduced motion and automated checks.
• Some sections use scroll-driven card stacks. They fall back to a plain stacked list where the browser does not support them, but they have not been verified against every assistive technology.
• Older case-study screenshots are images of past interfaces; the text inside them is described rather than reproduced.

How it is tested

• Keyboard-only passes over every page and every interactive element.
• Rendering checked at 200% zoom and at phone width.
• Reduced motion checked as its own rendering path, not as an afterthought.
• Automated contrast and structure checks during the build.

If something blocks you

Tell us and it gets fixed. Say which page, what you were trying to do, and what you use to browse — that is usually enough to reproduce it.

Reports get a reply within two business days, and a fix or a date within ten. If a page is unusable for you right now, ask for its content another way — by email, or read out over the phone — and you will get it.