Accessibility statement for setsquare.dev

You should be able to:

• choose WCAG 2.2 AA or AAA sizing for the whole site, in the footer
• choose a light or a dark theme, or follow your system
• change colours and contrast with your browser or operating system
• zoom to 200% without text spilling off the screen
• use every page with a keyboard
• use the site with animation turned off
• read it at 320 pixels wide without scrolling in two directions

How accessible this website is

We publish the scan behind what follows rather than asking you to take it on trust: every page, in both themes, at every width the suite runs, at each level you can choose. The figures are on the evidence page, including everything the scan could not decide.

Compliance status

This website is fully compliant with the Web Content Accessibility Guidelines version 2.2 AA standard.

We aim higher than AA and do not fully meet AAA. The guidelines do not recommend AAA as a general policy, because some of it cannot be met for all content, but we build to it because it is what our own software asks of the people who use it.

Content that does not meet the AAA level

The reading level of our writing does not meet WCAG success criterion 3.1.5 on 20 of 20 pages, grading as high as 63.4 against a target of 9. We have chosen precision over a lower score: the words that would bring the grade down are the words that would make the claims vaguer. It is a named exception in our own test suite, so every other rule still has to come back clean, and if the finding stops appearing the exception fails too.

The measure itself is a proxy: a formula counts sentence and word length, and the criterion is about reading ability. If you find a page genuinely hard to follow, that is worth more to us than the score.

Decisions we have taken, and would defend

• Colour is never the only carrier of meaning. The conformance levels are told apart by their letters, a failure always says so in words, and the evidence bars repeat numbers that are in their own table cells.
• The faintest line in our palette is decorative. It sits below any contrast floor and never separates two pieces of information on its own. At AAA, region edges use the 3:1 border instead. If you find a faint line doing real work, it is a bug we want to hear about.
• We do not offer a high-contrast theme of our own. What we support is your system replacing our palette entirely: the page is built so that losing our colours loses nothing but colour.

Feedback and reporting a problem

If you need anything here in a different format, or you find a problem this page does not list, use the report form or email hello@setsquare.dev. Say which page, what you were trying to do and what happened, and, if you use assistive technology, which one. We reply within two working days.

Enforcement procedure

The regulations that require a statement in this format apply to public sector bodies. Worktree Amigos is not one, so no enforcement procedure applies and there is no regulator to escalate to. We publish the statement anyway, in the format a reader already knows, because a company selling conformance evidence should be the last one asking to be taken at its word.

How we tested this website

Every page each site publishes, not a sample, in both themes, at three widths, at each level we have a scan for. The scan reads the same route list each site is built from, so a page that exists is a page that was assessed.

• www.setsquare.dev at AAA: six pages, 42 scans, last on 2026-10-03 09:22 UTC, with axe-core 4.13.0
• www.setsquare.dev at AA: six pages, 36 scans, last on 2026-10-03 09:23 UTC, with axe-core 4.13.0
• docs.setsquare.dev at AAA: 61 pages, 427 scans, last on 2026-10-03 09:39 UTC, with axe-core 4.13.0
• docs.setsquare.dev at AA: 61 pages, 366 scans, last on 2026-10-03 09:49 UTC, with axe-core 4.13.0

Automated rules reach a part of what matters, not all of it: Deque measured their engine finding 57% of issues in first audits, and it is the engine we run. The criteria no rule can decide are listed on the evidence page with the reason. The rest are held by tests that run on every build: keyboard reach on every control, both themes, both levels, reduced motion, text at 200% and layout at 320 pixels. That makes them repeatable, and narrower than a person would be.

What we have not done

There has been no external audit, and no testing by people who use screen readers or other assistive technology every day. Those find things that neither a rule nor a developer does. When that changes, this section will say who did the work and when.

This statement was revised on 2 October 2026, for the rebuild of both sites.