Accessibility statement template for a small business website

An accessibility statement is a short page on your website that says which standard you aim for, what you have tested, which known problems remain, and how to reach a person if something does not work. This accessibility statement template is written for a small business: copy it, replace the bracketed parts with true facts, link it from your footer, and update the date each time you recheck. Below the template are the rules for filling it in honestly, the mistakes that make a statement worse than none, and examples for a restaurant and a clinic.

Do not want to write it yourself? Site Record includes a statement page built from your own test results, ready to link from your footer, with monthly rechecks for a year: $499 once. See the Site Record page.

The template (copy and edit)

Accessibility statement for [Business name]

[Business name] wants everyone to be able to use our website,
[address, e.g. www.example.com].

Standard we work toward
We aim to follow the Web Content Accessibility Guidelines (WCAG)
2.1, level AA.

What we have done
On [date] we tested [number] pages of this site with automated tools
([tool names, e.g. axe]) and by using the keyboard alone. We fixed
[number] issues, including [two or three plain examples, e.g. low-contrast
text, missing image descriptions].

Known limits
- [e.g. Our online ordering page is provided by another company and
  we are asking them to fix [specific issue].]
- [e.g. Older PDFs of our menu may not work well with screen readers.
  Ask us and we will send the menu as plain text.]
Automated tests find only part of what the guidelines ask, so some
problems may remain.

Tell us if something does not work
Email [address] or call [phone]. Tell us the page and what went wrong.
We will reply within [number] business days and offer another way to
get what you need, such as an order by phone.

Last reviewed: [date]

What each part of an accessibility statement does

The standard

Naming WCAG 2.1 AA tells visitors and web people what you measure yourself against. Say "aim to follow", not "comply with", unless you have had a full manual audit that says so.

What you tested and when

A date and a number of pages make the statement checkable. A statement with no date reads as marketing. A vague "we are committed to accessibility" with no facts says nothing.

Known limits

This is the part owners most want to skip, and it is the part that builds trust. List real problems: a booking widget from another vendor, old PDFs, video without captions. Pair each with what you do instead.

A way to reach a person, and a promise you can keep

Give an email address and a phone number, and a reply time you will actually meet. A contact form alone can itself be an accessibility barrier, so offer an email address too.

The review date

Update it after each recheck. A statement last reviewed three years ago suggests nobody is looking.

Is an accessibility statement a legal requirement?

For most US private businesses, no law we know of requires one by name. Some other countries and some public bodies do require statements. A statement does not make a site compliant and does not stop a complaint. It does show visitors you care, give them a contact route before they take another step, and put your testing on the record with a date. We are not lawyers; ask yours about your situation.

Example 1: a restaurant statement (filled in)

Accessibility statement for Harbor Street Kitchen

We want every guest to be able to read our menu and order online.

We aim to follow WCAG 2.1 level AA. On 2026-11-10 we tested our home,
menu, contact and order pages with axe and with the keyboard alone. We
fixed 14 issues, including faint grey menu prices and photos with no
descriptions.

Known limits: our online order checkout is run by our ordering partner
and we have asked them to label the tip buttons. Our printed menu PDF
is an image; the same menu is on the Menu page as text.

Need help? Email hello@harborstreetkitchen.example or call 555-0100.
We reply within 2 business days, and you can always order by phone.

Last reviewed: 2026-11-10

This is an invented example to show the shape; use only your own facts.

Example 2: a clinic statement (filled in)

Accessibility statement for Lakeside Family Dental

We want every patient to be able to book and read about care online.

We aim to follow WCAG 2.1 level AA. On 2026-11-12 we tested 8 pages
with automated tools and a keyboard walk and fixed 9 issues, mostly
unlabelled form fields and low-contrast buttons.

Known limits: our patient portal is provided by another company; we
have reported its issues to them. Call us to book or to get forms by
email in a text format.

Contact: info@lakesidedental.example, 555-0142. Reply within 1 business day.

