Digital Accessibility Statement: What to Include and Why

An accessibility statement sits on your website to explain how accessible your digital properties are and how people can report barriers they encounter. It's a straightforward practice that has become increasingly common, though many companies still aren't sure what to include or whether they actually need one.

The answer is simple: if you have a website or web application that people with disabilities use—and they do—an accessibility statement is reasonable practice. It doesn't require perfect accessibility to publish one. It just requires honesty about where you are and commitment to improving.

Why an Accessibility Statement Matters

An accessibility statement serves several purposes. For visitors with disabilities, it signals that you've thought about accessibility and provides a clear way to report problems. It also demonstrates to regulators, auditors, and potential customers that accessibility is part of your operational thinking.

Most importantly, it removes ambiguity. If someone encounters a barrier on your site—a video without captions, a form field without a proper label, a color contrast that's too low—and can't use a feature because of that barrier, they want to know: is this an oversight, or is this site simply not designed for people like me? An accessibility statement answers that question. It says, in effect, we're working on this, and here's how to let us know when something doesn't work.

This applies regardless of legal requirements in your jurisdiction. An accessibility statement is simply a responsible practice for any website that serves the public or has users.

What to Include in Your Accessibility Statement

Start with a declaration of intent. This is one or two sentences explaining your commitment to accessibility and your goal to make your digital properties usable by everyone.

Example: "We're committed to making our website accessible to everyone. We've worked to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, and we're continuously making improvements."

Be honest about your current level of accessibility. You don't need to achieve perfect compliance before publishing a statement, but don't overstate where you are. If you've met WCAG Level AA in most areas but know some pages haven't been audited yet, say that.

Include what accessibility standards or guidelines you've used as your reference. WCAG 2.1 is the most widely recognized standard. Mention the level—AA is a reasonable target for most websites. AAA is more intensive and typically only required for specific contexts like government sites.

List the accessibility features you've implemented. Have you ensured color contrast meets standards? Do videos have captions? Are images properly labeled for screen readers? Have you tested keyboard navigation? Include specific features you've addressed.

Acknowledge areas where you're still working or where accessibility might be limited. This is important. If you know certain sections of your site are less accessible, or if you haven't yet adapted all older content, be direct about it.

The Feedback and Reporting Mechanism

A statement is incomplete without a clear way for people to report accessibility issues. Provide a dedicated email address and, if possible, a web form where people can report barriers.

Example: "If you encounter an accessibility barrier on our website, please let us know at accessibility@company.com. Include a description of the barrier, the page where you encountered it, and how it affected your ability to use that page. We'll get back to you within 5 business days."

Be specific about your response time and what will happen after someone reports an issue. Will someone review it? Escalate it to the product team? Send you an update? Set realistic expectations and meet them. If you say you'll respond within 5 business days, do that consistently.

Some companies publish a log of known accessibility issues and their status—open, in progress, resolved. This shows transparency and demonstrates that you're actually tracking and fixing problems rather than ignoring them.

Avoid Overclaiming Compliance

Many websites publish accessibility statements that claim to be fully WCAG compliant when they're not. This undermines the entire practice. Audits cost time and money, and most websites have some accessibility gaps.

The better approach is to be accurate. "We have conducted a WCAG 2.1 Level AA audit of our main pages and core user flows" is more honest than a blanket claim of full compliance. "We continue to work on improving accessibility across our site" acknowledges that it's an ongoing effort, not a finished product.

If you haven't done a formal audit, you can say that too. "We've implemented accessible design practices and tested our site with assistive technologies, but have not conducted a third-party audit" is a reasonable statement that sets expectations accurately.

Accessibility Statement Format and Placement

Place your accessibility statement where people can find it. Common locations are the footer of your site, a dedicated /accessibility page, or as part of your site navigation in a help or about section.

Write it in plain language. Avoid jargon or overcomplicated explanations. A person visiting your site to report a barrier should be able to read your statement quickly and understand what to do next.

Keep it concise. An accessibility statement doesn't need to be long. 3-5 paragraphs is typically sufficient.

FAQ: Common Questions About Accessibility Statements

Do I need an accessibility statement if I'm a small business? It depends on your situation. If you have a website and serve the public, an accessibility statement is reasonable practice. It doesn't require massive resources—just honesty about where you are.

What if I'm not sure what accessibility standards to use? WCAG 2.1 is the most widely recognized and referenced guideline. Targeting Level AA is a reasonable middle ground. You don't need to be an expert; research what WCAG 2.1 Level AA means and communicate that as your target.

Can I remove or update my statement later? Yes. Your statement should evolve as your accessibility efforts evolve. Update it when you complete major improvements, when you discover new issues, or when you shift your approach.

Should I hire an accessibility consultant? It depends on the scope of your site and your internal expertise. A consultant can conduct an audit, identify barriers, and recommend fixes. For some companies this is worthwhile; for others, starting with a statement and fixing reported issues is a reasonable approach.

What if someone reports an issue I can't fix? Respond honestly. If fixing an issue would require rebuilding a major section of your site or a technology change you can't make immediately, explain that. Offer a workaround if you have one, and commit to fixing it in your roadmap. Ignoring reports is worse than slowly addressing them.

How often should I update my accessibility statement? At least annually, or whenever you make significant changes to your website or accessibility practices. If you're actively fixing reported issues, update it to reflect your progress.

The Legal and Ethical Case

In some jurisdictions, accessibility statements are part of legal compliance frameworks. In others, they're purely best practice. Regardless, they serve an ethical purpose: they acknowledge that accessibility is part of your responsibility as a website operator.

An accessibility statement is not a liability protection, and it shouldn't be treated as one. It's a communication tool. It tells people how you're thinking about accessibility and how they can participate in making your site better.

Next Steps

If you don't have an accessibility statement, write one this week. Use the framework outlined above: declare your intent, list what you've done, acknowledge what needs work, and provide a way for people to report barriers. You don't need it to be perfect. You need it to be honest and useful.

If you already have a statement, review it. Is the contact information current? Does it accurately reflect your current accessibility status? Is there a better way for people to report issues? Small improvements to your statement compound over time.

Accessibility is not a one-time project. It's an ongoing practice. Your accessibility statement is part of that practice—a clear signal that you're thinking about the people who use your site and how to serve them better.