Category: Compliance and Reporting

Accessibility Statement

Also known as: Website Accessibility Statement, Digital Accessibility Statement

Simply put

An accessibility statement is a public document in which an organization describes its commitment to making its digital content usable by people with disabilities. It commonly explains the steps the organization has taken, notes any known areas that may not yet be accessible, and offers a way for users to report problems or request help.

Formal definition

An accessibility statement is a published declaration, typically posted on a website, mobile application, or other digital property, that communicates an organization's approach to digital accessibility. Guidance from recognized authorities such as the W3C Web Accessibility Initiative and Section508.gov commonly recommends that a statement include the organization's commitment to accessibility, any technical standards or conformance targets it references, known limitations or inaccessible areas, and contact information for reporting barriers or requesting assistance. An accessibility statement is a communication and documentation practice rather than a technical conformance measure; publishing one does not by itself establish conformance with any WCAG version or level, nor does it guarantee legal compliance. Content, scope, and legal significance vary by jurisdiction and context, and this description is not legal advice.

Why it matters

An accessibility statement serves as a visible signal of an organization's commitment to digital inclusion. For users who rely on assistive technology, it provides reassurance that accessibility has been considered and, importantly, offers a clear channel to report barriers or request assistance when they encounter problems. Because no digital property is guaranteed to be free of accessibility issues, a statement that discloses known limitations and provides a feedback mechanism can help organizations identify and remediate problems that automated and manual testing may have missed.

Beyond user-facing benefits, an accessibility statement documents an organization's approach and can reflect the standards or conformance targets it references, such as a particular WCAG version and level. This documentation practice can support internal accountability and demonstrate good-faith effort. However, it is important to be clear about what a statement does not do: publishing an accessibility statement does not by itself establish conformance with any WCAG version or level, nor does it guarantee legal compliance. A statement is a communication and documentation measure, not a technical fix, and it should accurately reflect the actual state of a digital property rather than overstate its accessibility.

The content, scope, and legal significance of accessibility statements vary by jurisdiction and context. Organizations should treat a statement as one component of a broader accessibility program that includes testing, remediation, and ongoing maintenance. Because requirements evolve through regulation and case law, and because an inaccurate or overstated statement could itself become a liability, organizations should consult qualified legal counsel regarding the specific claims they make.

Who it's relevant to

Compliance Officers

Accessibility statements provide a documented record of an organization's stated accessibility commitments, referenced standards, and known limitations. Compliance officers should ensure the statement accurately reflects the actual state of digital properties, since an overstated claim could create risk rather than reduce it. A statement supports accountability but does not by itself guarantee legal compliance.

Accessibility Engineers and UX Designers

Practitioners often maintain the statement alongside testing and remediation work, updating known limitations as issues are found and fixed. The feedback channel described in a statement can surface real-world barriers encountered by users of assistive technology that automated and manual testing may not have caught.

Legal Counsel

The legal significance of an accessibility statement varies by jurisdiction and context, and this material is not legal advice. Counsel should review the specific claims made, particularly any conformance representations, and advise on how disclosures of known limitations and commitments are framed in light of current regulation and case law.

Business Leaders

An accessibility statement communicates an organization's commitment to digital inclusion to customers and the public. Leaders should understand that publishing a statement is one element of an accessibility program and does not substitute for testing, remediation, and ongoing maintenance.

Federal Agencies and Contractors

For federal contexts subject to Section 508, resources such as Section508.gov offer guidance on what a website accessibility statement should include. Section 508 standards apply to covered federal agencies and are distinct from the ADA's requirements for other entities, so the applicable authority should be identified before relying on any particular template.

Inside Accessibility Statement

Conformance Target

A statement of the accessibility standard the organization aims to meet, commonly WCAG 2.1 or 2.2 at Level AA. Well-drafted statements specify the version and conformance level rather than referring vaguely to 'accessibility guidelines', and may note whether conformance is full, partial, or in progress.

Scope and Coverage

A description of which digital properties the statement applies to, such as a specific website, mobile app, or subset of pages. Because conformance can vary across a large digital estate, identifying what is and is not covered helps set accurate expectations.

Known Limitations

A candid list of areas that are not yet fully accessible, such as third-party content, legacy documents, or specific features. Noting known issues reflects that meeting success criteria does not guarantee an accessible experience for every user and that remediation may be ongoing.

Feedback and Contact Mechanism

A way for users to report accessibility barriers, typically an email address, phone number, or form, ideally with an expected response timeframe. This provides an alternative channel for users who encounter problems.

