Process

Accessibility Statement: What to Include and Why It Matters

By EZUD Published · Updated

Accessibility Statement: What to Include and Why It Matters

An accessibility statement is a public declaration of your organization’s commitment to digital accessibility. It tells users with disabilities what to expect from your product, what barriers may still exist, and how to get help or report issues. Beyond good practice, accessibility statements are required or recommended by several regulations, including the European Accessibility Act (EAA) and EN 301 549 in the EU, and are referenced in Section 508 guidance in the United States.

Why Publish an Accessibility Statement

  • Transparency. Users with disabilities can make informed decisions about whether your product meets their needs.
  • Trust. A detailed, honest statement signals that your organization takes accessibility seriously rather than treating it as a checkbox.
  • Legal compliance. The EAA and EN 301 549 require public sector bodies in the EU to publish accessibility statements. In the U.S., federal agencies must post Section 508 conformance information.
  • Feedback loop. A statement with clear contact information invites users to report barriers you may not have detected.

Essential Components

Conformance Level

State the WCAG version and conformance level you target or have achieved. Common phrasing: “This website aims to conform to WCAG 2.2 Level AA.” If a formal audit has been completed, state the result: “An independent audit conducted on [date] by [auditor] found this site to be partially conformant with WCAG 2.2 Level AA.”

Be honest. If the site is not fully conformant, say so. “Partially conformant” is more credible and legally defensible than a vague claim of full compliance.

Known Limitations

List specific accessibility barriers that you are aware of. For each limitation, describe:

  • The nature of the barrier
  • The content or functionality affected
  • The reason it exists (third-party content, legacy system, active remediation)
  • Your plan and timeline for addressing it

Example: “The interactive map on our Locations page does not provide keyboard access. We are working with the vendor to implement an accessible alternative by Q3 2025.”

Assistive Technologies Supported

Describe which browser and assistive technology combinations the site has been tested with. This helps users understand what to expect. Example:

  • NVDA with Chrome on Windows
  • JAWS with Chrome on Windows
  • VoiceOver with Safari on macOS and iOS
  • TalkBack with Chrome on Android

Feedback Mechanism

Provide a clear way for users to report accessibility barriers. Include:

  • Email address (monitored regularly)
  • Phone number (with TTY or relay service option)
  • Web form (which must itself be accessible)
  • Expected response time

The W3C WAI provides a template for an accessibility feedback form that meets these requirements.

Enforcement and Escalation

If applicable under your jurisdiction, explain how users can escalate complaints. In the EU, this includes the national enforcement body. In the U.S., users can file complaints under Section 508 (for federal agencies) or file ADA complaints with the Department of Justice.

Date and Review Cycle

State when the statement was last reviewed and when it will be reviewed again. Accessibility statements should be updated at least annually or after major site changes.

  • Organizational commitment. A brief paragraph on your accessibility goals, such as achieving full WCAG 2.2 Level AA conformance, conducting annual accessibility audits, and including disabled users in usability testing.
  • VPAT/ACR link. If you publish a Voluntary Product Accessibility Template, link to it from the statement. See our guide on VPATs and ACRs.
  • Training and governance. Mention ongoing accessibility training and governance frameworks to show systemic commitment.

Where to Publish

  • Place the statement on a dedicated page linked from the site footer, typically labeled “Accessibility” or “Accessibility Statement.”
  • Ensure the statement page itself is fully accessible: proper heading hierarchy, sufficient contrast, readable font size, and keyboard navigability.
  • Some organizations also include a brief accessibility notice in their site footer with a link to the full statement.

W3C Generator Tool

The W3C WAI Accessibility Statement Generator walks organizations through creating a conformant statement. It produces a structured document that covers all the elements above and follows international best practices.

Key Takeaways

  • Accessibility statements are both a legal requirement in many jurisdictions and a trust signal for disabled users.
  • Be honest about conformance level and list known limitations with remediation timelines.
  • Provide clear, accessible feedback mechanisms with expected response times.
  • Update the statement at least annually and after major product changes.
  • Link the statement from your site footer and ensure the page itself is fully accessible.

Sources

More in Process

Inclusive Design Process Guide: Building Accessibility Into Every Stage Guide Continuous Accessibility Monitoring Accessibility in Design Reviews Nothing About Us Without Us: The Principle That Shapes Inclusive Design

View all Process articles →