Skip to main content

Accessibility statement

Last updated: 30 August 2026

We build accessibility testing software, so it would be poor form if our own site shut people out. This page sets out what we have tested, what we found, what we know is still imperfect, and how to tell us when we get it wrong.

What we aim for

We aim to meet WCAG 2.2 Level AA across checkstrue.com and the signed-in application. WCAG 2.2 is the current W3C Recommendation and is backward compatible with the WCAG 2.1 and 2.0 versions that most accessibility laws currently name, so building to it also satisfies those. You can read our plain-English explanation of what WCAG actually requires.

How accessible this site is

This site is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the standard is met, with the known exceptions listed below.

We deliberately do not claim full conformance. WCAG has no percentage-based conformance and there is no body that certifies it, so any “certified accessible” badge is self-issued. Claiming more than we can demonstrate would be exactly the behaviour we warn our own customers about.

What we tested, and how

Most recently on 30 August 2026, we ran:

  • Automated testing with the axe-core engine against the WCAG 2.2 AA rule set, across every public page — the home page, pricing, all product pages, all legal pages, the sign-in and sign-up pages, and every article on the blog — at three screen widths (mobile, tablet and desktop). Result: zero violations across 138 page-scans.
  • Structural checks that automated rules do not cover: unique and descriptive page titles, a declared page language, one main heading per page, no skipped heading levels, one main landmark, working skip links, and reflow with no horizontal scrolling at a 320-pixel viewport.
  • Keyboard testing of the navigation, the sign-in and sign-up flows and the plan-selection journey.

These checks run from a script kept in our codebase so they can be repeated on every release rather than once a year.

The limits of what that proves

We want to be precise about this, because it is the single most commonly overstated thing in our industry.

Automated testing produces results for only about a third of the WCAG Level AA success criteria. Research published by Deque, who build the axe-core engine, found automated tests returned results for 16 of the 50 WCAG 2.1 Level AA success criteria. When the UK Government Digital Service ran ten automated tools against a page seeded with 143 deliberate accessibility barriers, the best single tool found 41% of them and 29% were missed by every tool tested.

So a clean automated result means the machine-detectable failures are gone. It does not mean the site is fully accessible. Judgement-based criteria — whether alternative text is meaningful, whether a complete process can be finished with a screen reader, whether an error message actually helps — need a human, and our coverage of those is partial. We say the same thing inside the product about every scan we sell.

Known problems

Things we know about and have not finished:

  • The signed-in application has had a source-level review but not a full end-to-end assistive technology test. Automated and keyboard checks have been run against its components; a complete screen reader pass of every journey has not.
  • We have not yet tested with people who use assistive technology daily. Expert testing is not a substitute for that, and we intend to arrange it.
  • Some PDF reports generated by the product are not fully tagged for screen readers. The same information is available on screen in HTML, which is tested.
  • Third-party checkout. Payment is handled by Paddle in a hosted overlay we do not control and cannot remediate. If you hit a barrier there, contact us and we will take your order another way.

Tell us about a barrier

If something on this site stops you doing what you came to do, we want to know — it is the most useful feedback we receive. Email support@checkstrue.com and describe what you were trying to do and what happened. We aim to reply within two working days.

If you need anything on this site in a different format, ask and we will provide it.

How we keep this honest

We re-run the automated and structural checks on every release, and we review this statement at least every six months, or sooner when we change something it describes. The date at the top is the last time it was reviewed — if it looks stale, it probably is, and you should tell us.

Accessibility testing on this site uses axe-core by Deque Systems, used under MPL-2.0. axe® and axe-core® are trademarks of Deque Systems, Inc.; ChecksTrue is not affiliated with or endorsed by Deque.