A mid-sized retailer once published a one-paragraph accessibility statement. It said the company was "committed to accessibility for all users" and "strives to meet WCAG standards." Legal signed off. Marketing published it. Everyone felt covered.
Eighteen months later, that exact paragraph showed up as an exhibit in a demand letter. Not as proof the company cared. As proof the company knew accessibility mattered, said so publicly, and then took no specific, documented action to back it up. The statement that was supposed to be a shield became a timestamp of awareness with nothing attached to it.
That is the trap. A statement written to sound reassuring, without dates, scope, or specifics, does not read as reassuring to a court or a plaintiff's attorney. It reads as an admission with no follow-through.
The Stat: More than 1,000 businesses, over 25% of all tracked digital accessibility lawsuits in 2026, were sued despite already having an accessibility overlay or widget installed on their site. (Source: 216digital 2026 overlay risk analysis)
That statistic matters here because it tells you something uncomfortable: having "something" in place, whether that's a widget or a vague statement, is not the same as having something defensible. Plaintiffs and their counsel are not impressed by the presence of a good-faith gesture. They are looking at whether the gesture is specific enough to mean anything.
Why vague statements backfire
An accessibility statement exists to do two things: tell visitors what to expect, and tell a court or investigator what your organization actually knew and did. A vague statement fails both jobs at once.
Phrases like "we strive to be accessible to all" or "we are committed to WCAG compliance" carry no operational content. They do not say which WCAG version, which conformance level, which date, or which parts of the site are covered. When a plaintiff's attorney reads that language, they read a company that knew accessibility was a legal and usability issue, said so in writing, and then offered nothing to show what was actually done about it.
That is worse than saying nothing. Silence is neutral. A vague promise is a documented awareness with no remediation trail attached, and it can be cited as exactly that.
What makes a statement legally defensible
A defensible accessibility statement is not longer for the sake of length. It is specific in four places.
1. A stated conformance target
Name the actual standard and level you are working toward, such as WCAG 2.2 Level AA. Do not just say "accessible." A stated target gives you (and anyone reviewing your site) a fixed, testable benchmark instead of a feeling.
2. A real, current date
Include the date the statement was last reviewed or updated. An undated statement looks static and abandoned, which suggests it was published once and forgotten. A dated statement, updated on a real cadence, shows an active, ongoing process rather than a one-time PR move.
3. A named, working contact method
Give visitors an actual way to reach a person, not just a generic contact form buried three clicks away. A named email or a direct accessibility contact shows you are inviting feedback rather than hoping no one asks. It also gives you a documented record that you responded when someone did ask, which matters enormously if a dispute ever gets to a legal stage.
4. Disclosed known limitations
This is the one most companies skip, and it's the one that matters most. If you know a certain feature, page type, or third-party embed isn't fully accessible yet, say so, along with your plan or timeline to address it. Disclosing a known gap, paired with a plan, reads as an organization that understands its own site and is actively managing the issue. Hiding the gap and hoping no one notices reads as concealment the moment it's discovered, and it will be discovered.
Why "we use an overlay" is not a substitute
Some companies treat an accessibility overlay or widget as a stand-in for doing this work. It is not, and treating it that way is exactly how you end up as a data point in a statistic like the one above. An overlay might adjust contrast or font size on the fly, but it does not fix broken form labels, inaccessible custom components, or content that was never structured for a screen reader in the first place. A statement that leans on "we have an accessibility widget installed" as its main claim is functionally as vague as "we strive to be accessible," because it still says nothing about scope, testing, or known gaps. If your statement's strongest claim is the tool you installed rather than the testing you did, that is worth revisiting before anyone else reads it that way.
A simple structure that holds up
You don't need a legal team to draft something workable. A defensible statement generally follows this shape:
- A short opening stating your organization's commitment and the specific standard and level you're targeting
- The scope: which site, subdomains, or products the statement covers
- The date of the most recent review
- Known limitations and the plan to address them
- A named contact method for reporting issues, with a realistic response timeframe
This is not a legal document written to sound impressive. It's an operational document written to be checked against reality. The W3C's guidance on accessibility statements lays out this same structure in more depth, and it's worth reading directly rather than relying on secondhand summaries.
Review it on a real schedule
A statement that never changes eventually looks exactly like the vague, undated version it was meant to replace. Put a recurring review on the calendar, ideally every time the site gets a meaningful redesign or a new major feature ships, and update the review date even if nothing else changes. A statement dated eighteen months ago, sitting untouched through two site redesigns, tells the same story as no date at all: nobody has looked at this since it was written.
Keep a paper trail behind it
The statement itself is the public face, but what protects you is what sits behind it. Keep records of your testing process, the audits you've run, and how you responded to any accessibility feedback you received. If your statement says known limitations are being addressed, be able to show, internally at least, what "being addressed" actually meant on a given date. A statement backed by a real internal record is a different animal, legally, than a statement that was simply typed up and forgotten.
Statement versus VPAT: not the same job
A statement and a VPAT (Voluntary Product Accessibility Template) serve different but related purposes, and conflating them is another common mistake. The statement is your public-facing, plain-language commitment. The VPAT is the detailed, criterion-by-criterion technical conformance record, usually used in procurement and enterprise sales contexts. If you haven't yet worked through how the two fit together and what to actually publish, the deeper breakdown in Accessibility Statement and VPAT: What to Publish, and Why It Actually Matters covers that pairing in full. This piece is narrower on purpose: it's about what makes the statement itself hold up when someone tries to use it against you.
The cost of getting this wrong
None of this is theoretical risk. The financial exposure of an ADA-related website lawsuit, including settlement costs, legal fees, and remediation under a consent decree, is substantial and well documented in what an ADA website lawsuit actually costs. Reviewing that breakdown alongside the ADA.gov guidance on digital accessibility obligations gives a fuller picture of why a specific, dated statement is worth the extra hour it takes to write properly.
Write it once, get it right
Your accessibility statement is one of the cheapest pieces of legal protection your organization can produce, but only if it's written with actual specifics instead of comforting generalities. A dated, scoped statement with a named contact and honestly disclosed limitations does more to protect you than any overlay widget or one-line promise ever will.
If you're not sure where your current statement (or your current site) stands, it's worth having someone actually look at it rather than guessing. Reach out to our team at experts@wcag.world, or start with a free accessibility audit to see exactly what your statement should say and what it might currently be exposing you to.