Assessment and Testing Approach

An explanation of how accessibility was evaluated, which may reference automated testing, manual review, and assistive technology testing. Because automated tools detect only a portion of issues, describing the combined approach is more informative than citing automated checks alone.

Date and Revision Information

The date the statement was published or last reviewed, and where relevant a reference to the standard version used. Because requirements evolve through regulation and case law, and because sites change, a current review date signals whether the statement is up to date.

Common questions

Answers to the questions practitioners most commonly ask about Accessibility Statement.

Does publishing an accessibility statement make my website legally compliant with the ADA?

No. An accessibility statement is a communication and transparency tool, not a legal safe harbor. Posting a statement does not by itself establish compliance with the ADA or any other accessibility law, nor does it guarantee immunity from legal claims. Compliance generally depends on the actual accessibility of your digital content, which is assessed through the underlying experience for users of assistive technology and, in the legal context, through applicable statutes, regulations, and case law. This entry is not legal advice; consult qualified legal counsel regarding your specific obligations.

If my accessibility statement claims WCAG conformance, does that mean my site is fully accessible?

Not necessarily. A stated conformance target, such as WCAG 2.1 Level AA, reflects a goal or a claim about a point in time, but a written claim does not by itself demonstrate that the target has been met. Meeting WCAG success criteria also does not guarantee an accessible experience for every user, since automated testing detects only a portion of issues and manual and assistive technology testing are required. It is generally advisable to describe your conformance status accurately, including known limitations, rather than asserting full accessibility.

What information is commonly included in an accessibility statement?

Accessibility statements commonly identify the organization's commitment to accessibility, the conformance standard being targeted (for example, a specific WCAG version and level), the current conformance status, known limitations or areas still being addressed, and contact information for reporting barriers or requesting assistance. Some statements also describe testing methods used and the date the statement was last reviewed. The specific contents may vary by organization and jurisdiction.

Where should an accessibility statement be placed on a website?

An accessibility statement is commonly placed where users can locate it easily, such as in the site footer, so it is reachable from any page. The link and the statement page itself should be accessible to users of assistive technology. Making the statement easy to find supports its function as a channel for users to learn about accessibility efforts and report barriers.

How often should an accessibility statement be updated?

Because accessibility status can change as content and functionality evolve, an accessibility statement is generally treated as a living document rather than a one-time posting. Organizations often review and update it periodically and after significant site changes, and may include the date it was last reviewed. Keeping the stated conformance status and known limitations current helps the statement remain accurate.

Should an accessibility statement include a way for users to report problems?

Providing a feedback or contact mechanism is a common practice in accessibility statements, allowing users who encounter barriers to report them or request assistance. Offering more than one contact method (for example, email and phone) can help ensure users with different needs can reach the organization. Responding to reported issues supports the ongoing improvement that a statement typically describes.

Common misconceptions

Publishing an accessibility statement makes an organization legally compliant or immune from claims.

A statement is a communication tool, not a legal safe harbor. Meeting WCAG success criteria or describing accessibility efforts does not by itself guarantee compliance with the ADA, Section 508, or other authorities, nor does it guarantee immunity from legal claims. Organizations should consult qualified legal counsel regarding their obligations.

A statement claiming WCAG conformance means the site is fully accessible to all users.

Conformance to success criteria is distinct from real-world usability. Automated testing detects only a portion of issues, and manual and assistive technology testing are needed. Even a conforming site may present barriers for some users, which is why many statements include known limitations and a feedback channel.

Any generic accessibility statement will do, regardless of specifics.

Vague statements that omit the standard version, conformance level, scope, and contact method provide little useful information. Recognized guidance generally favors specificity so users and reviewers can understand what has actually been assessed and where to report problems.

Best practices

Specify the exact standard and level you target, such as WCAG 2.1 or 2.2 Level AA, rather than referring generally to 'accessibility guidelines', and note whether conformance is full, partial, or in progress.

Clearly define the scope of the statement, identifying which sites, apps, or sections it covers and, where relevant, what it excludes such as third-party or legacy content.

Describe how accessibility was evaluated, referencing manual and assistive technology testing alongside automated tools, since automated checks alone detect only a portion of issues.

Provide an accessible feedback mechanism, such as an email address, phone number, or form, and, where possible, an expected response timeframe for reported barriers.

Disclose known limitations honestly rather than claiming full accessibility, and describe any planned or ongoing remediation.

Include a last-reviewed date and revisit the statement periodically, since digital content changes and requirements evolve through regulation and case law; consult qualified legal counsel for compliance obligations.