An Accessibility Statement is a public document that describes how accessible your website, mobile app, or digital product is for people with disabilities. It communicates your organization’s commitment to inclusive design, outlines your conformance with accessibility standards such as WCAG, and provides a clear way for users to report accessibility barriers.

Governments, enterprises, and global accessibility standards now strongly recommend or require Accessibility Statements as part of compliance and procurement processes. Whether your organisation operates locally or serves a global audience, publishing an Accessibility Statement demonstrates transparency, accountability, and a commitment to designing for everyone.

This guide explains what an Accessibility Statement is, why it matters, what it should include according to W3C guidance, and how to write one using globally recognized best practices.

What is an Accessibility Statement

The W3C Web Accessibility Initiative (WAI) defines an Accessibility Statement as a transparent disclosure that:

• Describes the accessibility of a website or app
• States the standards or guidelines followed, such as WCAG 2.1 AA or WCAG 2.2 AA
• Identifies known issues and limitations
• Explains accessibility features
• Provides clear contact information for reporting barriers
• Communicates steps taken for ongoing improvement

The purpose of an Accessibility Statement is to help users understand the current level of accessibility, know what to expect, and find support when necessary.

Why Accessibility Statements Matter Globally

Accessibility Statements are required or strongly encouraged across many regions. They play a key role in helping organizations meet legal expectations and demonstrate responsible digital practices.

United States

The Americans with Disabilities Act and Section 508 expect digital accessibility. Accessibility Statements are widely used in government and enterprise procurement processes.

European Union

The EU Web Accessibility Directive requires public sector websites and apps to publish Accessibility Statements in a standardized format. EN 301 549 defines expectations for digital products and services.

United Kingdom

Public institutions must publish Accessibility Statements under the Public Sector Bodies Accessibility Regulations. These statements must include conformance details and known issues.

Canada

AODA and the Accessible Canada Act require transparency around accessibility achievements and barriers. Accessibility Statements support reporting requirements for government and enterprise.

Australia

The Disability Discrimination Act encourages accessible digital experiences. Government agencies commonly include Accessibility Statements in accessibility plans and documentation.

India

Under the Rights of Persons with Disabilities Act and the digital accessibility standard IS 17802, organizations benefit from publishing Accessibility Statements to demonstrate proactive compliance.

Even in countries without specific regulations, Accessibility Statements are considered a global best practice for inclusive and responsible digital design.

What an Accessibility Statement Should Include (Based on W3C Guidance)

W3C recommends using a clear, structured format that allows users to quickly understand accessibility status and available support. Each element below contributes to transparency and usability.

1. Commitment to accessibility

Start with a clear declaration of your dedication to inclusive digital experiences. Use simple language and describe accessibility as part of ongoing improvement rather than a one-time project.

2. Applicable standards and specifications

List the accessibility guidelines you follow, such as WCAG 2.1 AA or WCAG 2.2 AA. You may also reference national standards or industry requirements where relevant.

3. Accessibility status

State your level of conformance using one of the terms recommended by W3C.

• Fully conforms
• Partially conforms
• Does not conform

If your product does not fully conform, briefly explain why and outline planned improvements.

4. Known accessibility limitations

Provide details related to issues users may encounter, including who may be affected and whether remediation work is in progress. Transparency builds trust and sets realistic expectations.

5. Measures taken to support accessibility

Describe the internal processes that ensure accessibility is embedded in development and continuous improvement. Examples include developer training, design guidelines, accessibility reviews, or third-party audits.

6. Methods used for evaluation

State how accessibility testing was performed. Examples include self-assessments, external evaluations, automated testing tools, and manual testing with assistive technologies like screen readers or keyboard navigation.

7. Feedback mechanism

Offer one or more accessible contact methods for users to report issues. Include an email address, phone number, or accessibility feedback form. Inform users how quickly they can expect a response.

8. Compatibility with browsers and assistive technologies

Clarify which browsers, assistive technologies, and operating systems your website or product has been tested with. Providing this information helps users understand the environments that deliver the best experience.

Example:
This website has been tested with the latest versions of Chrome, Edge, Firefox, and Safari, and with screen readers including NVDA and VoiceOver.

9. Technical prerequisites

List any requirements needed to use your site, such as modern browser support, JavaScript enabled, or reliance on WAI ARIA. This helps users better prepare their settings.

10. Date of publication and updates

Include the date the Accessibility Statement was created and the last review date. W3C recommends updating the statement regularly to keep information accurate and aligned with product changes.

How to Write an Accessibility Statement Step by Step

The process below aligns with W3C recommendations.

Step 1. Identify the accessibility standard you follow

Choose the WCAG version and conformance level. Include legal or regulatory requirements where relevant.

Step 2. Conduct an accessibility evaluation

Use a combination of automated and manual testing. Evaluation can be completed internally or by certified accessibility professionals.

Step 3. Declare your level of conformity

Do not claim full compliance unless verified. Accuracy is essential for trust.

Step 4. List known issues and limitations

Inform users about barriers they may encounter and describe planned improvements.

Step 5. Provide an accessible feedback channel

Make it easy for users to share concerns or request accessible alternatives.

Step 6. Add compatibility and technical information

Help users understand conditions that provide the best experience.

Step 7. Add a review and update plan

Organizations often review Accessibility Statements every six to twelve months.

Your Next Step in Accessibility Compliance

An Accessibility Statement is more than a formality. It reflects your commitment to transparency, inclusive design, and an equitable digital experience for all users. Following W3C guidance enables you to publish a clear and trustworthy statement that supports compliance and strengthens your digital accessibility posture.

Whether you manage a government platform, a large enterprise application, or a growing digital product, publishing an Accessibility Statement is a practical and valuable step in your accessibility journey.

If you need assistance drafting an Accessibility Statement, conducting an accessibility audit, or improving your WCAG conformance, the team at Pivotal Accessibility can support you at every stage.