A highly searched question on website compliance happens to be “What is an accessibility statement?” This is because the term has been thrown around quite often and a lot of website owners need clarity on whether they require one.
An accessibility statement is a public page on your website that explains your commitment to digital accessibility, describes your site’s current conformance status against a recognized standard such as WCAG, and tells users with disabilities how to report a problem or get help. Think of it as the accessibility equivalent of a privacy policy: part legal record, part user communication tool.
Over 5,100 federal ADA website lawsuits were filed in 2025, up 37% year over year. The DOJ has required publication of an accessibility statement in ADA Title III settlements. The European Accessibility Act, enforceable since June 2025, mandates one for all businesses selling digital services in the EU. If your website does not have one, this guide tells you exactly what you need and how to create it.
What Is an Accessibility Statement?
An accessibility statement is a page on your website that explains how you’re making your website accessible to people with disabilities. It tells visitors what you’re doing to improve accessibility, what accessibility features your site offers, and how they can get help if they run into any problems.
It is not a technical report or a legal document that says your website is fully compliant with accessibility standards. Instead, it’s written in simple language so everyone can understand it. If someone with a disability has trouble using your website, the accessibility statement is usually the first place they’ll look for information or support.
What Is the Difference Between an Accessibility Statement and a VPAT?
An accessibility statement is a page that anyone visiting your website can read. It explains your commitment to accessibility, mentions any known accessibility issues, and provides a way for people to contact you if they need help.
A VPAT (Voluntary Product Accessibility Template) is different. It is a detailed technical document used mainly by government agencies and large organizations when deciding whether to buy a product or service. It explains how well a product meets accessibility standards.
In simple terms, an accessibility statement is written for your website visitors, while a VPAT is written for organizations that need detailed accessibility information before making a purchase. Many businesses that work with government agencies or large companies need both.
Does Your Website Legally Need an Accessibility Statement?
The legal requirement depends on your jurisdiction and the type of organization you run.
| Organization Type | Requirement | Legal Basis |
| EU public sector websites | Mandatory | EU Web Accessibility Directive |
| EU private sector digital services | Mandatory (since June 2025) | European Accessibility Act (EAA) |
| UK public sector websites | Mandatory (specific template required) | UK Accessibility Regulations |
| US federal agencies | Mandatory | Section 508 / OMB Memorandum M-24-08 |
| US state and local government websites | Strong best practice, required in settlements | ADA Title II (DOJ 2024 rule) |
| US private businesses | Not explicitly required, but strongly recommended | ADA Title III (courts reference it in settlements) |
In the United States, there is no federal law that explicitly requires private businesses to publish an accessibility statement. That said, the DOJ has required accessibility statements as part of ADA Title III consent decrees and settlements. Courts treat the presence of one as evidence of good-faith compliance effort. Its absence, when a complaint is filed, can work against you.
For any US business that wants to demonstrate good faith under the ADA, publishing an accurate, up-to-date accessibility statement is one of the simplest and most effective steps you can take.
What Must an Accessibility Statement Include?
A good accessibility statement should include the following:
- A commitment to Accessibility. Explain that your organization is committed to making its website or app accessible to people with disabilities. Clearly mention which website or app the statement applies to.
- The Accessibility Standard You’re Following. State the accessibility standard you’re working toward, such as WCAG 2.1 Level AA or the newer WCAG 2.2 Level AA.
- Known Accessibility Issues. Be honest about any parts of your website that aren’t fully accessible yet. Describe these issues in simple language. For example, instead of saying “WCAG Success Criterion 1.2.2 was not met,” say “Some older videos do not have captions.”
- Contact Information. Tell users how they can report accessibility problems or request help. Include at least two contact options, such as an email address, phone number, or contact form. It’s also helpful to let users know how quickly they can expect a response.
- The Last Update Date. Include the date the accessibility statement was last reviewed or updated. Review it regularly, especially after making major changes to your website.
- Technical Details (optional but recommended). You can also mention which browsers, devices, or assistive technologies your website has been tested with, any known compatibility issues, and alternative ways to access content if some features are not yet fully accessible.
- Relevant Accessibility Laws (if applicable). If your business must comply with specific accessibility laws, mention them. For example, businesses in the European Union may need to reference the European Accessibility Act, while businesses in the United States often mention the ADA and WCAG.
What Should an Accessibility Statement Not Include?
Don’t claim that your website is fully WCAG compliant unless it has been confirmed by a recent professional accessibility audit. Making false or exaggerated claims can damage your credibility and may create legal risks if your website still has accessibility problems.
Instead, be honest about your current level of accessibility, acknowledge any known issues, explain what you’re working to improve, and provide a clear way for users to contact you if they need assistance.
How to Write an Accessibility Statement
Keep it Simple:
The W3C is explicit. Accessibility statements are for users, not lawyers or web developers. Avoid technical jargon. If you use terms like WCAG or ARIA, define them. Write at a reading level that most visitors can understand.
Be Honest About Limitations:
A statement that acknowledges known issues and provides a clear contact path is far more useful and credible than a vague pledge. Users with disabilities read these statements because they need help. Give them actionable information.
Make it Easy to Find:
Link to your accessibility statement from your website footer alongside your privacy policy and terms of service. Some organizations also link from their homepage, help center, and sitemap. The harder it is to find, the less useful it is.
Update it regularly.
Accessibility statements should be reviewed and updated at least once a year, and whenever you make significant changes to your site, install new tools, or complete a new accessibility audit. An outdated statement that references work you did three years ago is not a compliance asset.
How ADAcertify Helps You Create and Maintain Your Accessibility Statement
ADAcertify generates your accessibility statement as part of your compliance documentation, alongside your audit report and VPAT. The statement is created from your site’s actual scan data, reflecting your real conformance status rather than a generic template with blanks you fill in manually.
When your site changes or you complete a new audit, your statement updates to reflect the current state of your accessibility work. That means your statement is always accurate, which is the most important thing it needs to be.
What Is an Accessibility Statement: Summary
An accessibility statement is a public page on your website that tells users with disabilities what standard you are working toward, what works, what does not yet work, and how to reach you for help. In the EU it is legally mandatory for both public sector and private sector digital services. In the US it is not explicitly required for private businesses but is strongly recommended as a good-faith compliance measure and is required as part of many ADA settlement agreements.
The most important thing your accessibility statement can do is be accurate. A statement that honestly reflects your compliance effort, acknowledges known limitations, and provides real contact information is both more useful to users and more defensible if your site is ever challenged.
Frequently Asked Questions About Accessibility Statements
Does an accessibility statement protect you from ADA lawsuits?
Not by itself. A statement demonstrates good faith, which courts consider. But the most important protection is genuine accessibility work: audits, remediation, monitoring. A statement attached to a site with hundreds of WCAG failures offers little legal protection. A statement that accurately reflects an ongoing, documented compliance program is a meaningful part of your legal defense.
How long should an accessibility statement be?
There is no required length. Most effective statements run between 300 and 800 words. They are long enough to cover all required elements and short enough that users with disabilities will actually read them. Prioritize clarity over length.
Can I use a template for my accessibility statement?
Yes. The W3C provides a free accessibility statement generator at w3.org/WAI/planning/statements. Templates are a good starting point, but your statement must be customized to reflect your actual site’s conformance status, known limitations, and contact information. A generic template left unchanged is not an accurate statement.
How often should I update my accessibility statement?
At minimum once a year. Also update it after any major site redesign, after completing a new accessibility audit, after installing or removing accessibility tools, and whenever your contact information for accessibility feedback changes.
