How to Write an Accessibility Statement: Template, Examples & Best Practices (2026)

What Is an Accessibility Statement?

An accessibility statement is a public document on your website that communicates your organization's commitment to digital accessibility, describes the current conformance status of your site, identifies known limitations, and provides a way for users to report problems or request assistance.

Think of it as the digital equivalent of the accessibility signage you see in physical buildings — it tells visitors with disabilities what they can expect, how to get help, and what you're doing to improve.

✅ What an Accessibility Statement Is:

A publicly available document on your website (usually linked in the footer)
A declaration of which accessibility standard you target (e.g., WCAG 2.1 Level AA)
An honest assessment of your current conformance status
A feedback channel for users to report accessibility barriers
A living document updated as your site evolves

❌ What It Is NOT:

A substitute for actual accessibility work (a statement without action is worse than no statement)
A one-time document you publish and forget
A VPAT / Accessibility Conformance Report (that's a separate, more detailed technical document)
A legal shield by itself — it must be backed by genuine effort

An accessibility statement sits at the intersection of legal compliance, user experience, and corporate responsibility. When done right, it builds trust with users, demonstrates good faith to regulators and courts, and provides a structured framework for your ongoing accessibility efforts.

Why Every Website Needs an Accessibility Statement in 2026

As of 2026, the case for publishing an accessibility statement has never been stronger. Three converging forces make it essential:

1. The Litigation Explosion

ADA website lawsuits continue to accelerate. Seyfarth Shaw's annual report documented 8,667 federal ADA website lawsuits in 2025 — and a Cox Media Group investigation found over 15,000 cases when including all federal filings from 2022 to 2025, with 90% filed by just 16 law firms. Businesses from Cowford Chophouse in Jacksonville ($20,000 settlement) to a small bakery in Gainesville ($6,500 settlement) have been hit.

An accessibility statement with a feedback mechanism gives potential plaintiffs an alternative to litigation. In several court rulings, judges have considered whether the defendant provided a way for users to report issues before jumping to a lawsuit.

2. New Legal Mandates

The European Accessibility Act (EAA), enforceable since June 28, 2025, requires an accessibility statement for all products and services covered by the directive — including e-commerce websites, banking services, and digital content sold to EU consumers. This applies to US companies serving EU markets.

In the US, the DOJ's 2024 Title II final rule requires state and local governments to make their web content conform to WCAG 2.1 Level AA by April 2026 (larger entities) or April 2027 (smaller entities), and to communicate their accessibility status. While the rule doesn't explicitly mandate a standalone "accessibility statement," it requires entities to provide accessible alternatives and information about their conformance — functions an accessibility statement serves.

3. User Expectations and Trust

Accessibility statements have become as expected as privacy policies. The WebAIM Million annual analysis consistently shows that users with disabilities check for accessibility information before engaging with a site. An absent statement signals that accessibility isn't a priority — and increasingly, that a business may not be safe to do business with.

For B2B companies, many enterprise procurement processes now require evidence of accessibility commitment. An accessibility statement, paired with a VPAT/ACR, can be the difference between winning and losing a contract.

Legal Requirements by Jurisdiction

The legal landscape varies significantly by jurisdiction. Here's what's required — and what's strongly recommended — in each major regulatory framework:

🇪🇺 European Union — MANDATORY

EU Web Accessibility Directive (2016/2102): Public sector websites and mobile apps must publish a detailed accessibility statement in a standardized format, including conformance status, non-accessible content, feedback mechanism, and enforcement body contact information. Annual review required.

European Accessibility Act (EAA) — EN 301 549: Since June 28, 2025, private sector organizations providing covered products and services must document accessibility conformance. While the EAA doesn't prescribe a specific "accessibility statement" format for private sector, manufacturers and service providers must provide information about the accessibility of their products — which an accessibility statement satisfies. Member states may impose additional requirements through national transposition laws.

🇺🇸 United States — STRONGLY RECOMMENDED

ADA Title III (Private Businesses): No explicit requirement for an accessibility statement, but courts and the DOJ consistently look for evidence of good faith effort. Multiple DOJ settlement agreements have required organizations to publish and maintain accessibility statements as a condition of resolution.

ADA Title II (Government Entities): The 2024 final rule requires state and local governments to provide accessible alternatives and communicate how to request them. An accessibility statement is the standard way to fulfill this requirement.

Section 508 (Federal Government): Federal agencies are required to document the accessibility of their ICT and provide information about accommodations. The FY2024 Section 508 Assessment found that agencies scoring higher on "public accessibility information" criteria correlated strongly with better overall conformance.

State Laws: California SB 84, if enacted, would give businesses 120 days to cure violations before a lawsuit proceeds — but only if they can demonstrate good faith effort, which an accessibility statement helps establish. Similar bills are active in Missouri and Utah.

🇨🇦 Canada — MANDATORY (Federal)

The Accessible Canada Act requires federally regulated entities to publish accessibility plans and progress reports, which include descriptions of policies, feedback processes, and conformance information. CAN/ASC-EN 301 549 (the Canadian adoption of the European standard) sets the technical baseline, with full digital compliance deadlines in 2027-2028.

🌏 Other Jurisdictions

United Kingdom: The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 requires public sector organizations to publish an accessibility statement using a prescribed format. Private sector coverage under the Equality Act 2010 is expanding.

Australia: The Disability Discrimination Act 1992 covers websites, and AS EN 301 549 provides the technical standard. While accessibility statements aren't explicitly mandated, they're considered best practice and are common among government agencies.

⚠️ The Bottom Line

Even in jurisdictions where accessibility statements aren't explicitly required by law, they're effectively becoming mandatory through court expectations, settlement requirements, procurement demands, and industry standards. Publishing one is far less expensive than defending its absence.

The 10 Essential Components of an Effective Accessibility Statement

Based on W3C WAI guidance, EU directive requirements, and analysis of DOJ settlement agreements, an effective accessibility statement should include these components:

1. Commitment Statement

Open with a clear declaration of your organization's commitment to accessibility. This should be genuine and specific — not generic boilerplate. Reference the standard you're targeting and why accessibility matters to your organization.

✅ Good:

"[Company] is committed to ensuring our website is accessible to people with disabilities. We target WCAG 2.1 Level AA conformance and continuously work to improve the user experience for everyone."

❌ Bad:

"We believe in accessibility for all."

(Too vague — no standard referenced, no specifics)

2. Standard Referenced

Identify which accessibility standard(s) you're targeting. For most organizations in 2026, this means WCAG 2.1 Level AA (the DOJ's Title II requirement) or WCAG 2.2 Level AA (the current version with additional criteria for mobile and cognitive accessibility). If you serve EU markets, reference EN 301 549.

