Website accessibility statement examples you can adapt for a small business
Good website accessibility statement examples share five parts: what you aim for, the standard you test against, what you know is not yet fixed, how to reach a person, and the date of your last check. Below are four plain examples for a small business, written for different situations, followed by what each part has to say and the claims to leave out. Copy the one that is closest to the truth about your site and change it until every sentence is something you can prove. We are not lawyers, and a statement does not protect you from a complaint on its own.
What website accessibility statement examples have in common
Look at published statements, from the UK government's sample for a fictional public-sector site to the pages large companies link from their footers, and the same pieces recur: a commitment, the standard, the current state, known limits, a contact route and a date. The UK sample is based on a model statement that is the minimum legal wording for public bodies there, and it says your statement must be specific to your own website. In the United States, private businesses have no required wording. That makes the specific parts, not the polite ones, the only parts that matter.
- A short commitment. One sentence, in your words.
- The standard. Usually WCAG 2.1 Level AA, the checklist most settlements and guidance point to. See our WCAG 2.1 AA checklist for what it contains.
- The current state. Fully, partly or not yet meeting it, in plain words.
- Known problems. Specific pages or features, and when you will fix them.
- A contact route. An email address a person reads, a response time and an alternative way to get what the page offers.
- A date. When you last tested, and how.
Example 1: a small service business that has fixed its errors
Use this when a recent scan and a keyboard test found nothing serious.
Accessibility statement for Harbor Plumbing We want everyone to be able to use our website, including people who use screen readers, keyboards or magnification. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We last tested our site on 12 November 2026 with an automated scanner and by using each page with a keyboard only. We found no errors in the pages we tested: home, services, booking form and contact. If something on our site does not work for you, email access@example.com or call 555-0100. We reply within 2 business days, and we can take a booking by phone or email instead of the online form. Last updated: 12 November 2026.
Replace the name, the pages, the dates and the contact details. If you did not test with a keyboard, delete that sentence. The strength of this example is that it names what was tested.
Example 2: a site with known issues and a fix date
This is the most useful of the website accessibility statement examples for owners who have just scanned and found work to do. It admits the gaps, which makes it more believable than a promise of perfection.
Accessibility statement for Maple Street Bakery We are working to make our website usable by everyone. We aim to meet WCAG 2.1 Level AA and we test against it. Where we are now: partly meeting. Our last check, on 12 November 2026, found these problems: - Photos on the menu page do not all have descriptions. We expect to add them by 12 December 2026. - The pickup time picker on the order page cannot be used with a keyboard. Until it is fixed you can order by phone on 555-0100 or by email at orders@example.com. - Some older PDFs of the menu are not readable by screen readers. A text version is on the menu page. Contact: access@example.com. We read every message and reply within 2 business days. Last updated: 12 November 2026. We will update this page when the work above is finished.
Notice the alternative route for the one barrier that stops a task. If a visitor cannot book through your form, a phone number is the difference between a statement that helps and one that does not. Only promise a date you will keep.
Example 3: an online shop on Shopify or WordPress
Accessibility statement for North Pine Goods We want every customer to be able to browse and buy from our shop. We test our own pages against WCAG 2.1 Level AA. What we have checked: the home page, collection pages, product pages and cart, on 12 November 2026, with a free scanner and a keyboard. What we cannot fully control: our payment page is provided by Shopify, and some product videos come from a supplier without captions. We have asked both to improve and we offer help by email or phone to anyone who cannot complete an order. Contact: help@example.com or 555-0100. Replies within 2 business days. Last updated: 12 November 2026.
The line about what you cannot control is accurate and fair. It is also a reminder that third-party parts such as the checkout and embedded booking tools are tested separately; our Shopify guide shows what Shopify covers.
Example 4: a site built by an agency
Accessibility statement for Redwood Dental Our website was built by an outside agency. We asked them to follow WCAG 2.1 Level AA, and we recheck the site every quarter. Last check: 12 November 2026. We found two issues: low contrast on the grey footer text and a missing label on the newsletter field. Both are scheduled for 30 November 2026. If you have trouble using any page, email access@example.com. We will help you directly and tell you when the problem is fixed. Last updated: 12 November 2026.
If an agency made the site, keep a copy of what you asked them to deliver. Accessibility is much easier to fix at the contract stage than after a complaint.
What website accessibility statement examples should never say
- "Our website is fully ADA compliant." Nobody can certify that, and you cannot prove it. Say what you tested.
- "WCAG 2.1 AAA." The top level is not achievable for whole sites and no standard asks it.
- "This site is accessible thanks to our overlay." A toolbar does not prove conformance. FTC action in January 2025 against accessiBe concerned claims that a tool could make any site WCAG compliant.
- A generated page nobody read. Our guide to accessibility statement generators shows what to check in their output.
- No contact route. A statement with no way to report a problem is decoration.
- Old dates. A statement from 2022 on a redesigned site is worse than none.
Where to put the statement and how to keep it true
Link it from the footer of every page with the words "Accessibility statement", because people look for it there. Give it its own address such as /accessibility. After each redesign, new plugin or template change, rescan, update the date and the known-issues list. If a visitor writes to you, answer within the time you promised and, where the problem is real, add it to the list.
Our accessibility statement template has a blank version of these examples to fill in section by section.
Do I need an accessibility statement?
For most small US businesses no law says you must publish one. It is still worth doing: it gives people a route to tell you about a barrier, and it shows that you take it seriously, which matters if a customer or a lawyer reaches out. Public bodies in some countries must publish one in a set form, and the EU's accessibility rules ask for one from some businesses that sell to EU consumers; check your own situation.
Frequently asked questions
What should a website accessibility statement include?
A commitment, the standard you test against, what you found, known problems with dates, a contact route and the date of your last check.
Can I copy another company's accessibility statement?
Copy the structure, not the claims. Their statement describes their site, not yours.
Is there a free accessibility statement generator?
Yes, the W3C offers one and several vendors do. Edit the result so every line matches your site.
Where do I put my accessibility statement?
On its own page, linked from the footer on every page.
How often should I update it?
After each redesign or significant change, and at least once a year.
Does a statement protect me from a lawsuit?
No. It shows effort and gives people a way to contact you. Only fixing the problems reduces them. Speak to an attorney if you receive a demand letter.
Sources
- UK government, sample accessibility statement for a fictional public sector website (gov.uk).
- W3C Web Accessibility Initiative, Developing an Accessibility Statement.
- Accessible Web, exemplary accessibility statements; Equalize Digital, how to write an accessibility statement (read 2026-11-15).
- FTC, order against accessiBe, January 2025.