Accessibility Statement

We build with accessibility in mind from the start, not as a final pass. We design and test against WCAG 2.1 Level AA, which is the benchmark most commonly applied to websites in the United States and the one California courts look to, and we also work toward the newer WCAG 2.2 Level AA success criteria, which add requirements around focus visibility, dragging alternatives, and target size. Where the two differ, we aim for the stricter of the pair.

We don’t claim certification, ADA certification, perfect compliance, or a legal guarantee of compliance; those aren’t things a website can honestly claim about itself. What we can say is what we test for and what we’ve fixed.

• Keyboard operability: every interactive element is reachable and usable by keyboard alone, not just a mouse or touchscreen
• Visible focus states, applied site-wide rather than removed
• Semantic structure: one heading level 1 per page, headings that descend in order, and real landmarks (header, navigation, main, footer)
• Support for reduced motion: visitors who prefer less motion get a stable, fully visible page rather than a broken one
• Responsive layouts designed for mobile, tablet, and desktop, not just one screen size
• Labeled form fields, with errors announced to assistive technology rather than conveyed by color alone
• Real interactive elements (buttons, links, and the native dialog element for menus) instead of divs styled to look clickable

An automated browser suite, run before each release, checks every page for one heading level 1, keyboard reachability of the primary controls, reduced-motion rendering that leaves nothing hidden, labelled form fields with announced errors, and no horizontal overflow at phone, tablet, and desktop widths. In a readability pass in September 2026 we measured text contrast on the rendered pixels behind the type rather than against an assumed background, and raised the type scale and several colours as a result. We have not commissioned a third-party audit or screen-reader user testing.

This is a small, actively developing website, and we don’t claim it’s free of accessibility issues. If something doesn’t work well with your assistive technology, we want to know. See “Report a problem” below.

Some elements on this site, such as the Cloudflare Turnstile verification widget, are provided by third parties. We choose vendors thoughtfully, but we can’t guarantee the accessibility of tools we don’t build ourselves.

If you run into an accessibility barrier on this website, please tell us. Say what page you were on, what you were trying to do, and what assistive technology or browser you were using, and we’ll reply within 5 working days.

We don't have a published accessibility email address yet, which is itself a barrier: someone who can't use this site can't currently reach us without it. Until we publish one, the Start Your Project form is the working channel, and it is built to the same keyboard, label, and error-announcement standards described above. If the form itself is what's blocking you, any message that reaches us by any means will be treated as an accessibility report.

Prefer a form? The Start Your Project form reaches the same inbox.

We’ll update this statement as our accessibility work continues and as the website changes.