3. Conformance Status

Use the W3C's recommended conformance terminology:

Fully conformant: The content fully conforms to the standard with no exceptions
Partially conformant: Some parts of the content do not fully conform (this is the most honest option for most websites)
Non-conformant: The content does not conform to the standard
Not assessed: The content has not been evaluated against the standard

Most organizations should say "partially conformant" — it's honest, and honesty is your strongest asset in both legal defense and user trust.

4. Known Limitations

Document specific areas where your website doesn't fully meet the standard. Be specific — "some images may lack alternative text" is better than nothing but "user-generated content in our community forum (Section 1.1.1 Non-text Content) may lack alternative text descriptions; we are adding automated alt-text prompts in Q2 2026" is significantly more credible. Include workarounds where available.

5. Feedback Mechanism

This is arguably the most important component. Provide at least two ways for users to report accessibility barriers or request assistance:

A dedicated email address (e.g., accessibility@company.com)
A phone number
An accessible web form
A physical mailing address

Specify your expected response time (e.g., "We aim to respond within 2 business days"). This feedback channel serves double duty: it helps users get the assistance they need AND provides an alternative to filing a lawsuit. Several courts have noted whether a feedback mechanism existed when evaluating ADA claims.

6. Date of Last Update

Always include when the statement was last reviewed and updated. A statement dated within the last 3-6 months signals active maintenance. A statement dated 2023 — or worse, one with no date — signals abandonment and can actually hurt your legal position.

