An accessibility statement is a public page where you explain your commitment to accessibility, the standard you’re working toward (usually WCAG 2.1 AA), and how people can report problems. It’s a recognized good-faith signal under ADA Title III — but only when your site is genuinely being remediated. Below is a free, copy-paste template.
Why an accessibility statement matters
Thousands of ADA website lawsuits are filed in the US each year, and most target small businesses with inaccessible sites. An accessibility statement won’t make you immune, but it does three useful things:
- Signals good faith. It shows you take accessibility seriously, which courts and the DOJ view favorably when a business is actively fixing barriers.
- Gives users a path to report problems. A real contact channel often resolves a complaint before it becomes a demand letter or lawsuit.
- Documents your standard. It states the conformance level (A, AA, or AAA) you’re targeting, which makes your effort measurable.
There’s a critical catch: a statement is a promise. If you claim conformance your site doesn’t have, a serial plaintiff can quote your own words back to you. The statement has to be honest and backed by actual work. That’s why we treat it as the last step after manual remediation, not a substitute for it.
What to put in an accessibility statement
A credible statement covers six things. The table below maps each part to what it accomplishes.
| Section | What it says | Why it matters |
|---|---|---|
| Commitment | You’re committed to accessibility for people with disabilities | Sets intent and good faith |
| Standard | You’re working toward WCAG 2.1 AA (and Section 508 if you sell to government) | Makes the goal measurable |
| Current status | Whether the site fully, partially, or does not yet conform | Honesty protects you legally |
| Known limitations | Specific areas still being fixed | Shows ongoing, active effort |
| Feedback channel | Email/phone to report barriers, with a response timeframe | Resolves issues before lawsuits |
| Last updated | The date you last reviewed it | Proves the effort is current |
Notice what’s not on that list: a line about an accessibility overlay or widget. Overlays don’t ensure compliance, and naming one in your statement can actively hurt you — overlay vendors are themselves named in a growing number of suits. A good statement reflects hand-coded fixes verified against assistive technology like screen readers (NVDA, JAWS, and VoiceOver) plus full keyboard navigation.
The free accessibility statement template
Copy the block below, replace every [PLACEHOLDER], and publish it at a stable URL such as /accessibility/. Edit the conformance language to match your real status — never claim “fully conforms” unless an accessibility audit confirms it.
Accessibility Statement for [BUSINESS_NAME]
Last updated: [DATE]
Our commitment
[BUSINESS_NAME] is committed to ensuring digital accessibility for
people with disabilities. We are continually improving the user
experience for everyone and applying the relevant accessibility
standards.
Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements
for designers and developers to improve accessibility for people with
disabilities. It has three levels: A, AA, and AAA. [BUSINESS_NAME] is
[partially conformant / fully conformant] with WCAG 2.1 level AA.
[Partially conformant means that some parts of the content do not yet
fully meet the standard.]
What we are doing
We are actively remediating our website. Recent and ongoing work
includes: adding alt text to images, fixing color-contrast issues,
labeling forms, ensuring full keyboard operability, and testing with
screen readers (NVDA, JAWS, and VoiceOver).
Known limitations
Despite our efforts, some content may not yet be fully accessible.
Known issues we are working to fix:
- [LIST_KNOWN_ISSUE_1]
- [LIST_KNOWN_ISSUE_2]
Feedback
We welcome your feedback on the accessibility of [BUSINESS_NAME].
If you encounter a barrier, please contact us:
- Email: [ACCESSIBILITY_EMAIL]
- Phone: [PHONE_NUMBER]
We aim to respond within [NUMBER] business days.
Assessment and standards
This statement was prepared based on a review of our website against
WCAG 2.1 level AA. [Optionally: An independent audit was conducted by
[AGENCY_NAME] on [AUDIT_DATE].]
Date
This statement was created on [DATE] and last reviewed on [DATE].If you sell to government agencies or enterprise buyers, they’ll often ask for a VPAT (Voluntary Product Accessibility Template) in addition to this statement — a formal document mapping your product against Section 508 and WCAG criteria. The public statement is for everyone; the VPAT is for procurement.
A shorter version for small sites
Not every brochure site needs the full version. A tight statement still works:
Accessibility at [BUSINESS_NAME]
We want everyone to be able to use our website. We aim to meet
WCAG 2.1 AA and are actively fixing issues as we find them. If you
have trouble using any part of this site, please email
[ACCESSIBILITY_EMAIL] or call [PHONE_NUMBER] and we'll help and fix
the problem. Last updated: [DATE].Should you use an accessibility statement generator?
A generator is a fine starting point — it saves typing. The risk is the same with every generator: it spits out generic conformance language that may not match your site. The two failure modes are:
- Over-claiming. A generator that asserts “this site fully conforms to WCAG 2.1 AA” is a liability if it isn’t true.
- The overlay trap. Many “free statement” tools are marketing funnels for overlay widgets. The statement they generate quietly endorses a product that doesn’t fix the underlying barriers — overlays and manual remediation are not the same thing.
Use the template above instead, then edit it to your real situation. The honest version protects you; the inflated version is a trap.
How to make your statement true
A statement is only as strong as the site behind it. Here’s the order that actually works:
- Audit first. Find what’s broken with a combination of automated and manual testing against the POUR principles — Perceivable, Operable, Understandable, Robust.
- Remediate by hand. Fix the code: alt text, ARIA where appropriate, color contrast, labels, focus order. Real fixes, not a script.
- Verify with assistive technology. Test with screen readers and keyboard-only navigation to confirm the fixes hold.
- Then publish the statement — dated, honest, and matching the site’s real status.
For authoritative guidance while you draft, the W3C/WAI publishes an accessibility statement generator and the canonical WCAG specs, ADA.gov covers your legal obligations, WebAIM offers practical testing resources, and Section508.gov is the reference for federal requirements.
This page is informational and not legal advice — for how a statement fits your specific risk, talk to an attorney who handles ADA web claims.
Make the promise real
Publishing a statement on an inaccessible site is worse than publishing nothing. If you want the words to be true, Curbcut does the hand-work: a full WCAG 2.1 AA audit and remediation, verified with real assistive technology — never an overlay. Start by running a free accessibility scan to see exactly where you stand before you publish.