Accessibility Statement for a Website: Practical Template

Accessibility statement for a website: what it should do

An accessibility statement for a website should help a visitor understand the site's accessibility work and get assistance when something does not work. W3C's Web Accessibility Initiative recommends including a commitment to accessibility, the standard being applied, and contact information. It also advises explaining known limitations, measures taken, technical prerequisites, tested environments, and the assessment approach when those details are available.

The statement is not the accessibility work itself, a technical audit, or a universal legal shield. Publishing an unsupported claim of full conformance can be less useful than plainly describing what has been evaluated, what remains difficult, and how the organization will respond. Requirements vary by country, sector, and organization, so a regulated or high-risk service should have its exact obligations reviewed by qualified counsel.

Start with a commitment you can maintain

Use direct language that includes people with disabilities and names the website or digital service covered. A small organization can say it is committed to making its website usable and improving barriers it identifies. Avoid promising that every page works with every assistive technology unless a credible evaluation supports that statement.

Name an accessibility target only when the team understands it. WCAG 2.2 is a W3C technical standard for making web content more accessible. If the organization uses WCAG 2.2 Level AA as a target, say that it is the target or basis for the work. Do not turn a target into a conformance claim without appropriate evidence.

Give visitors a feedback route that actually works

Provide a monitored email address, accessible form, phone route, or another method appropriate to the organization. Tell visitors what information will help: the page address, the task they were trying to complete, the barrier they encountered, and their preferred way to receive the content or service.

Set an internal owner and response expectation that the organization can meet. Do not publish a fast response promise if the mailbox is reviewed only occasionally. Test the contact route with a keyboard and verify that form errors, confirmation messages, and email notifications work.

• Page URL or name
• The task the visitor was trying to complete
• A plain-language description of the barrier
• Requested accessible alternative, when applicable
• Preferred contact method

Describe known limitations honestly

Name the content or function, explain the observable problem, and offer an alternative when possible. Plain language such as "some archived videos do not yet have captions" is more useful than citing only a success-criterion number. Add what is being done and a realistic review or repair plan.

Do not hide known problems behind a general statement that the site is a work in progress. Prioritize barriers that stop people from completing essential tasks. Update the statement when a limitation is fixed, when a new platform changes the experience, or when an assessment finds another material issue.

Record how and when the site was assessed

State whether the assessment was a self-evaluation, an external evaluation, or a combination. List the parts of the site and representative user journeys covered when that context matters. Automated scanning can support an assessment, but it cannot determine every accessibility requirement or replace testing with people and assistive technologies.

Add the date the site was assessed and the date the statement was reviewed. If the organization has not completed a formal conformance evaluation, say so. A short, accurate method note gives the reader more context than a badge with no supporting report.

Use this practical accessibility statement template

Replace every bracketed field with verified information. Remove sections that do not apply rather than leaving placeholder claims. Have the statement reviewed by the people who own the website, accessibility work, customer support, and legal obligations.

Accessibility statement for [website or organization]

[Organization] is committed to making [website or service] usable by people with disabilities. We use [standard or internal target] to guide our accessibility work.

Feedback and assistance
If you encounter an accessibility barrier, contact us at [monitored contact method]. Please include the page address, the task you were trying to complete, and your preferred contact method. We aim to [accurate response process or timeframe].

Known limitations
- [Content or function]: [plain-language limitation]. [Available alternative or remediation plan].

Assessment approach
This website was evaluated through [self-evaluation, external evaluation, user testing, tools, or other verified method]. The most recent review was completed on [date].

Compatibility and technical information
The site is designed to work with [verified browsers, devices, and assistive technologies]. It relies on [relevant technologies, if useful].

This statement was last updated on [date].

Publish it where people can find it

Use a stable page titled "Accessibility statement" and link it consistently from the site footer. W3C also suggests prominent locations such as a help menu, sitemap, or about page. Keep the link available on mobile layouts and authenticated areas when the statement covers those experiences.

Review the statement on a schedule and after a redesign, platform migration, major feature launch, or accessibility evaluation. Track reported barriers through the same issue process used for other product defects. The statement becomes credible when it reflects a maintained operating practice.