7. Assessment Methods

Describe how you evaluated your website's accessibility. Did you use automated scanning tools? Manual expert testing? Assistive technology testing? User testing with people with disabilities? Listing specific tools (e.g., "automated scanning with axe-core and RatedWithAI, supplemented by manual NVDA screen reader testing") adds significant credibility.

8. Remediation Plan and Timeline

If your site isn't fully conformant (and almost no site is), describe what you're doing to improve. Include specific timelines when possible: "We are addressing color contrast issues identified in our February 2026 audit and expect to resolve them by April 2026." This demonstrates active, ongoing commitment — exactly what courts and regulators want to see.

9. Scope

Clearly define what the statement covers. Does it apply to your main website only? Mobile apps? Web applications? Third-party content? PDF documents? Being specific about scope prevents misunderstandings and protects you from claims about properties not covered by your statement.

10. Enforcement and Escalation (EU/UK)

If you're subject to EU or UK regulations, include contact information for the relevant enforcement body. In the EU, this is the designated national enforcement body in each member state. In the UK, it's the Equality and Human Rights Commission (EHRC) for England, Scotland, and Wales, or the Equality Commission for Northern Ireland.

Free Accessibility Statement Template (Copy & Paste)

Use this template as a starting point. Replace all bracketed items with your specific information. Don't just copy it verbatim — customize it to accurately reflect your organization's accessibility journey.

# Accessibility Statement for [Organization Name]

**Last updated:** [Date]

## Our Commitment

