- accessibility statement
- WCAG
- small business
- how-to
How to Write a Website Accessibility Statement (With a Template)
What a website accessibility statement is, what W3C says to include, and a fill-in template that stays honest about what you have actually tested.
On this page
An accessibility statement is a short page on your website that tells visitors what you are doing to make your site usable for people with disabilities, and how to reach you if something doesn't work.
It is one of the easiest accessibility tasks on your list. It doesn't require code changes, and you can write it in an afternoon. This guide explains what to include, what to avoid, and gives you a template you can adapt.
This is not legal advice. An accessibility statement does not make a website accessible or compliant, and it does not prevent a legal claim. If you have received a demand letter, talk to an attorney before you publish or change one.
What an accessibility statement is (and isn't)
The W3C's Web Accessibility Initiative publishes guidance on accessibility statements. It describes them as a way to show your users that you care about accessibility, share information about your site's accessibility, and demonstrate your commitment.
It is just as clear about what a statement is not. W3C says accessibility statements "are not technical assessments or declarations of conformity." In other words, the statement describes your efforts. It is not proof that your site meets a standard.
That distinction matters. A statement that claims more than you have verified can mislead the very visitors it is meant to help.
Why bother with one?
- It gives visitors a way to tell you about problems. The Justice Department's web accessibility guidance says: "Websites that provide a way for the public to report accessibility problems allow website owners to fix accessibility issues."
- It sets honest expectations. If part of your site has a known problem, saying so (with a workaround) saves visitors frustration.
- It keeps you accountable. Writing down your goal and your next steps makes it more likely the work actually happens.
What W3C says to include
According to W3C's statement guidance, a statement should include at least:
- A commitment to accessibility for people with disabilities
- The accessibility standard you are working toward, such as WCAG 2.1 or WCAG 2.2 Level AA
- Contact information for people who run into problems
W3C also suggests these optional parts:
- Known limitations, so visitors know what to expect
- Measures you take to support accessibility
- Technical requirements, such as which browsers your site supports
- Environments where the site was tested
- References to applicable laws or policies
The most important rule: don't claim what you haven't checked
The biggest mistake small businesses make is copying a statement that says something like "This website is fully compliant with WCAG 2.1 AA." Unless a qualified person has actually evaluated your whole site against every success criterion, you don't know that.
Instead, describe the standard you are working toward, what you have actually done, and what you know is still broken. Honest phrases look like this:
- "We are working toward WCAG 2.1 Level AA."
- "We ran an automated scan on [date] and are fixing the issues it found."
- "We know our online booking form is hard to use with a keyboard. Until it's fixed, you can book by phone."
Avoid phrases like "fully compliant," "100% accessible," or "certified accessible" unless you have documented evidence for them. Also remember that automated scans, including ours, cannot detect every accessibility problem. W3C notes that human judgment is required to evaluate accessibility, so a clean scan is not a conformance claim.
Accessibility statement template
Copy this, replace everything in [brackets], and delete any line that isn't true for your business. Keep the language plain.
Accessibility Statement for [Business Name]
Our commitment
[Business Name] wants everyone, including people with disabilities,
to be able to use our website. We are working to improve the
accessibility of [website address] on an ongoing basis.
The standard we are working toward
We are working toward the Web Content Accessibility Guidelines
(WCAG) 2.1 Level AA, published by the W3C. We have not yet had a
full independent evaluation, and we do not claim that every page
meets this standard today.
What we have done so far
- [Example: Ran an automated accessibility scan on [date] and began
fixing the issues it found.]
- [Example: Added text descriptions to product images.]
- [Example: Checked that our main menu works with a keyboard.]
Known limitations
- [Example: Some older PDF menus may not work well with screen
readers. Call us and we will read you the menu or send it in
another format.]
- [Example: Our third-party booking widget is not fully keyboard
accessible. You can book by phone at [phone number].]
Tell us about a problem
If you have trouble using any part of this website, please let us
know. We will do our best to help and to fix the problem.
- Email: [email address]
- Phone: [phone number]
- Mail: [mailing address]
We aim to respond within [number] business days.
This statement was last reviewed on [date].
A few notes on the template:
- The "we do not claim" line is intentional. Remove it only if you have a documented evaluation showing your site meets the standard, and then say who did it and when.
- The response time is your choice. Pick a number you can actually meet.
- The review date is optional (W3C doesn't require one), but it shows visitors the statement isn't stale. Update it whenever you change the page.
If you'd rather fill in a form, W3C offers an online accessibility statement generator. Apply the same rule there: only select options you have actually verified.
Where to put it
- Add a link labeled "Accessibility" to your site footer so it appears on every page.
- Make sure the statement page itself is accessible: real headings, readable contrast, and a contact email that is a working link.
- Check that the contact methods work. An email address nobody reads defeats the purpose.
What to do when someone uses it
When a visitor reports a problem:
- Reply promptly and thank them.
- Offer an immediate workaround, such as taking the order by phone.
- Log the problem, fix it, and note the date it was fixed.
- Update the "known limitations" section if needed.
That record of reports and fixes is useful on its own, and it is the kind of documentation an attorney may want to see if you ever receive a demand letter.
A statement is the start, not the finish
The statement describes your accessibility work. The work itself is fixing the real barriers on your site. Two good places to start are The 10 Most Common Website Accessibility Problems (and How to Fix Them) and WCAG 2.1 AA Explained for Small Business Owners.
To fill in the "What we have done so far" section honestly, run a free scan of your homepage. You'll see which detectable problems show up, with a plain-English explanation of each.
If your statement is being written because a demand letter arrived, read Got an ADA Website Demand Letter? What Small Business Owners Should Do First and see the Demand Letter Response Kit, which includes a dated PDF report you can share with your attorney.