Accessibility

Semantic HTML before JavaScript, so the content, the limits and the sources of a tool are readable with scripts off. Full keyboard operation with a visible focus ring on every control. Real labels, help text and error messages wired to their fields. One h1 per page and headings in order.

Buttons, choices, form fields and stand-alone links are at least 44 pixels in both directions. Links that sit inside text, including the long reference lists on the sources page, keep the height of their line of text instead. Every piece of text on the site is at least 16 pixels, labels, help text and metadata included. Neither floor is taken on trust from a stylesheet: the site's own checks measure the pixels a browser actually paints, on the tool library and on a tool page, and they were red on both counts until the design was redrawn to meet them. Color is never the only thing carrying a meaning: every state has a word or a shape as well. Motion is decorative and is switched off entirely when your system asks for reduced motion.

No tool has a time limit, and none ever will.

Keyboard operation, focus order, heading structure, label wiring, contrast ratios, rendered text size, rendered target size, reflow at 320 pixels, 200 per cent zoom, and printing in black and white, all on a local build of the site. The automated measurements run on the English pages. Every language shares the same layout, but longer or shorter words can move a button or a line, so each language still needs its own measurement.

That is a floor, not a pass. Automated and self-conducted checks catch the mechanical failures and miss the ones that matter most.

Testing with screen reader users. Testing with people who have low vision, limited mobility, or cognitive and learning differences. Testing on assistive technology we do not own.

Two tools additionally need a test that has nothing to do with disability and everything to do with the moment they are used: can a stressed person find the safety boundary and the human route without reading the whole page. Neither has had it.

Until those happen, this site does not claim conformance with WCAG 2.2 AA. It claims to be built against it.

On pages written in the Latin alphabet, every form control, every label and all body text are set in Atkinson Hyperlegible, designed by the Braille Institute so that letterforms which are usually confused with each other are not. It is used here because the pages get read quickly, often on a phone, sometimes by someone who is not in a state to squint at anything. A page written in a script that Atkinson does not cover uses the fonts already on your device instead, rather than mixing two typefaces in one line.

There is no contact email address. The private feedback on the feedback page reaches me, and a report of an accessibility problem sent there is treated as a bug rather than as an opinion. The private feedback asks for no name and no contact details, so it cannot be answered.