Accessibility statement generator
Draft an accessibility statement for the UK, the European Accessibility Act, or the US. It is free. Edit it, then publish it on your site.
What the draft is for
A statement tells customers how to reach you and what you know about the site today. It is a page on your domain, with a contact email and a date. It is not a badge and it is not a certificate.
The generator writes a starting text in one of three shapes. The UK shape follows the public-sector pattern people already recognise: what you are doing, how to report a problem, and the limits of automated checks. The European Accessibility Act shape is for shops selling in the EU. The US shape explains the checks and how to report a barrier.
You get the draft on this page and by email. Every AltGrade plan includes it. The £49 audit attaches a draft to the PDF as well. You still edit before anyone else should see it.
What you must change
Put your real organisation name, the site URL and a contact email a person reads. Delete any issue that you have already fixed. Add issues you know about that the scanner did not see, such as a video without captions.
Set the date to the day you publish. When you rescan and fix a group, update the date and the list. A statement from last year that lists bugs you shipped in March is worse than a short current one.
Publish it at a stable URL, often /accessibility, and link it from the footer. Do not hide it in a PDF only. People need to open it from the page they are stuck on.
What the draft will not do
It does not decide whether you meet the Equality Act 2010, the European Accessibility Act, or the Americans with Disabilities Act. This is general information, not legal advice. If you need a view of your legal position, ask a qualified adviser.
It does not invent a conformance claim. The text says which checks were run and how to report a problem. If you want a stronger claim, you need a review that supports it. Do not add one because it sounds tidy.
If the draft mentions the checks you ran, keep that sentence. Then keep fixing the list the scan gave you.
A sensible order
Scan the store first so the known issues are real. Draft the statement second. Edit the contact line and the issue list third. Publish fourth. Rescan when the theme changes and update the page.
Agencies can draft this for a client from the white-label report, then let the client publish it on the client domain. The contact email should be the client's, unless you have agreed to take the reports.
If you only have ten minutes, run the free scan, generate the UK draft, and put a real email in it. That is a better public page than a widget icon with no statement at all. Link the page from the footer so people can find it from any template. Update the date when you next publish a fix. Keep the old date in your notes if a customer asks what changed.
Questions
Is the draft free?
Yes. Leave an email and we send the text. Paid plans include the same draft with the audit.
Can I publish it unchanged?
Edit the name, the URL, the contact email and the known issues first. Then publish.
Does this replace a scan?
No. The statement describes the work. The scan finds the issues. Automated scans cannot catch every WCAG issue.