Free tool

Accessibility statement generator

Answer a few questions and get a complete accessibility statement you can publish today. No account, no card, nothing to install, and it works with JavaScript switched off because the whole thing is built on the server.

An accessibility statement is the page a customer, a procurement form or a public body asks for when they want to know where you stand. Writing one from scratch is an afternoon. Writing one that overclaims is worse than having none at all, which is why this generator will not produce a claim of full conformance for you.

Your answers

Organisation name

Exactly as you want it to appear in print.

Website address

The domain on its own is fine. We add https:// for you.

Email address for accessibility problems

This is printed in the statement, so use an address somebody actually reads. A shared inbox is better than a person who might leave.

Standard you are aiming at

WCAG 2.2 level AA is the sensible default. Pick EN 301 549 if you sell into European public procurement or are working to the European Accessibility Act.

Where you honestly stand

There is no "fully conformant" option here, and that is deliberate. Full conformance is a claim about every success criterion on every page, which no form can check on your behalf. If you have had a full evaluation done and it says that, write the sentence yourself and name the evaluator.

How you checked

All three of these are still a self-assessment, and the statement says so. If an independent specialist audited the site, add that yourself with their name and the date of their report.

Date you last reviewed the site

Format YYYY-MM-DD if your browser shows a plain text box. This becomes the date of the self-assessment in the statement, so it needs to be a day you really looked.

Known problems (optional)

One per line. For example: "PDF price lists published before 2024 are not tagged" or "the booking calendar cannot be operated with a keyboard alone". Leave it blank if you have not recorded any yet and the statement will say that plainly, which is honest and is better than an empty promise.

Nothing you type here is stored. The statement is written in memory, sent back to your browser, and forgotten. There is no account to create and no email required.

What comes out

The statement you get

Six short sections, in the order most readers and most procurement forms expect them: who the statement covers, the conformance status, how the site was assessed, the known problems, how to report a new one, and when the statement was prepared. Plain text you can paste into any content management system, or download as a file.

What it will never say

That your site is compliant with the ADA, the Equality Act or any other law. A statement cannot make that true and publishing it does not make you safer.
That your site fully conforms to WCAG. That is a claim about every criterion on every page, and this form has not seen your pages.
That automated testing checked everything. It says out loud that automated testing reaches roughly 30 to 40 percent of WCAG success criteria, because a reader who later finds that out on their own will stop believing the rest of the page.

Three things to check before you publish

Some jurisdictions require the statement to name an enforcement or complaints procedure, and public sector bodies in the UK and the EU have specific wording rules. Check what applies to you and add it.
Put it at a stable address, usually /accessibility, and link it from the footer of every page. A statement nobody can find does no work.
Diary a review. A statement dated two years ago tells a reader that nobody has looked since, which is the opposite of what you wanted it to say.

Questions

Things people ask about this

Is an accessibility statement legally required?

It depends entirely on who you are and where you operate. Public sector bodies in the UK and across the EU have published statement obligations with prescribed content. Private businesses in the United States generally do not have a statutory statement requirement, although one is often asked for in procurement and in the correspondence that follows a demand letter.

We are not a law firm and this is not legal advice. Check your own obligations, because they vary by country, by sector and by contract.

Why will it not let me say I am fully conformant?

Because a form cannot verify it, and a statement is only useful while people believe it. Full conformance means every success criterion is met on every page in scope, confirmed by evaluation. If that is genuinely your position, you will have an evaluation report to cite, and you should write the sentence with the evaluator's name in it.

Does listing known problems make me a target?

It is a fair worry and worth asking your lawyer about. The practical argument the other way is that the problems are already visible to anyone who tests the site, and a dated list showing you found them and are working through them reads very differently from a site that claimed everything was fine.

You choose what goes on the list. Nothing here forces you to publish anything.

Do you keep what I type?

No. There is no database write on this page. Your answers are used to compose the text and then discarded when the response is sent. Ordinary web server request logs exist, as they do everywhere, and they record the request rather than the contents of your form.

What does this cost, and what is the catch?

It is free and there is no catch worth hiding. We built it because people who need an accessibility statement usually also need to know what is actually wrong with their site, and that is what we sell. If you use the generator and never buy anything, the tool still did its job.

The limits of this

Automated testing detects roughly 30-40% of WCAG success criteria. It cannot determine whether a site is legally compliant, and it is not a substitute for manual review and assistive-technology testing. This report is a record of what automated checks found on the date shown - nothing more, and nothing less.

A statement describes where you stand. It does not change where you stand, and it is not legal advice. If you want to know what is actually broken on the page before you publish anything, scan it first.

Run a free scan on one page