Accessibility statement
This site aims to meet WCAG 2.2 level AA, and is tested against it automatically before every change is published. This page says what that covers, what it does not, and how to tell me when something is wrong.
What is checked, every time
These run on every change. If any of them fails, the change is not published.
- An automated WCAG 2.2 AA audit of every page, run twice — once in the light theme and once in the dark one.
- Reflow at a 320 px viewport, with no horizontal scrolling.
- Text enlarged to 200%, with the page still readable and nothing clipped.
- Keyboard navigation: a skip link, a visible focus indicator, and a control target of at least 44 px.
- Reduced motion honoured, for anyone whose system asks for it.
- The whole site read and navigated with JavaScript switched off.
- Every page carrying a language, a single first-level heading, and a description.
What that does not prove
Automated testing finds a minority of accessibility problems. It is good at contrast, missing labels, broken structure and invalid attributes. It cannot judge whether a heading describes what follows it, whether alternative text says the useful thing, whether an interaction makes sense with a screen reader, or whether the writing is clear.
So the checks above are a floor, not a certificate. I review pages by keyboard and take care over structure and alternative text, and I have not commissioned an independent audit of this site. If you find something that the tests missed, that is a gap in my process rather than an edge case, and I would like to know about it.
Known limitations
The colour-theme control needs JavaScript, so it is hidden when scripting is unavailable. Nothing else on the site depends on it: with scripting off, the theme follows your system setting and every page remains fully readable.
Reporting a problem
If any part of this site is difficult or impossible to use, please email hello@knowlezi.dev with the page address and a short description of what happened. Tell me what you were trying to do and what you were using, if you can — it usually makes the cause obvious.
I aim to reply within three working days, and to say either when it will be fixed or why it cannot be.
Why this page exists
I build websites for churches and community organisations, where the people arriving may be older, unfamiliar with the site, on a slow connection, or looking for something urgently. Accessibility is the substance of that work rather than a compliance exercise, and it would be strange to claim it without publishing how my own site is held to it.
The technical detail is in the colophon.