Last reviewed: 2026-11-12

Also invented, for the layout only.

Wording swaps: say it plainly and truthfully

Instead of	Write	Why
"Our site is fully accessible."	"We aim to follow WCAG 2.1 level AA and tested 8 pages on 2026-11-12."	It states a goal and a fact you can prove
"We are committed to accessibility."	"We fixed 9 issues this month, listed below."	Commitment is shown by work, not adjectives
"Contact our webmaster."	"Email hello@yourdomain or call 555-0100."	A real route that works without the site
"Some content may not be accessible."	"Our menu PDF is an image; the same menu is on the Menu page as text."	Specific limits with an alternative
"We are ADA compliant."	"Automated tests find part of what the guidelines ask, so some problems may remain."	Avoids a promise you cannot keep

Accessibility statement template for WordPress, Shopify and other platforms

The same accessibility statement template works on any platform. What changes is how you publish it. On WordPress, create a page called Accessibility, paste the text, and add it to the footer menu under Appearance, Menus. On Shopify, add a page under Online Store, Pages, and link it in the footer menu under Navigation. On Wix, Squarespace and GoDaddy, add a normal page and link it in the footer section. Use headings for the section titles, not bold text, so assistive software can jump between them, and write links with words that make sense alone ("email us", not "click here").

What to put under "known limits" if you do not know yet

Run your first scan before you write the statement. If you have not tested, do not publish a statement that implies you have. Scan four pages, list the top errors that you cannot fix straight away, and write them in plainly. A short, honest list of three limits reads better than a long page of reassurance. If the scan finds nothing you cannot fix, say what you tested and leave the limits as the standard sentence that automated tests find only part of what the guidelines ask.

Where to put the statement

A page at an address people can guess, such as /accessibility.
A link in the footer on every page, with the words "Accessibility" or "Accessibility statement".
A link from your contact page.
Plain text on the page itself, not a PDF, so it is readable with any tool.

Mistakes that make a statement worse than none

Claiming full compliance. A page saying "our site is fully ADA compliant" invites a challenge, because a scanner may find errors the next day.
Copying another company's statement. Their tests are not yours. A copied list of limits is false for your site.
No contact route. A statement with no way to reach you adds nothing.
Never updating it. If you rescan, update the date and counts.
Hiding it. A link only in the sitemap does not help anyone.
Putting it behind an overlay. A statement written by a widget's generator may describe features of the overlay rather than your code; see accessiBe alternatives.

How to keep the statement true

Run a free scan (see free website accessibility checkers) on your main pages each month.
Fix what you can; list what you cannot.
Update the counts and the date in the statement.
Keep the old versions. A dated history shows steady work.

If you pay for a professional check, see website accessibility audit cost for what to expect.

Frequently asked questions

What should an accessibility statement include?

The standard you aim for, what you tested and when, known limits, a contact route and a review date.

Is there a free accessibility statement generator?

Yes, several, including one from the W3C's Web Accessibility Initiative for public bodies. Whatever tool you use, replace each placeholder with a true fact; a generator cannot know what you tested.

Does a statement protect me from a lawsuit?

No. It can show good faith and a dated record, but it does not replace fixing errors. Speak with an attorney about any claim.

Where should the link go?

In the footer of every page, so visitors can find it from anywhere.

Can I say my website is WCAG compliant?

Only if a full audit by a qualified tester supports it. For most small sites, "aim to follow" plus what you tested is the honest wording.

How often should I update it?

After each recheck, and at least every few months.

Need a statement built from real test results? Site Record includes one. More: all accessibility guides.

Keep your statement honest by backing it with real checks: the ADA compliant website checklist lists 25.

Prefer a form? See accessibility statement generator options.

Sources

W3C Web Accessibility Initiative, accessibility statements guidance and generator.
W3C, Web Content Accessibility Guidelines 2.1.
Google suggest searches for "accessibility statement" and "is an accessibility statement a legal requirement", 2026-11-14.