Do I Need an Accessibility Statement? ADA Website Requirements Explained

"Do I need an accessibility statement on my website?" It's one of the most common questions organizations ask when addressing digital accessibility. The answer depends on who you are, where you operate, and what regulations apply to you—but the short version is this: even when not strictly required, an accessibility statement is almost always a good idea.

This guide clarifies when accessibility statements are legally required, when they're strongly recommended, and what purpose they serve regardless of mandate.

When Accessibility Statements Are Required

European Union (EAA and Web Accessibility Directive)

If you operate in or serve customers in the European Union, accessibility statements are explicitly required by law. The EU Web Accessibility Directive mandates accessibility statements for all public sector websites and mobile applications. The European Accessibility Act extends similar requirements to private sector businesses offering certain products and services.

These statements must follow a specific format and include particular elements: conformance status, non-accessible content with explanations, feedback mechanisms, and links to enforcement procedures. The EU provides a model accessibility statement that organizations can adapt for their own use.

Government Websites (Section 508, Global Requirements)

Federal agencies in the United States must comply with Section 508 of the Rehabilitation Act, which includes documentation requirements. While Section 508 doesn't prescribe exactly how to document accessibility, agencies are expected to provide accessibility information and maintain evidence of compliance efforts.

Many other countries have similar requirements for government websites. Canada's Standard on Web Accessibility, Australia's Digital Service Standard, and the UK's Public Sector Bodies Accessibility Regulations all include documentation components.

Organizations Receiving Government Funding

If your organization receives federal funding—grants, contracts, or financial assistance—you may be subject to Section 504 of the Rehabilitation Act or similar state requirements. These often include obligations to document accessibility practices and provide information about accommodations.

When Accessibility Statements Are Strongly Recommended

ADA-Covered Businesses

The Americans with Disabilities Act doesn't explicitly require accessibility statements, but having one demonstrates good faith effort toward compliance. If your business qualifies as a "place of public accommodation" under ADA Title III—which courts have increasingly interpreted to include websites—an accessibility statement shows you're taking accessibility seriously.

In ADA litigation, courts consider whether organizations have made good faith efforts toward accessibility. A well-maintained accessibility statement that acknowledges current status, describes ongoing efforts, and provides contact information for accommodation requests creates documentary evidence of those efforts.

E-Commerce and Online Services

Online retailers and service providers face significant accessibility lawsuit exposure. Thousands of web accessibility lawsuits are filed annually, with e-commerce sites being the most frequent targets. An accessibility statement won't prevent a lawsuit, but it demonstrates organizational commitment and provides a clear channel for users to request help before resorting to legal action.

The statement also serves practical purposes: users who encounter barriers can contact you directly, giving you the opportunity to resolve issues before they escalate.

Enterprises and B2B Companies

Large enterprises increasingly require accessibility information from vendors during procurement. Government contracts routinely request VPATs (Voluntary Product Accessibility Templates) and accessibility documentation. Educational institutions evaluating software expect accessibility statements.

Having a readily available accessibility statement streamlines sales conversations and removes friction from procurement processes. Not having one may disqualify you from consideration altogether.

What an Accessibility Statement Accomplishes

Demonstrates Commitment

An accessibility statement publicly declares that your organization cares about accessibility. This matters to users with disabilities, who often feel ignored or forgotten by businesses. It matters to advocacy organizations that track accessibility across industries. And it matters to potential partners and customers who prioritize working with socially responsible organizations.

The statement doesn't claim perfection—honest acknowledgment of ongoing work is more credible than vague claims of full compliance. Users appreciate transparency about current limitations and remediation timelines.

Provides User Information

Users with disabilities need to know several things before investing time in your website or product: What assistive technologies does it support? Are there known issues that might affect their specific needs? What accessibility features are available? Who can they contact if they encounter problems?

An accessibility statement answers these questions upfront, saving users frustration and helping them make informed decisions about whether and how to engage with your content.

Creates a Feedback Channel

