Skip to content

Accessibility

Accessibility statement

Last updated: October 23, 2026

We build this site to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Below are the checks we run, the date they last ran and who ran them, the gaps we know of, and how to reach us if something gets in your way.

Whether a particular site meets the law is a question for a lawyer, and this page gives no legal advice.

What we test, and how

An automated sweep opens every page listed in this site's sitemap twice, once at a desktop width of 1,440 pixels and once at a phone width of 412 pixels. On each page it runs axe-core, an open-source test engine from Deque Systems, with its standard rules for WCAG 2.0 and 2.1 at Levels A and AA. It also checks that each link to another page of the site answers without an error, and it saves a screenshot of the whole page. A finding that axe rates serious or critical fails the sweep. By Deque's own figure, axe finds about 57 percent of WCAG issues on average, so a page can pass the sweep and still have a barrier.

No step of our release process runs the sweep. Its last recorded run was on October 9, 2026, before this version of the site went live: one of the studio's coding agents ran it on a development copy of the site on the studio's computer and wrote the result into the build's record. Every page in the sitemap passed at both widths, and the 404 and offline pages answered as expected. Frederick approved the release.

The sweep leaves out every page missing from the sitemap: the two offer pages under /go, the sign-in page, and the private links we send clients for an invoice, a proposal or a discovery form.

This statement also covers the client portal, where clients sign in to see their project's files, messages and invoices. The sweep cannot open pages behind sign-in, and no automated test covers the portal, so its known gaps are listed below. The studio's dashboard is our internal tool, and this statement does not cover it.

What is built in

  • The page language is declared, so screen readers pronounce the text correctly.
  • On every page, the 404 page and the holiday offer page included, the first press of the Tab key reaches a “Skip to content” link.
  • Links and buttons show a cyan outline when they have keyboard focus; form fields show a cyan border.
  • Every field on the contact form and on the holiday offer's form has a visible label, and the anti-spam check is Cloudflare Turnstile, which does not ask you to solve a puzzle.
  • Text is sized in units that follow your browser's text-size setting, so enlarging text in the browser enlarges it here, and nothing on the site disables pinch-zoom.
  • The looping video on the holiday offer page carries a pause button, and the small repeating movements on the homepage and the How we work page can be paused with the control at the foot of every page. When your device asks for reduced motion, nothing moves and each loop shows its still frame.
  • Heading levels run in order on every page, and every picture carries a text description; a drawing that stands in for a picture says so in its label.
  • The pages reflow at a width of 320 CSS pixels with no horizontal scrolling.

Known limits

In the client portal, the message box has a placeholder and no label. On the sign-in page, the code field has a placeholder and a name for screen readers, with no visible label.

In the client portal's discovery form, the labels and prompts are grey on a dark card at a contrast ratio of 4.32 to 1, under the 4.5 to 1 that WCAG 2.1 Level AA asks for text of that size.

The ownership offer page under /go keeps the earlier design and has no “Skip to content” link; it comes down when its campaign ends.

Case-study pages include screenshots of client work. Their descriptions say what the screen shows, not every word on it.

Tell us about a barrier

If anything on this site is hard to use with a screen reader, magnification or other assistive technology, or with a keyboard alone, email us at [email protected]. The link fills in “Accessibility” as the subject; please add the address of the page. We read each report and fix what we can.

The standard

WCAG 2.1 is published by the World Wide Web Consortium at w3.org/TR/WCAG21. It is also the standard the U.S. Department of Justice set for state and local government websites under Title II of the Americans with Disabilities Act; the rule and its compliance dates are published at ada.gov.