Accessibility statement

Accessibility statement generator

An honest statement of your goals, what you have tested and how people can tell you about a barrier.

Hand-painted illustration: a paper-document character holding a green umbrella over a small cottage on a floating island.

Free template page. Updated 20 November 2026.

What a accessibility statement is for

An accessibility statement tells visitors what you do to make your site usable by people with disabilities, which standard you aim for and how to report problems. Some laws require one, and it helps users even where none does.

Who needs one

Public bodies, many EU businesses under accessibility law, online shops and anyone who wants to show they take access seriously. It must be truthful: do not claim more than you have done.

What your accessibility statement covers

Your commitmentA short and honest goal, such as aiming for WCAG 2.2 level AA.
Current statusPartly, fully or not yet conforming, and what is known to be wrong.
What you have testedTools, assistive technology and dates.
Known limitsContent you cannot fix yet and the reason.
Feedback routeAn email and a response time.
Date preparedWhen you last reviewed the statement.

What the wizard asks you

These are the kinds of questions. Each one explains why we ask it, and you can skip what does not apply.

  1. Question 1Which standard do you aim for?
  2. Question 2Have you tested the site, and how?
  3. Question 3What known issues remain?
  4. Question 4How can people report a barrier?
  5. Question 5When did you last review it?

A sample clause

Your real text is built from your answers. This is an example of the plain style we aim for, with the parts you fill in shown in brackets.

Sample: feedback
We aim to meet WCAG 2.2 level AA. If you find something on this site that you cannot use or read, please email [email] with the page address and what went wrong. We will reply within [5] working days and tell you what we plan to do.

Sample text for illustration. Your page is written from your own answers.

Mistakes we see most

  • Claiming full compliance without testing. Be specific about what you checked.
  • Using an overlay widget as proof of accessibility. Overlays do not replace fixing the site.
  • Not responding to reports. A feedback route is only useful if someone reads it.

Questions

Is an accessibility statement legally required?
In some places for some organisations, such as public bodies and certain businesses in the EU. In others it is good practice.
Does a statement make my site accessible?
No. It describes your effort. The work is in building and testing the site.
Which standard should I choose?
WCAG 2.2 level AA is the usual target and what most laws point to.
Can Termsquill test my site?
Not at launch. We write the statement from your answers and point you to free testing tools.
Hand-painted illustration: a paper-document character at a round wooden door holding up a brass key.

Be first through the door.

Join the waitlist. One email when the free plan opens, and nothing else.