Accessibility

What was tested, and what is not fixed

No law requires this site to be accessible. It aims at WCAG 2.2 AA anyway, and the parts that can be checked automatically are checked on every build rather than at launch.

Standard
WCAG 2.2 Level AA
Status
Adopted voluntarily. No legal obligation applies.
Assessed
Self-assessed. No third-party audit.
Last checked
4 October 2026

Enforced by the build

These fail CI on every pull request rather than appearing on a checklist: axe checks every route against WCAG 2.2 AA in light and dark mode, the page reflows at 320px without horizontal scrolling, nothing focusable on the home page ends up hidden under anything pinned to the top of the screen, every page keeps one h1 and a working skip link, every route stays readable with JavaScript switched off, and no request leaves this origin.

Decisions rather than defaults

Nothing is signalled by colour alone: every status is written out in words. Nothing on the site moves. There is no animation and no transition, so there is nothing forprefers-reduced-motion to switch off, and nothing stays pinned to the screen while you scroll.

Known to fall short

The server diagram on the home page and on the server page is one image to a screen reader. It reads a single text description of the whole figure rather than each box and arrow in turn. On a phone the diagram rearranges itself to fit the width instead of scrolling sideways.

The product screenshots are pictures of other software. Their alt text describes what the screenshot shows and why it is on the page, which is what the figure is for. It does not transcribe every label inside the interface.

This is a self-assessment. It has not been tested with a screen reader by anyone who uses one daily, and that is the gap most likely to be hiding something.

If something does not work

Email [email protected] and say what you were trying to do. That is a more useful report than a conformance level, and it will get a reply.