How to Write an Accessibility Statement: Why It Matters + WCAG Guidance
An Accessibility Statement is one of the simplest and most effective ways an organization can show its commitment to accessibility and inclusion for people with disabilities. It gives customers and users a clear indication of your approach to digital accessibility and your broader responsibility.
Definition
An accessibility statement is a public-facing page on your website that outlines:
- your commitment to digital accessibility
- the standards you aim to meet (such as WCAG)
- known accessibility limitations
- contact details for support
- how you are improving over time
It is not a technical or legal report. It is communication for real users.
Why Accessibility Statements Matter
Promotes inclusion
An accessibility statement shows that an organization recognizes the diverse needs of its users, including people with disabilities, older users, and those who rely on assistive technologies. It reflects a commitment to equal access to information and services.
Builds transparency and trust
A good statement explains the current accessibility status of your website or application, including known limitations. Being open about both strengths and gaps builds trust and sets clear expectations.
Shows commitment
Publishing a statement is a visible way to demonstrate that accessibility is part of your values and digital strategy.
For many organizations, especially smaller teams, it’s a practical first step toward more inclusive digital services.
Supports users facing barriers
When users encounter accessibility issues, the statement provides a clear way to report problems or request help. This reduces friction and helps users access content in alternative ways when needed.
Supports compliance efforts
In many regions, accessibility regulations require or recommend publishing an accessibility statement. Including one can help demonstrate due diligence when supported by real accessibility work and ongoing improvements.
An accessibility statement shows that an organization recognizes the diverse needs of its users, including people with disabilities, older users, and those who rely on assistive technologies.
What Should a Good Accessibility Statement Include?
Accessibility commitment
A short, clear statement of your organization’s intent. Keep it direct and honest.
Standards and conformance level
State the standard you are working toward, such as WCAG 2.1 AA or WCAG 2.2 AA.
You can describe your conformance status using common categories:
- Fully conforms
- Partially conforms
- Does not conform
Be realistic. Avoid claiming full conformance unless it has been properly verified.
Known limitations
Be transparent about issues that:
- affect users
- are still present
- are being worked on
- come from third-party tools
Keep descriptions short, in plain language, and focused on user impact.
Testing approach
Explain how accessibility has been evaluated. This might include:
- automated testing tools
- manual audits
- assistive technology testing
- internal or external reviews
Accessibility features (optional)
Highlight features that may help users, such as:
- keyboard navigation support
- screen reader compatibility
- text resizing
- sufficient color contrast
- alternative text for images
Compatibility with browsers and assistive technology
Let users know which environments were used for testing. For example:
“This website has been tested with the latest versions of Chrome, Firefox, and Safari, and with screen readers such as NVDA and VoiceOver.”
Feedback and contact
Provide a clear way for users to:
- report accessibility issues
- request assistance or alternative formats
Use a real, monitored channel. Include expected response times where possible.
Dates
Include:
- the publication date
- the last review date
This shows the statement is actively maintained.
Continuous improvement
Make it clear that accessibility is ongoing. Let users know you regularly review and improve the experience.
How to Create an Accessibility Statement
Creating an accessibility statement does not require complex tools or legal language. A simple, structured approach works well.
Step 1: Identify your standard
Choose the WCAG version and level you are working toward. Include legal requirements if relevant.
Step 2: Define the scope
Clearly state what the statement covers (website, app, specific sections).
Step 3: Conduct an accessibility review
Use both automated and manual testing to understand your current state and identify known issues.
Step 4: Decide your conformance status
Choose a status based on your findings. Be conservative and accurate.
Step 5: Write user-focused issue descriptions
Explain what users may experience, where the issue occurs, and whether a fix is in progress.
Step 6: Add a contact method
Make sure the contact option itself is accessible and easy to use.
Step 7: Include compatibility details
Help users understand which environments provide the best experience.
Step 8: Publish and link it
Make the statement easy to find, typically from the website footer.
Final Thoughts
An accessibility statement is not about perfection. It’s about transparency, accountability, and steady progress.
Even for small organizations, a clear and honest statement is a practical step toward more inclusive digital services.
If you need support drafting an accessibility statement, conducting an audit, or improving your WCAG conformance, the Ally team can help guide you through the process.
