Does Your Website Need an Accessibility Statement? (Yes — Here's Exactly What It Must Include)

An accessibility statement is not a privacy policy. It's not a generic legal disclaimer. It's a public, specific document that tells users what your accessibility commitments are, where your site currently falls short, and how they can report barriers. Done right, it's also meaningful protection in litigation.

With April 24, 2026 — the first hard federal Title II deadline — less than two months away, now is the right time to understand what accessibility statements require, who needs one, and how to get yours in shape.

What an Accessibility Statement Actually Is

Think of it as a status report on your site's accessibility, published where users can find it.

It documents:

The standard you're targeting (WCAG 2.1 Level AA, in most cases)
What you've done to test and remediate
What known issues still exist and why
How users can report problems they encounter
What they can do if their report goes unanswered

It is not a promise that your site is perfect. It's a documented, honest account of where you are and what you're doing about it. That distinction matters legally — courts look at whether an organization knew about barriers and had a process for addressing them.

Who's Legally Required to Have One

Government entities (U.S.): Under the DOJ's Title II rule, state and local government entities serving populations over 50,000 must comply with WCAG 2.1 Level AA by April 24, 2026. Publishing an accessibility statement is a core component of that compliance. Miss the deadline and you're in violation.

Public sector (EU): The EU Web Accessibility Directive has required accessibility statements for public sector bodies since 2020. The statement must follow a specific template, be published in the site's primary language, and be updated at least annually. The European Accessibility Act (EAA), which extends requirements to private businesses, takes effect June 28, 2025 for new products and 2030 for existing ones.

Private businesses (U.S.): There's no federal law that explicitly mandates an accessibility statement for private businesses — yet. But here's the practical reality: ADA Title III lawsuits against private websites surged 37% in 2025, with more than 5,000 cases filed. When your site gets a demand letter, a documented accessibility statement showing you knew about the standard, tested against it, and maintained a feedback channel is meaningful evidence of good faith. Courts and plaintiff attorneys look for this. Businesses without any documented effort are much easier targets.

If you're a private business and you're not required to have one, you still want one. It signals intent, documents effort, and reduces exposure.

What an Accessibility Statement Must Include

Vague is worse than nothing. A statement that says "we are committed to accessibility" without specifics may actually hurt you in litigation — it shows you were aware of the concept but chose to say nothing concrete.

A proper accessibility statement includes:

1. Conformance status State the standard (WCAG 2.1) and level (Level A, AA, or AAA) you're targeting or have achieved. If you're partially conformant, say so and explain what that means.

Example: "This website aims to conform to WCAG 2.1 Level AA. We are partially conformant; some content does not yet meet all criteria."

2. Known limitations List specific accessibility barriers you're aware of but haven't yet resolved. Include what the issue is, which WCAG criterion it affects, and your planned timeline for fixing it.

This is the part most organizations skip — and it's the part that matters most. Hiding known issues is a liability. Disclosing them with a remediation plan is documentation of good faith.

3. Testing methodology Automated tools miss 60–70% of real accessibility issues. Your statement needs to say what testing you actually did: automated scanning (and which tools), manual keyboard testing, screen reader testing (which reader, which browser combination), and whether users with disabilities were involved.

A statement that claims conformance without disclosing testing method is not credible — and a plaintiff's attorney will notice.

4. Date last tested and scope When was your last audit? Which pages or sections were covered? An annual review is the minimum; quarterly is better for active sites.

5. Feedback and contact mechanism Users who encounter a barrier need a clear way to report it. Include a dedicated email address or form — not a generic contact page. Response time commitment is a plus (e.g., "we aim to respond within 2 business days").

6. Escalation path If a user reports a problem and doesn't get a resolution, where can they go? In the EU, this is a legal requirement (you must name an enforcement body). In the U.S., it's best practice — and mentioning the DOJ complaint process signals that you take reports seriously.

What Bad Looks Like vs. Good

Bad:

"We are committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone."

This is boilerplate. It's everywhere. It says nothing about what standard you follow, whether you've tested anything, what issues exist, or what users should do. It proves awareness without demonstrating action — which in litigation can work against you.

Good:

"This website conforms to WCAG 2.1 Level AA with the following known exceptions: [list]. We last conducted a full audit in February 2026 using automated scanning (AccessiGuard) and manual keyboard and NVDA/Chrome testing. If you encounter a barrier, email accessibility@example.com. We aim to respond within 2 business days. If your issue is not resolved, you may file a complaint with [relevant body]."

Specific. Honest. Actionable. Regularly updated.

The difference isn't just polish — it's legal exposure. The second version documents a process. The first documents that you knew about accessibility and didn't engage with it seriously.

How to Create One

Start with your audit data. Before you can write a statement, you need to know where you actually stand. If you don't have recent audit results, start with a free accessibility audit to identify current WCAG failures and generate the data your statement needs.

Write to the required components. Use the six elements above as a checklist. If you can't fill in the testing methodology section, that's a signal you need to do the testing first.

Use a template if you need a starting point. The structure is standardized enough that starting from scratch wastes time. The ADA Compliance Kit includes a ready-made accessibility statement template covering U.S. requirements — you fill in your specifics and you're done.

Publish it correctly. The standard location is a footer link labeled "Accessibility" or "Accessibility Statement." Not buried in your legal docs. Not hidden in a sitemap. Footer link, visible on every page.

Review it regularly. Set a calendar reminder for at minimum annual review. When you do an audit and fix issues, update the statement. If your known limitations change, update it. An outdated statement that claims issues are "in progress" from two years ago is another red flag.

The Bottom Line

If you're a covered government entity, an accessibility statement is now legally required with a hard deadline of April 24, 2026. If you're a private business, it's not legally mandated — but in an environment with 5,000+ ADA lawsuits filed per year, documented good-faith effort is a meaningful defense. The cost of writing a proper statement is an hour of your time. The cost of not having one when a demand letter arrives is significantly higher.

Start with knowing where you stand. Use the AccessiGuard free ADA checklist to audit your site against WCAG 2.1 Level AA. Then write the statement using what you find — or grab the $15 full report if you want a complete, page-by-page WCAG violation list to build your statement from.

The statement is not the hardest part of accessibility. But it is the part that's public, searchable, and referenced in litigation. Make it count.