[Organization 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.

## Standards

This website aims to conform to **WCAG 2.1 Level AA** (Web Content 
Accessibility Guidelines). These guidelines define how to make web 
content more accessible to people with disabilities, including those 
with visual, auditory, physical, speech, cognitive, language, learning, 
and neurological disabilities.

## Conformance Status

This 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.

## Known Limitations

Despite our best efforts, some content on this website may not yet 
be fully accessible. The following is a description of known 
limitations and potential workarounds:

1. **[Area/Feature]:** [Description of limitation]. We plan to 
   [remediation action] by [date]. In the meantime, [workaround].

2. **[Area/Feature]:** [Description of limitation]. We plan to 
   [remediation action] by [date]. In the meantime, [workaround].

3. **Third-party content:** Some content provided by third-party 
   services (such as [examples]) may not be fully accessible. We 
   are working with these providers to improve accessibility.

## Assessment Methods

We assessed the accessibility of this website through:

- **Automated testing** using [tools, e.g., axe-core, RatedWithAI]
- **Manual testing** using [assistive technologies, e.g., NVDA, 
  VoiceOver]
- **Expert review** by [internal team / external consultant]
- Last audit completed: [Date]

## Feedback

We welcome your feedback on the accessibility of [Organization Name]'s 
website. If you encounter accessibility barriers or need assistance, 
please contact us:

- **Email:** accessibility@[company].com
- **Phone:** [phone number]
- **Mailing address:** [address]

We aim to respond to feedback within **[X] business days**.

## Scope

This statement applies to:
- [Website URL]
- [Additional properties if applicable]

It does not cover:
- [Third-party services, if any]
- [Legacy content, if applicable]

## Remediation Timeline

We are actively working to improve accessibility:

- **[Q1 2026]:** [Specific remediation milestone]
- **[Q2 2026]:** [Specific remediation milestone]
- **Ongoing:** Regular automated and manual accessibility testing

## Technical Specifications

This website relies on the following technologies for conformance:
- HTML
- CSS
- JavaScript
- WAI-ARIA

These technologies are relied upon for conformance with WCAG 2.1 
Level AA.

## Compatible Browsers and Assistive Technologies

This website is designed to be compatible with:
- Recent versions of major browsers (Chrome, Firefox, Safari, Edge)
- Screen readers (NVDA, JAWS, VoiceOver, TalkBack)
- Screen magnification software
- Speech recognition software

---

This statement was prepared on [date] and last reviewed on [date].

💡 Pro Tip: Audit Before You Write

Before filling out this template, run a free accessibility scan of your website to identify your actual conformance level and specific issues. Try RatedWithAI's free scanner — it tests against WCAG 2.1 AA and gives you a letter grade (A through F) with specific issue details you can reference in your known limitations section.

Real-World Examples from Major Organizations

The best way to learn is by studying what's working. Here's how leading organizations handle their accessibility statements, along with what makes each effective:

🏛️ GOV.UK (UK Government)

Why it works: GOV.UK sets the gold standard for accessibility statements. Each government service has its own statement that follows a standardized template with specific WCAG criteria references, plain language descriptions of issues, and concrete timelines for fixes. They explicitly list which WCAG success criteria are not met, provide workarounds, and link to the enforcement body.

Key takeaway: Specificity builds credibility. GOV.UK doesn't say "some images lack alt text" — they say exactly which pages, which criteria (1.1.1), and when they'll fix it.

🏢 Microsoft

Why it works: Microsoft's accessibility statement goes beyond the standard template by including a comprehensive description of built-in accessibility features, keyboard shortcuts, and assistive technology compatibility for each product. They provide conformance documentation per product (VPATs/ACRs) and link to their centralized accessibility support team.

Key takeaway: If you have multiple products, provide product-specific accessibility information rather than one generic statement.

🎓 Harvard University

Why it works: Harvard's Digital Accessibility Policy addresses the complexity of a large organization with thousands of web properties. They define clear roles and responsibilities, link to training resources for content creators, and provide a formal complaints process with escalation paths. Their statement acknowledges that decentralized content creation presents ongoing challenges.

Key takeaway: For organizations with many content creators, address how you handle decentralized content — it's more honest than pretending full control.

🛒 Target (DOJ Settlement Example)

Why it matters: Target's accessibility statement was created as part of a landmark 2008 DOJ settlement ($6 million) and set the template for post-lawsuit accessibility commitments. It required ongoing accessibility auditing, a dedicated accessibility team, annual testing with assistive technologies, and a published commitment with regular updates.

Key takeaway: It's far cheaper to publish a good accessibility statement proactively than to be forced to create one as part of a multimillion-dollar settlement.

7 Common Mistakes That Undermine Your Accessibility Statement

1️⃣

Claiming Full Compliance When You're Not

The most dangerous mistake. If you claim "our website is fully WCAG 2.1 AA compliant" and a plaintiff finds a single missing alt text attribute, your statement becomes evidence of either deception or negligence. The FTC's $1 million fine against accessiBe was partly about deceptive compliance claims. Use "partially conformant" and be specific about what works and what doesn't.

2️⃣

Using Generic Boilerplate Without Customization

A statement that says "We are committed to accessibility" without any specifics about your actual website is meaningless. Courts and users can tell the difference between genuine effort and copy-paste compliance theater. Reference your specific site, your specific issues, and your specific remediation work.

3️⃣

Publishing It and Never Updating It

A stale accessibility statement with a date from two years ago is arguably worse than no statement at all. It suggests you wrote it once to check a box and never followed through. Set a calendar reminder to review and update at least quarterly.

4️⃣

No Feedback Mechanism (or a Broken One)

If your statement doesn't include a way for users to report problems, you've missed the most important component. Worse: if you list an email address that bounces or a phone number that nobody answers, you've created evidence of negligence. Test your feedback channels regularly.

5️⃣

Making the Statement Page Itself Inaccessible

The irony is painfully common: accessibility statements published as images, embedded in inaccessible PDFs, or placed on pages that fail basic WCAG criteria. Your accessibility statement page should be one of the most accessible pages on your entire site. Use clean HTML, proper headings, adequate contrast, and test it with a screen reader.

6️⃣

Hiding It Where Nobody Can Find It

An accessibility statement buried three clicks deep in your sitemap doesn't serve users who need it. Link it from the footer of every page, next to your privacy policy and terms of service. Use a predictable URL like /accessibility or /accessibility-statement.

7️⃣

Substituting an Overlay Widget for a Real Statement

Accessibility overlay widgets like accessiBe and UserWay often auto-generate a "compliance" statement that claims WCAG conformance. These auto-generated claims are not a substitute for a genuine accessibility statement and can expose you to additional liability — especially after the FTC's enforcement action. Write your own statement based on your actual accessibility audit results.

Conformance Language: What to Say (and What NOT to Say)

The language you use in your accessibility statement carries legal weight. Here's guidance on getting it right:

✅ Say This:

"This website is partially conformant with WCAG 2.1 Level AA."
"We aim to conform to WCAG 2.1 Level AA and are actively working toward that goal."
"Our most recent audit identified [X] issues, of which we have resolved [Y] and are addressing the remaining [Z]."
"We test with NVDA, VoiceOver, and axe-core automated scanning tools."
"We know that [specific feature] has limitations for keyboard-only users and plan to remediate by [date]."

❌ Don't Say This:

"Our website is ADA compliant." (ADA doesn't define specific web standards)
"We use an accessibility widget to ensure full compliance." (Widgets don't ensure compliance; FTC fined accessiBe $1M for similar claims)
"Our website is 100% accessible." (No website is 100% accessible to all users in all situations)
"We comply with Section 508." (Unless you're a federal agency; Section 508 applies to federal ICT)
"This website is WCAG 2.1 AAA compliant." (Level AAA full conformance is intentionally aspirational, not a practical target)

⚖️ Legal Language Tip

The DOJ has stated that WCAG is not the ADA standard — it doesn't endorse WCAG as the sole measure of ADA compliance for Title III entities. However, WCAG remains the most widely recognized benchmark. Frame your statement around WCAG conformance as a technical standard you target, rather than claiming it equals ADA compliance. Say "We target WCAG 2.1 Level AA as our technical benchmark for accessibility" rather than "We are ADA compliant because we follow WCAG."

How to Keep Your Accessibility Statement Current

An accessibility statement is a living document. Here's a practical maintenance schedule:

📅 Monthly (Lightweight)

Run an automated accessibility scan of your website
Review any feedback received through your accessibility channel
Update the "last reviewed" date even if no changes are needed
Check that your feedback email and phone still work

📋 Quarterly (Thorough)

Review and update conformance status based on recent changes
Update known limitations section — remove resolved items, add newly discovered ones
Update remediation timeline
Review third-party content and services for accessibility changes
Conduct at least basic manual testing (keyboard navigation, screen reader spot-check)

🔄 After Major Changes (Immediate)

Website redesign or migration — full accessibility audit + statement rewrite
New features or sections — test for accessibility, update scope and limitations
New third-party integrations — assess vendor accessibility and note any limitations
After receiving an ADA demand letter — immediately update to reflect remediation efforts

📊 Annually (Comprehensive)

Commission a professional accessibility audit
Review against current standards (WCAG may have updated criteria)
Review legal landscape for new requirements (EAA enforcement, state laws)
Update VPAT/ACR if you maintain one
Review training needs for content creators and developers

Free Generators, Tools & Resources

These tools can help you create, validate, and maintain your accessibility statement:

W3C WAI Accessibility Statement Generator

Best for: Everyone — this is the gold standard. The W3C WAI's free tool walks you through creating a comprehensive statement following international best practices. It produces clean, structured output that follows the format expected by EU regulations and global accessibility standards.

🔗 w3.org/WAI/planning/statements/generator

Accessible Web Statement Generator

Best for: Quick generation with a clean interface. Fill out basic information about your organization and accessibility efforts, and it generates a customizable statement you can paste into your site.

🔗 accessibleweb.com/accessibility-statement-generator

RatedWithAI Free Scanner

Best for: Identifying your actual conformance level before writing your statement. Scan your website against WCAG 2.1 AA, get a letter grade (A through F), and identify specific issues to document in your known limitations section. The scan results give you concrete data to reference rather than guessing at your conformance status.

🔗 ratedwithai.com

Termly Accessibility Statement Template

Best for: Organizations that want a template alongside their privacy policy and terms of service. Termly offers a downloadable template in their legal document suite.

🔗 termly.io/resources/templates/accessibility-statement-template

⚠️ Important: Generators Are a Starting Point

No generator can create a fully customized, legally defensible accessibility statement automatically. Use them to get the structure right, then tailor every section to accurately reflect your specific website, your actual audit results, and your real remediation plans. A generated statement that doesn't match reality is worse than a custom statement with honest limitations.

How Your Accessibility Statement Protects You in Litigation

With ADA lawsuits accelerating to nearly 8,700 per year, and repeat lawsuits targeting the same businesses, understanding how your accessibility statement functions in litigation is critical:

Evidence of Good Faith

Courts evaluating ADA claims consistently consider whether a defendant demonstrated "good faith" in addressing accessibility. A well-maintained accessibility statement — especially one that predates the lawsuit — is powerful evidence. In the DOJ's settlement with Rite Aid (2024), the agreement specifically required publishing and maintaining an accessibility statement. The fact that a settlement requires one tells you how courts value them.

Documented Remediation Efforts

When your statement includes a remediation timeline and specific milestones, it creates a documented record of improvement that courts consider favorably. If you can show "We identified 47 accessibility issues in January, resolved 35 by March, and have a plan for the remaining 12 by June," that's significantly more defensible than "We just found out our website had problems."

The Feedback Mechanism as Alternative to Litigation

This is where your feedback channel pays for itself. If a user encounters a barrier, contacts you through your published feedback mechanism, and you respond promptly with a fix or workaround, that interaction undermines any subsequent lawsuit claim. It shows: (1) you had a mechanism in place, (2) you responded, and (3) the issue could have been resolved without litigation.

Several courts scrutinizing serial plaintiffs have questioned whether plaintiffs actually attempted to use feedback mechanisms before filing suit. The Satchel's Pizza case in Gainesville argued in its motion to dismiss that Evans (who filed 49 lawsuits) sued without first contacting the business through available channels.

State Right-to-Cure Laws

Multiple states are actively pursuing legislation that would require notice and opportunity to cure before an ADA lawsuit can proceed. California's SB 84 would provide a 120-day cure period, and Missouri and Utah have similar bills. An accessibility statement with a feedback mechanism positions you to take advantage of these protections: you already have a channel for receiving and responding to complaints.

⚠️ Warning: A Statement Without Action Backfires

A plaintiff's attorney can use your own accessibility statement against you. If your statement claims "partially conformant" but your site is riddled with basic violations, the gap between claim and reality becomes evidence of negligence. If you list a feedback email that nobody monitors, that's evidence of bad faith. Your statement must be backed by genuine, documented effort. That's why we recommend conducting a thorough audit before publishing your statement.

Accessibility Statement vs. VPAT: When You Need Each

Organizations often confuse accessibility statements with VPATs (Voluntary Product Accessibility Templates). They serve different purposes:

📄 Accessibility Statement

Audience: General public, all website visitors
Purpose: Communicate commitment, conformance status, and feedback channel
Detail level: Summary — plain language, no technical jargon
Location: Published on your website (footer link)
When needed: Always — every website should have one
Update frequency: At least quarterly
Required by: EU Web Accessibility Directive, EAA, DOJ settlements

📊 VPAT / ACR

Audience: Procurement teams, government buyers, enterprise customers
Purpose: Document detailed, criterion-by-criterion conformance
Detail level: Comprehensive — maps every WCAG/508 criterion
Location: Shared on request or published in documentation
When needed: When selling to government or enterprise
Update frequency: After major releases or annually
Required by: Section 508 (federal procurement), many state/local procurement policies

Most organizations need an accessibility statement. If you sell software or digital services to government or enterprise clients, you also need a VPAT/ACR. The accessibility statement often references the VPAT: "For detailed conformance information, see our Accessibility Conformance Report (ACR)."

Frequently Asked Questions

Is an accessibility statement legally required?

It depends on your jurisdiction. Under the European Accessibility Act (EAA), accessibility statements are mandatory for products and services sold in the EU as of June 2025. The EU Web Accessibility Directive requires them for all public sector websites. In the US, the ADA does not explicitly require an accessibility statement, but the DOJ's 2024 Title II final rule requires state and local governments to publish information about their accessibility efforts. Section 508 requires federal agencies to document conformance. Even where not legally mandated, an accessibility statement demonstrates good faith effort that can significantly help in litigation defense.

What should an accessibility statement include?

An effective accessibility statement should include: (1) a commitment to accessibility, (2) the standard you're targeting (e.g., WCAG 2.1 Level AA), (3) your current conformance status, (4) known limitations with workarounds, (5) a feedback mechanism with contact information, (6) the date the statement was last updated, (7) links to any audit reports or conformance documentation, and (8) information about your remediation timeline for known issues.

Where should I put my accessibility statement on my website?

Your accessibility statement should be linked from the footer of every page on your website, similar to your privacy policy or terms of service. The URL should be intuitive — typically /accessibility or /accessibility-statement. It should also be reachable from your sitemap. The W3C WAI recommends placing it in a consistent, predictable location that users can easily find regardless of which page they land on.

How often should I update my accessibility statement?

You should update your accessibility statement at least quarterly, and immediately after any major website redesign, accessibility audit, or remediation milestone. The EU Web Accessibility Directive requires annual reviews for public sector organizations. Stale statements — especially those claiming full WCAG compliance with a date from two years ago — can actually hurt your credibility and legal position more than having no statement at all.

Can an accessibility statement protect my business from ADA lawsuits?

An accessibility statement alone cannot prevent a lawsuit, but it can significantly strengthen your legal defense. Courts and the DOJ look favorably on organizations that demonstrate good faith effort toward accessibility. A well-maintained statement that includes a feedback mechanism, documented remediation efforts, and specific conformance information shows proactive commitment. In several ADA settlement agreements, the DOJ has specifically required companies to publish and maintain accessibility statements as part of the resolution.

What's the difference between an accessibility statement and a VPAT?

An accessibility statement is a public-facing document on your website that communicates your accessibility commitment, conformance status, and contact information to all users. A VPAT (Voluntary Product Accessibility Template) / ACR (Accessibility Conformance Report) is a detailed technical document that maps your product's conformance to specific standards criterion by criterion, typically used in procurement processes. Think of the accessibility statement as a summary for the general public, and the VPAT/ACR as the detailed technical audit used by IT procurement teams.

Should I claim WCAG 2.1 AA compliance in my accessibility statement?

Be extremely careful about claiming full compliance. Instead, use the W3C's recommended conformance language: "fully conformant," "partially conformant," or "non-conformant." Most websites should use "partially conformant" with specific details about known non-conformances. Claiming full compliance when your site has accessibility issues — which almost all sites do — can be seen as misleading and may actually increase legal liability. Honesty about your current state plus a clear remediation plan is far more defensible than overclaiming.

Are there free tools to help generate an accessibility statement?

Yes. The W3C WAI offers a free Accessibility Statement Generator at w3.org/WAI/planning/statements/generator that walks you through creating a comprehensive statement following international best practices. Other free options include Accessible Web's generator and various templates from accessibility consultancies. However, the best accessibility statements are customized to your specific situation rather than purely auto-generated — use generators as a starting point, then tailor the content to accurately reflect your organization's accessibility journey.

Write Your Accessibility Statement with Confidence

Before you write your statement, know where you stand. Run a free accessibility scan to identify your actual WCAG conformance level, specific issues, and areas that need remediation. Then write your statement based on real data — not guesswork.

Scan Your Website Free →Read the Full Audit Guide