Guide · Documentation
What an accessibility statement has to say
A statement is a public, dated description of where your site actually stands — not a badge and not a promise. Done properly it is the most useful page you can publish, because it answers the question anyone asking is really asking.
- Published on your own domain
- Dated and specific, not decorative
- “Partially conformant” is the honest wording
What separates a real statement from a badge.
It names a standard and a level
WCAG 2.2 at level AA, stated explicitly. A statement that names no standard is not saying anything measurable.
It carries a date
A statement without a date describes a site that no longer exists. Yours should say when it was last reviewed and what it was based on.
It admits what is not done
Roughly a third of WCAG is human judgement. A statement that claims full conformance across a real site invites the obvious question.
It lives on your domain
Not on a vendor’s. If the statement disappears when you change tools, it was never really yours.
It is backed by something
The claim should trace to a scan you can produce. AbleGuard generates the statement from real scan data and keeps the evidence behind it.
It gets regenerated
Sites change. A statement is a snapshot, so it needs re-running rather than writing once and forgetting.
How AbleGuard produces yours.
Scan the site
Every page on your plan is tested against WCAG 2.2 AA and graded, so the statement rests on measured data rather than an assertion.
Generate the wording
The conformance line is hard-coded to “partially conformant” — the honest position for a real site — with the date and the page count it was based on.
Publish it on your own domain
It goes live at your own URL, and the evidence pack behind it stays dated and printable.
A statement is a description, not a defence.
Publishing one does not make a site accessible and does not settle a claim. Its value is that it is true, specific and dated — which is also why AbleGuard will not generate a “fully conformant” statement for you, however much better that would look.
- We do not write “fully conformant” statements
- A statement does not replace fixing the site
- The wording is not legal advice
Frequently asked questions
About this guide. The product-wide questions are on the features page.
Can I say the site is fully conformant?
AbleGuard will not generate that wording, because it is almost never true across a real site and it is the easiest claim to disprove. Partially conformant, dated and specific, is the stronger position.
Where does the statement live?
On your own domain, published by you. It is your document, and it should outlive whichever tool produced it.
How often should it be regenerated?
Whenever the site changes materially, and on your plan’s scan cadence otherwise. A statement is only as good as the date on it.
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