Perhaps most importantly, an accessibility statement establishes a clear mechanism for reporting issues. When users encounter barriers, they need somewhere to turn. Without a designated channel, complaints may go to generic contact forms where they're deprioritized or misunderstood. Worse, users may simply leave—taking their business elsewhere without telling you why.

A dedicated accessibility contact email or feedback form ensures issues reach people equipped to address them. This benefits users who get help faster and benefits organizations that learn about problems they can fix.

Documents Compliance Efforts

In legal contexts, documentation matters. An accessibility statement creates a record of what you've done, what you know about current limitations, and what you're doing to improve. This documentation can demonstrate good faith if compliance questions arise.

Update your statement regularly—at least annually and whenever significant changes occur. Version history shows ongoing attention rather than a one-time effort.

Essential Statement Elements

While specific requirements vary by regulation, effective accessibility statements generally include these components:

Conformance Status: What standard are you measuring against (typically WCAG 2.1 or 2.2) and what level (typically AA)? Are you fully conformant, partially conformant, or non-conformant? Be honest—claiming full conformance when issues exist damages credibility.

Scope: What does the statement cover? Your entire website? Specific sections? Mobile applications? Make the boundaries clear so users know what to expect.

Known Limitations: If certain content isn't accessible, acknowledge it. Explain why (legacy systems, third-party components, remediation in progress) and describe any workarounds. Provide a timeline for fixes when possible.

Feedback Mechanism: How can users report issues or request help? Provide specific contact information—email address, phone number, physical address. Include expected response times.

Date: When was this statement created or last updated? Stale statements suggest abandoned efforts.

Enhanced Elements

Stronger statements also include:

Evaluation Methods: How did you assess accessibility? Internal testing, external audits, automated scanning, user testing? This adds credibility to your conformance claims.

Compatibility Information: What browsers and assistive technologies do you support? Users want to know if their specific setup will work.

Accessibility Features: What features have you built in? Skip links, keyboard navigation, adjustable text size, color contrast options? Help users discover what's available.

Practical Considerations

Placement

Make your accessibility statement easy to find. The most common locations include:

• Footer link (labeled "Accessibility")
• Help/Support section
• About section
• Legal/Policies area

Don't bury it deep in site hierarchy. Users who need it shouldn't have to search extensively to find it.

The Statement Itself Must Be Accessible

This sounds obvious but bears emphasizing: your accessibility statement should itself be accessible. Proper heading structure, sufficient color contrast, keyboard navigable, works with screen readers. Nothing undermines your credibility faster than an inaccessible accessibility statement.

Keep It Current

An outdated statement is worse than no statement. If your statement references "upcoming Q2 2022 improvements" and it's now 2025, users will question whether you've paid any attention to accessibility in the intervening years.

Review and update your statement:

• At least annually
• After major website redesigns
• When accessibility audits complete
• When significant remediation milestones are achieved
• When regulations change

Balance Honesty and Aspiration

The best accessibility statements acknowledge current reality while demonstrating commitment to improvement. Don't claim conformance you haven't achieved—knowledgeable users and auditors will notice the gaps. But don't be so negative that users assume you've given up.

Frame limitations constructively: "We're aware that our legacy checkout process has accessibility issues. We're migrating to a new platform in Q3 2025 that addresses these concerns. In the meantime, please call 555-1234 for phone ordering assistance."

Taking Action

Whether legally required or voluntarily adopted, an accessibility statement serves your users and your organization. It demonstrates commitment, provides essential information, establishes feedback channels, and creates compliance documentation.

Start with the essential elements—conformance status, scope, limitations, and contact information—and expand from there. Review and update regularly. The goal isn't perfection but transparency and continuous improvement.

TestParty helps you maintain accurate accessibility statements by providing ongoing monitoring data about your actual compliance status.

Schedule a TestParty demo and get a 14-day compliance implementation plan.

Related Resources

• Accessibility Statement Template
• VPAT Creation Guide
• WCAG 2.2 Level AA Checklist
• EN 301 549 Compliance