Last updated .
We want this site to work for everyone who wants to read it, including people using a screen reader, a keyboard alone, magnification, or a browser set to larger text. The target is WCAG 2.1 level AA.
What we have actually measured
These are results from tooling that runs against the built site, most recently on 9 September 2026:
- Automated WCAG testing. axe-core, at levels A and AA plus its best-practice rules, across the blog, the answer pages, the hubs and the listing pages. The issues it found in those templates have been fixed.
- Contrast. Body and secondary text meet the 4.5:1 minimum for normal text on every background the site uses. Secondary text was previously below it, at 3.3:1, and was changed.
- Keyboard. There is a skip link to the main content that works, every control is reachable by keyboard, and focus is visible.
- Structure. One
h1per page, headings in order without skipped levels, amainlandmark on every page, a language on every page, and alternative text on every image. - Reflow and zoom. No page scrolls sideways at 1440, 1024 or 390 pixels wide, checked automatically on every build.
- Motion. Animations respect
prefers-reduced-motion; if your system asks for reduced motion, content appears without it.
The structural checks above run as part of our build, so a change that breaks one of them does not ship.
Where it still falls short
Being honest about the gaps is more useful than claiming there are none:
- Automated testing is not enough. Tools catch perhaps a third of real barriers. This site has not had a full manual audit or testing with people who use assistive technology daily, so we cannot claim it is fully conformant.
- Some marketing pages are still being rebuilt and their heading structure has known gaps we are fixing.
- Long articles have no in-page table of contents, which makes them slower to navigate with a screen reader than they should be.
Because of the first point, our position is partially conformant with WCAG 2.1 AA, not fully conformant.
Tell us if something blocks you
If any part of this site stops you doing what you came to do, email hello@wpbuildai.com. Tell us the page and what happened; you do not need to know why it happened or name a guideline. We aim to reply within five working days, and we will tell you what we can fix and when.
If you are not satisfied with our answer, you can raise it with the Netherlands Institute for Human Rights, which handles complaints about unequal treatment on grounds of disability under Dutch law.
How this page stays honest
This statement is reviewed whenever the site's templates change materially, and the date at the top moves when it does. It describes measurements we have taken, not an intention.