We build for people who are shut out of things, so a site nobody can read would be a strange place to start.

What we aim for

We work toward the Web Content Accessibility Guidelines, version 2.2, Level AA. That is the standard most of the world has settled on, and it is the one we measure against.

We are not claiming we meet it. Nobody has run a full audit of this site, and a page that announces conformance it has not tested is just a nicer way of guessing. When an audit happens, this page will say who ran it and when.

What we actually do

• Colour contrast is measured, not eyeballed. Text is checked against its real background as a ratio, and anything below the 4.5 to 1 that AA asks for on body text gets changed rather than argued about.
• The site works without a mouse. Every link and control is reachable by keyboard, and the focus outline is left visible instead of being styled away for looking untidy.
• The site works without JavaScript. Both forms on it submit and succeed with scripting turned off. The script only removes the page reload.
• The pages follow your light or dark setting. If your system or browser is set to one or the other, the reading pages here match it rather than forcing our preference onto your eyes. The front page stays dark by design, because what is on it is built out of darkness.
• Motion is optional. If your system is set to reduce motion, the drifting embers, the cursor glow and the reveal animations do not run. That is honoured properly, not partially.
• Headings mean something. They describe the structure of the page rather than being chosen for size.

What we know is not right yet

This is the part most statements leave out.

• We have not tested systematically with screen readers. Not with NVDA, not with VoiceOver. Pages are built to be read by one, and built-to-be is not the same as tested-with. This is the largest gap on the list.
• The footer on this site failed contrast until today. Its links measured 3.12 to 1 where 4.5 to 1 was needed, which meant that for anyone whose eyes were not perfect, the link to our privacy policy was effectively not there. We found it because someone said three times that they could not see it and we finally stopped telling them to refresh the page. It is fixed. It should not have shipped.
• The builder itself is not covered by anything on this page. It is not open yet. When it is, the sites people make with it will raise a harder question than this one, because we will be responsible for the tools and they will be responsible for what they publish. We would rather work that out before we make a promise about it.

Tell us what is broken

If something here is unusable, write to our contact form and say what you were trying to do, what got in the way, and what you were using. All three help. We will answer, and we will not ask you to prove it first.

A report about accessibility is treated as a fault in the site, not as a request for a favour.