Resource · v1.0
Accessibility Statement Template
A plain-English accessibility statement that meets W3C guidance without overpromising. Word-for-word draft, commentary, and publishing guidance.
Published by Startvest LLC · Updated April 17, 2026
Why this template exists
An accessibility statement is a public page on your website that describes your accessibility commitment, your conformance target, your known limitations, and how a user can report a problem.
Publishing one is part of a good-faith ADA compliance effort. Publishing one that is vague, boilerplate, or overpromising is worse than publishing nothing — it becomes an admission against interest if a demand letter arrives.
This template uses W3C-recommended structure, adapted for small businesses. Fill in every bracketed field. Do not leave brackets in the published version.
The template
Copy everything between the horizontal rules into a new page at
/accessibilityon your website.
Accessibility Statement for [Your Business Name]
Last updated: [Date]
[Your Business Name] is committed to providing a website that is accessible to the widest possible audience, regardless of ability. We are actively working to increase the accessibility and usability of our website and in doing so adhere to many of the available standards and guidelines.
Conformance status
We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible for people with disabilities. Conformance with these guidelines helps make the web more user-friendly for everyone.
Our website is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
Compatibility with browsers and assistive technology
Our website is designed to be compatible with recent versions of the following browsers:
- Chrome
- Firefox
- Safari
- Edge
We have tested our content with the following assistive technologies:
- [List the assistive technology you have actually tested with. For example: NVDA screen reader on Windows, VoiceOver on macOS, JAWS on Windows. If you have not tested with any, remove this section rather than listing technologies you have not actually used.]
Known limitations
Despite our best efforts to ensure accessibility of [your website URL], there may be some limitations. Below is a description of known limitations. Please contact us if you observe an issue not listed below.
-
[List known limitations. Example: some older PDF documents predating 2023 are not fully accessible and are being reviewed as part of our remediation plan. If you need an accessible version of a specific document, please contact us.]
-
[Another known limitation if applicable.]
-
[Another known limitation if applicable.]
Assessment approach
We assess the accessibility of our website in the following ways:
- Self-evaluation using automated tools including [name of tool, for example axe DevTools, WAVE, or Lighthouse].
- Manual testing of keyboard navigation and screen reader usability on key flows.
- [If you engage a third-party evaluator, name them and the date of their most recent evaluation. Otherwise remove this line.]
Our most recent assessment was completed on [date].
Feedback
We welcome your feedback on the accessibility of our website. Please let us know if you encounter accessibility barriers:
- Email: [accessibility@yourbusiness.com]
- Phone: [your phone number]
- Postal address: [your mailing address]
We try to respond to accessibility feedback within [number] business days.
Enforcement procedure
If the above feedback channels do not resolve your concern, you may contact the relevant enforcement agency:
- The U.S. Department of Justice, Civil Rights Division, Disability Rights Section for complaints under Title III of the Americans with Disabilities Act.
- Your state Attorney General's office for state-level accessibility complaints.
This statement was prepared on [date] using the W3C Accessibility Statement Generator Tool as a reference.
End of template. Copy everything above this line.
Why each section is written that way
The opening paragraph. Describes intent without overclaiming. "Committed to providing" is different from "guarantees." "Actively working" is different from "compliant."
Conformance status. The critical phrase is "partially conformant." This is an honest state for almost every website. The W3C provides this exact language in its template. Claiming full conformance is both unusual and risky.
Browsers and assistive technology. Tells users what you have tested. If you have not tested with assistive technology, omit the section. Do not list technologies you have not actually used.
Known limitations. Honest acknowledgment of problems that exist. A user who encounters a listed limitation will not be surprised. A user who encounters an unlisted one can report it, which is the point of the feedback channel.
Assessment approach. Tells readers what methodology you use. Shows the statement is backed by actual work.
Feedback. The most important section for a plaintiff defense. A responsive feedback channel is evidence of ongoing engagement. The channel must actually be staffed. An unused email address is worse than no email address.
Enforcement procedure. Required by W3C guidance. Shows you are not trying to trap users in a private complaint process.
What not to publish
Claims of full WCAG 2.1 AA conformance unless it is true across the entire site. Overclaims become evidence if a demand letter arrives.
Features that do not exist. A statement listing keyboard navigation, screen reader support, and high-contrast mode will be tested against the actual site. If any claim is false, the statement becomes evidence of misrepresentation.
Vague language. "We strive to make our website accessible" is marketing copy, not a statement. It does not help a user. It does not help you in court.
A statement without a feedback channel. Interpreted as a statement that you do not want feedback. Worse than no statement at all.
Where to put the statement
- Link from the footer of every page of your site. "Accessibility" is the standard link text.
- Stable URL like
/accessibility. Do not move or rename it. - Some sites link from the header as well. Optional, but improves discoverability.
Update cadence
- Quarterly update to reflect remediation progress.
- Update after any major site change.
- Update if feedback channel or contact information changes.
Do not update just the date without updating the content. It weakens the statement's credibility.
If your site is worse than the statement
Do not publish a statement that overstates your compliance.
The better path: publish a statement that is honest about partial conformance, lists the major known limitations, and commits to continued remediation. Over the following months, do the remediation and update the known-limitations section as items are addressed. That pattern is what courts recognize as a good-faith-effort program.
This template is general guidance, not legal advice. For a statement tied to an active claim or a specific business situation, consult a licensed attorney.
Prepared by Startvest LLC, a service-disabled veteran-owned small business based in Hampstead, NC. Updated [updatedAt]. Additional guidance at adacompliancedocs.com.
Want the full library?
Three templates in total. Demand letter response, documentation checklist, accessibility statement. Browse the others or read the articles that go with them.