WCAGGuard

Free tool · No account needed

Free Accessibility Statement Generator

Answer a few questions and get a clear, honest accessibility statement for your website, including any known issues and how people can reach you. Copy it, download it, or email yourself a copy. Free.

Your details

How well does your site meet it today?
One per line, in plain words. For example: "Some product videos don't have captions yet. We're adding them by March 2027."
For example: "The chat widget is provided by another company."
What you do to support accessibility (choose any that are true)
How was the site assessed?

Contact for accessibility problems

Your statement

We only use this address to send you the statement.

Need the full VPAT report or an expert audit?

A statement tells people where your site stands. Buyers and procurement teams often also ask for an Accessibility Conformance Report (VPAT), and the fastest way to fix problems is an expert review.

VPAT generator ($79 report) Accessibility audit service

What makes a good accessibility statement

  • It's honest. Say which standard you aim for and how close you are. If there are known issues, list them in plain words, with a workaround or a date for a fix.
  • It's easy to act on. Give an email or phone number, and say how quickly you'll reply. Someone who can't use a page needs another way to get help.
  • It's dated. Show when the statement was written and last reviewed, and update it when things change.
  • It's easy to find. Put it on its own page and link to it from your footer.

This generator follows the structure recommended by the W3C Web Accessibility Initiative. It never describes your site as fully conforming unless you choose that option.

Questions

Is this accessibility statement generator free?

Yes. You can generate, copy, download and email your statement for free, with no account.

What should an accessibility statement include?

Which standard you aim for (usually WCAG 2.2 Level AA), how well your site meets it today, any known issues and workarounds, what you're doing to improve, and how people can contact you if something doesn't work for them.

Should my statement say my site fully conforms?

Only if that's true, without exceptions, and you've tested it. If you know of any issues, say the site partially conforms and list them. Overstating accessibility in a public statement can cause more trouble than an honest list of known issues.

Where should I put the statement?

On its own page, linked from your site's footer, usually called "Accessibility".

How often should I update it?

Whenever you fix known issues or make major changes, and at least once a year. The statement includes the date it was last reviewed.

Does publishing a statement make my site accessible?

No. A statement explains where your site stands and how people can get help. The site itself still needs testing and fixes.

Not legal advice. A statement describes your site; it doesn't make it accessible or meet any law on its own.