An accessibility statement is the most misunderstood page on a small-business website. Some owners think it’s a magic shield against lawsuits. Others skip it entirely because “we don’t have a legal page like that.” Both are wrong. A statement won’t make you lawsuit-proof, but a genuine one — backed by genuine work — is one of the cheapest, clearest ways to show you took accessibility seriously before anyone asked.
Here’s what it actually is, what belongs in it, and why it matters when a demand letter shows up.
What an accessibility statement actually is
An accessibility statement is a public page that tells visitors three things: that you’re committed to making your site usable by people with disabilities, which standard you’re working toward, and how to reach you if something doesn’t work. The W3C Web Accessibility Initiative treats those three — a commitment, the standard applied (such as WCAG 2.1 or 2.2), and contact information — as the minimum a statement should contain.
It’s not a legal disclaimer, and it’s not marketing. At its best it’s a short, honest account of where your site stands and where it’s headed. The W3C even publishes a free statement generator you can fill in and then customize — a reasonable starting point, though the words matter less than the work behind them.
What to include (and what to leave out)
Beyond the three required pieces, the W3C recommends adding a handful of things that make a statement genuinely useful instead of boilerplate:
- Measures you’ve taken — for example, that you test with screen readers and by keyboard, not just an automated scanner.
- Known limitations, stated plainly. If a third-party booking widget isn’t fully accessible yet, say so. Honesty here manages expectations and reads as good faith, not weakness.
- Plain language, not jargon. The W3C is explicit: instead of “Success Criterion 1.2.2 was not met,” write “some videos do not yet have captions.” A statement is for users, not auditors.
- A real feedback channel — an email or contact form, ideally with a response window you can actually hit.
What to leave out is just as important. Never claim you’re “100% compliant” or “fully ADA compliant.” No honest statement promises perfection — accessibility is ongoing, and the right phrase is substantial conformance with WCAG 2.1 AA. Overstating doesn’t protect you; it hands a plaintiff a quotable gap between your promise and your code.
You can see a working example on our own accessibility statement — written to model the honest, no-overpromising tone we’re describing here.
Why a real statement helps when a lawsuit lands
Here’s the part owners care about. Digital accessibility litigation isn’t slowing down: by the end of 2025, plaintiffs had filed more than 5,000 digital accessibility lawsuits, with ecommerce sites making up close to 70% of targets, according to UsableNet’s tracking. A statement doesn’t make you invisible to that. So why publish one?
Because under the ADA, good-faith effort is something courts and plaintiffs actually weigh. The Department of Justice’s own web accessibility guidance doesn’t mandate a specific standard for businesses — it gives you flexibility in how you comply but is clear that you still must make what you offer online accessible. In that flexible environment, documented effort is the currency. Defense attorneys at Seyfarth’s ADA Title III blog note that businesses are in a far stronger position when they can show pre-suit accessibility work and a real remediation process, rather than a one-time scramble after the complaint. In some cases, prompt, documented remediation has even rendered a plaintiff’s claims moot.
An accessibility statement is the public-facing artifact of that effort. It’s dated, it names a standard, and it points to a feedback process — exactly the kind of paper trail that says “we were already working on this.” On its own it proves nothing. Standing on a real, remediated site, it’s evidence.
The trap: a statement your code can’t back up
The fastest way to turn a statement into a liability is to credit an accessibility overlay and call it done. UsableNet’s 2025 data shows a rising share of lawsuits that explicitly name an accessibility widget while alleging the underlying code is still broken — roughly 95 to 155 such cases a month over the year per their 2026 trends report. A statement that says “this site is accessible thanks to [widget]” while a screen reader still can’t complete checkout doesn’t read as good faith. It reads as a defendant who paid for the appearance of compliance.
This is why we draw a hard line: a statement should describe manual remediation that actually happened. Write the statement after the work, not instead of it.
How to do this in the right order
A statement is the last step, not the first. The sequence that holds up:
- Find out where you stand. A free accessibility scan or a full audit tells you what’s actually broken against WCAG 2.1 AA.
- Fix the real issues through remediation — the HTML, ARIA, contrast, and forms, by hand.
- Document and keep going. Accessibility isn’t a one-time event; ongoing monitoring is part of the good-faith story.
- Then publish the statement — honest about the standard, the testing, the known gaps, and how to report a barrier.
Do it in that order and the statement is true. Do it backwards and you’ve written a promise your site can’t keep. If you’re staring at a demand letter right now, the priority is the work, not the wording.
This article is general information, not legal advice. For your specific obligations and risk, consult a qualified attorney. [EXPERT_NAME] and the [AGENCY_NAME] team can help with the accessibility work a statement should stand on — start with a free scan.