A statement you are required to publish.

Public bodies do not get to treat the accessibility statement as optional. AbleGuard generates one from what the scan actually found, publishes it on your own domain, and keeps the dated record behind it — and it is hard-coded to say “partially conformant”, because for almost every real site that is the true answer.

  • Statement published on your own domain
  • Generated from real scan data
  • Dated evidence pack behind every claim
An office worker handles administrative tasks at a computer

Why it matters

What a public body is actually asked for.

  • A statement you must publish

    Public bodies do not get to treat this as optional. The statement is generated from your real scan data and served on your own domain.

  • Hard-coded to “partially conformant”

    The wording cannot be inflated, because for almost every real site that is the honest answer.

  • Evidence behind the claim

    A statement is only credible because of the record underneath it: dated scans, fixes, verifications and manual reviews.

  • Deadline already passed

    The EAA has been enforceable since 28 June 2025, so this is not a future compliance project.

  • English only today

    The generator writes English. Other languages are a roadmap item, which matters if you must publish in your own official language.

  • PDFs are out of scope

    Documents you host are not scanned, and for many public bodies those are the largest problem of all.

How it works

Three steps, no vocabulary to learn.

  1. Scan every page in scope

    WCAG 2.2 AA, graded by axe-core, with the 16 checks that need human judgement listed separately instead of quietly skipped.

  2. Publish the statement

    Built from what the scan found and served on your own domain, not ours. It states “partially conformant” and names what is not fixed, which is what a statement is for.

  3. Keep the evidence

    Every scan, fix, verification and manual review is dated and printable. Ongoing, documented effort is the thing that helps you if a complaint arrives.

Publish something defensible.

Start with the free check; the statement is generated from what it finds.

The statement, and what stands behind it.

Publishing a paragraph is easy. Being able to show the work behind it is the part that helps when someone complains.

On your domain, from your data.

Generated from the latest scan and served at your URL, not ours. It names what is not resolved, which is what a statement is for.

  • Served on your own domain
  • Generated from real scan data
  • Names the unresolved areas
An accessibility statement on the body’s own domain declaring partial conformance with WCAG 2.2 AA, dated to the latest scan of 122 pages.

Ongoing effort, documented as it happens.

Every scan, fix, verification and reviewed manual check is dated and printable. That history is what demonstrates good faith rather than a single audit.

  • Dated and printable
  • Nothing back-dated or edited
  • Includes the manual reviews
A dated log of a completed scan, applied fixes, a live verification and a reviewed manual check.

The sixteen a machine cannot make.

Roughly a third of WCAG is judgement. Those checks are listed as concrete questions and tracked, so the gap between automated and complete is explicit.

  • Sixteen concrete checks
  • Progress dated in the record
  • Does not certify conformance
Four of the sixteen manual checks, two reviewed and two outstanding.

Frequently asked questions

About public sector and non-profits. The product-wide questions are on the features page.

Can we publish the statement in our own language?

Not yet. The generator writes English today and additional languages are a roadmap item, so if you are legally required to publish in another language you would translate the generated text yourself.

Does it cover the PDFs on our site?

No. AbleGuard tests and fixes web pages. Documents you host — PDFs, spreadsheets, slide decks — are outside what it scans, and they are frequently the largest accessibility problem a public body has.

Is a published statement enough on its own?

No, and any vendor telling you otherwise is selling you a liability. A statement is credible because of what sits behind it: real scan data, fixes you actually applied, verification, and the manual checks worked through. That record is what the evidence pack is.

Start fixing your site today. Free.

Five pages, every problem ranked by risk, in plain English — before a lawsuit-hunting scan finds them first.

  • Free 5-page check
  • No credit card
  • 14-day money-back guarantee