Accessibility statement
A statement is required under the European Accessibility Act and expected in any complaint. AbleGuard generates yours from what the scan actually found, publishes it on your own domain, and hard-codes it to say “partially conformant”, because that is true.
- Generated from real scan data
- Published on your own domain
- Says “partially conformant”, on purpose
Why it matters
What makes a statement worth publishing.
Built from your scan, not a template
The statement describes what the scan actually found on your site, which is what separates it from the boilerplate everyone copies.
Published on your own domain
It lives at your URL, not on ours. A statement hosted by your vendor is worth very little if the vendor disappears.
Hard-coded to “partially conformant”
That wording cannot be changed to something stronger, because for almost every real site it is the true answer.
Backed by the evidence pack
The claim is only as good as the record behind it. Every scan, fix and manual check is dated and printable.
It names what is not fixed
A statement that admits gaps is more credible than one that does not, and it is the honest position anyway.
English only today
The generator writes English. Other languages are a roadmap item, which matters if you are required to publish in your own official language.
How it works
Three steps, no vocabulary to learn.
The statement is drafted from your results
Which standard was tested, what was found, what has been fixed, what is known to remain. Not a template with your name pasted in.
You add the human parts
Contact details, how a visitor can report a barrier, and anything the manual checklist turned up.
It is published on your domain and kept current
Each re-scan updates the figures behind it, so the statement keeps matching the site.
Publish something you can defend.
Start with the free check — the statement is generated from what it finds.
A statement, and the record under it.
Anyone can publish a paragraph claiming they care about accessibility. What matters is whether there is anything behind it.
Your domain, your data, fixed wording.
The page is served from your site and generated from your latest scan. It says “partially conformant” and names the areas that are not resolved.
- Served on your own domain
- Generated from real scan data
- Wording cannot be overstated
The record is the part that helps you.
If a complaint arrives, the useful answer is a dated history of scans, fixes, verifications and manual reviews. The statement points at it; the pack is it.
- Dated and printable
- Nothing back-dated or edited
- Covers manual checks too
It reflects the findings, including the open ones.
A statement generated from a scan changes when the scan changes. Fix things and it improves; let the site drift and it will say so.
- Regenerates from the latest scan
- Open findings are not hidden
- WCAG 2.2 AA, graded by axe-core
Frequently asked questions
About accessibility statement. The product-wide questions are on the features page.
Why “partially conformant” when my score is high?
Because automation can only measure part of WCAG. A high score means the measurable part is in good shape; the rest is human judgement, and the statement should say so.
Do I need a statement if I am not in the EU?
If you sell to EU consumers, the EAA applies to you regardless of where you are based. Elsewhere, a statement is still the first thing a complaint or a demand letter asks about.
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