Free Accessibility Tool

Free Accessibility Statement Generator

Produce a credible, WCAG-referencing accessibility statement for your site in two minutes — copy the HTML or plain text.

  • W3C/WAI structure
  • Honest conformance language
  • Copy HTML or text
  • Runs in your browser

Statement Generator

Your accessibility statement

How to use the Statement Generator

  1. Fill in your details. Add your organization name, website, conformance target, and a feedback contact.
  2. Set an honest status. Choose partially or fully conformant — partially conformant is the safe, defensible default.
  3. Add known limitations. List anything not yet fully accessible (optional but credible).
  4. Copy your statement. Copy it as clean HTML or plain text and publish it at a stable URL like /accessibility/.

How to use your statement

Fill in the fields and the statement updates live. The default status is "partially conformant" on purpose — it's the honest, defensible choice for most sites, and it pairs a real commitment with a feedback channel. Only claim full conformance if a recent audit supports it.

Copy the statement as clean HTML (ready to paste into a page) or as plain text. Publish it at a stable URL like /accessibility/, link it from your footer sitewide, and keep the date current.

A statement is a promise, not a shield

An accessibility statement signals good faith and gives users a way to reach you — both genuinely valuable. But it is not a substitute for conformance, and an inaccurate statement can undercut you. The strongest position is an accurate statement backed by real remediation and, for procurement, a VPAT.

Frequently asked questions

Does an accessibility statement make me ADA compliant?

No. A statement documents your commitment, conformance status, and a feedback channel — it's good practice and expected, but it doesn't substitute for actually conforming. Publishing a statement that overstates your conformance can even backfire. Pair it with real remediation.

What should an accessibility statement include?

Following the W3C/WAI model: your commitment, the conformance target (e.g., WCAG 2.1 AA) and current status, known limitations, how to give feedback or request help, and the date. This generator produces all of those sections.

Should I claim 'fully conformant'?

Only if a recent audit supports it. Most honest statements say 'partially conformant' — meaning some content doesn't yet fully meet the standard. Overclaiming is risky; an accurate, good-faith statement with a feedback channel is stronger.

Where do I put the statement?

Link it from your footer on every page (commonly at /accessibility/) so it's easy to find. Keep the date current and update it after significant changes or audits.

A scan is the start, not the finish

Automated tools catch only 30–40% of WCAG issues. Get a free human-led scan and a real remediation plan that makes your site defensibly compliant.