What we've done, and what we haven't.
We build for people who may be using a screen reader, a magnifier, a keyboard only, or a browser zoomed to 200%. Effective 17 September 2026.
The section that matters most on this page is the last one, because it is the one that admits what has not been tested.
What we aim for
WCAG 2.2 Level AA.
We target WCAG 2.2 Level AA. We are not claiming conformance, because conformance is a formal statement that requires a formal evaluation and we have not commissioned one.
What is built in
Checked, not assumed.
- Every page works with the keyboard alone. A skip link is the first focusable element on each page, and focus is always visible — a two-pixel amber outline, never removed.
- One
h1per page, headings in order. Verified programmatically on every page, not eyeballed. - The diagrams are described, not decorative. Both the entity diagram and the call-pipeline diagram carry a full sentence description, so a screen reader gets the argument rather than the word "image".
- Text resizes properly. The layout is built in relative units against a fluid root size, so browser zoom and larger default font sizes reflow the page instead of clipping it. Tested from 320px to 3440px wide.
- No motion. There are no animations, no autoplay, no parallax and no carousels. Nothing on this site moves unless you scroll it.
- No scripts. The site is static HTML and CSS. Nothing depends on JavaScript running, so nothing breaks when it doesn't.
- Contrast. Body text is near-black on warm paper. The teal used for links and emphasis was darkened from the brand's on-dark value specifically to pass on a light background.
- Self-hosted fonts render even on a slow or filtered connection, so text does not disappear while a CDN is reached.
- Links that leave this site open in a new tab and say so. Each one carries a hidden "(opens in a new tab)" for screen readers, because a link that silently replaces the page you were reading is a context change you should be warned about. Email links are excluded — they open your mail program, not a page.
Known limitations
The honest part.
No screen-reader testing has been done on this site. Not with NVDA, JAWS, VoiceOver or TalkBack. The structure was built to be read correctly and verified with automated checks, but automated checks find perhaps a third of real problems. Until someone has actually listened to these pages, treat the list above as intent supported by evidence, not as a tested result.
- No independent audit has been commissioned. We will commission one rather than claim coverage we do not have.
- The diagram descriptions are long. A screen-reader user meets a paragraph of description where a sighted reader sees a picture. That is better than nothing and worse than a properly structured alternative; a text version of each diagram is on the list.
- The hanging side headings are visually to the left of the content they introduce. In the reading order they come first, which is correct, but the visual relationship is carried by position rather than by anything a screen reader conveys.
- Colour has not been checked against every form of colour vision deficiency. Nothing on this site uses colour as the only means of conveying information, which is the rule that matters most, but the palette has not been formally simulated.
Tell us
It is a defect, not a favour.
If something here is hard or impossible to use, write to hello@kaindness.org and describe what happened and what you were using. We treat it as a bug report, not a complaint, and we will tell you what we found.
If you need anything on this site in another format, ask and we will send it.