Tool

Accessibility statement generator

Fill in the boxes and copy a plain-English statement for your website; it's made in your browser and nothing is sent to us.

As people know it, like "Town of Wrenfield".

Your home page, like "yourtown.gov".

Towns, counties, public libraries and public schools get a line about the ADA rule for state and local governments.

The standard you aim for WCAG is the international rulebook for websites people with disabilities can use. Not sure? Keep 2.1 AA.

One a line, in everyday words, like "Meeting minutes before 2024 are scanned PDFs that screen readers can't read."

How people can tell you about a problem At least one. Use an inbox or phone someone checks every working day.

Pick one you can keep on a busy week.

Usually today. Look at it again at least once a year.

Your statement

Your accessibility statement changes as you type. Gaps in brackets still need filling in.

Copy as text for an ordinary page editor (WordPress, Squarespace, Wix and most website builders). Copy as HTML for a code or HTML view: it has headings, a list and working email and phone links.

Put it on your website

  1. Make a page called "Accessibility" and paste the statement in.
  2. Link to it from the footer of every page, with the same words each time, so people can find it from anywhere.
  3. Send a test message to the email address and ring the number, to make sure someone answers.
  4. Read it again at least once a year, and whenever you fix one of the problems listed. Change the date when you do.

Before you publish

  • It's a template, not legal advice. Read every line and change anything that isn't true for you. If you have an attorney, show it to them.
  • A statement doesn't make a website accessible, and it doesn't make it meet the ADA. Fixing the problems does. The statement tells people what you're aiming for and how to reach you when something gets in their way.
  • Only list a problem you know about, and only promise a reply time you can keep. An honest list of problems is more use to people than none.
  • Find problems to list with our free Accessibility Check, then fix what you can before you publish.
  • What the law asks: the ADA rule for town, city and county websites (WCAG 2.1 AA by April 26, 2027 or April 26, 2028) and ADA website rules for small businesses. New to WCAG? WCAG explained.

What's in it, and why

Our commitment
That you want people with disabilities to be able to use your website. The W3C, which writes WCAG, says every statement needs this.
The standard
Which version of WCAG you aim for, so your web person knows what to check against.
Known problems
What doesn't work yet, in everyday words, and that people can ask for it another way. The ADA rule says governments may still need to give people what they need in a way they can use.
Tell us about a problem
Email, phone or mail, and how soon you'll reply. The Department of Justice says a way to report problems helps website owners fix them.
Last reviewed
A date shows the statement is looked after. The W3C suggests reviewing it at least once a year.

Check the official rules. Rules and dates change, so check them with the official sources before you rely on them: ADA.gov (the US Department of Justice), the W3C's WCAG pages and Section508.gov. PageKiwi helps you find problems and get closer to meeting the rules. It can't promise a website meets them, it isn't legal advice, and we can't take responsibility for decisions made from it.

Quick question

Did you find the tool you needed?