gotalt?

Accessibility statement generator

Fill in a short form. Get a plain-text draft accessibility statement you can review, edit and publish. It runs entirely in your browser — nothing you type is sent anywhere.

Free · No signup · Not legal advice

The W3C already built the real thing

The W3C's accessibility statement generator is the authoritative tool for this: it's free, more thorough than what's below, and maintained by the people who write the standard. Use it if you want every optional section covered. This page exists as a faster path through the common case — one site, one statement, a handful of fields — not a replacement.

What this tool actually does

It takes the fields above and drops them into a plain-text template modelled on the W3C's own statement structure: a commitment paragraph, a conformance status, known limitations, a feedback route, and an assessment-approach note. It does not test your site, does not know whether your claims are true, and does not check your work. Only you can say whether "fully conformant" is accurate — see the warning above.

How to use it properly

  1. Test the site first

    Run a free scan, a deep audit, or a manual pass with a screen reader and keyboard. Write down what you find before you write the statement, not after.

  2. Fill in the form honestly

    List real known issues in plain language — "the search filter can't be operated by keyboard" is more useful to a reader than silence.

  3. Edit the draft

    The generated text is a starting point. Add a real response-time commitment, your actual testing methods, and remove anything that doesn't apply to your site.

  4. Publish and link to it

    Put it on its own page, link to it from your site footer, and put a review date in your calendar — a statement that's two years out of date is worse than none.

Questions

What is an accessibility statement, and do I need one?

It's a published page telling visitors what accessibility standard you're aiming for, how well you currently meet it, and how to report a problem. The EAA, and several national laws that reference EN 301 549, expect one for covered services; even where it isn't strictly required, it's good practice and gives disabled users a route to report barriers instead of just leaving. See the W3C's guidance on accessibility statements for the full picture. This isn't legal advice — check what applies in your jurisdiction.

Should I select "Fully conformant"?

Only if you mean it. "Fully conformant" is a statement that you tested against every WCAG success criterion at your target level and found nothing outstanding — it is not an external certification and nobody is checking it for you before it goes live. If you haven't run a real audit yet, choose "Partially conformant" and list what you know is broken. That's more honest, and it's what most real sites should say.

Is this legal advice?

No. This tool and this page are not legal advice. Accessibility law varies by country and by what your organisation does — see our guides on the EU's EAA and the ADA Title II deadline for background, but talk to a lawyer for anything that depends on your specific situation.

Why not just use the W3C's generator?

You should consider it — it's free, official, and covers more ground than this page does (multiple contact methods, evaluation reports, formal complaints procedures, and more). We built this as a quicker version for the common case: one organisation, one site, a handful of known issues. If your situation is more complex than that, the W3C tool is the better starting point.

Does this store what I type?

No. Everything happens in JavaScript running in your browser. Nothing you enter is sent to a server, saved, or logged — close the tab and it's gone.

Can I edit the statement after it's generated?

Yes, and you should. The output box is plain text — copy it into whatever you're publishing with (your CMS, a static page, a Word document) and edit freely. Nothing about the generated wording is fixed or needs to match verbatim.

A statement is only honest if it's true

Before you publish "fully conformant" anywhere, it's worth finding out what's actually still broken. The free scan checks 16 common issues across up to three pages in under a minute.

Scan my site — free