# A starting point for your accessibility statement.

Canonical page: https://districtproof.io/resources/accessibility-statement-template

Describe your real scope, testing, known barriers, and help process. Replace the bracketed prompts with verified district information, and have the appropriate staff and counsel review the statement.

By [Nilesh Gadekar, Founder](https://districtproof.io/about#founder) · Last reviewed November 4, 2026.

This is an editable planning template. Its bracketed prompts are intentional instructions for the district author, not a finished public statement.

Template text — you can also select and copy it here

```text
[District name] accessibility statement

We aim to make our website and public information usable by people with disabilities.

Standard and scope
[Describe the standard you work toward, the web properties covered, and the limits of this statement.]

How we review accessibility
[Describe actual testing methods, coverage, dates, and the team responsible.]

Known issues
[List known barriers, affected content, alternatives, and the expected follow-up where confirmed.]

Request help or report a barrier
Contact [verified email and phone]. Tell us the page or document, the task you were trying to complete, and your preferred contact method. Do not send sensitive information.

Response process
[State the actual response process and an achievable timeline.]

Last reviewed: [date]
Statement owner: [department / role]
```

## Keep the statement accurate

Do not claim completed tests, fixed issues, certifications, or response times that your team has not verified. Provide a way to request help that does not rely on the inaccessible content itself.

## Pair the statement with a working process

A statement supports communication; it does not repair content. Explore [DistrictProof Web](https://districtproof.io/solutions/web) and review the [deadline estimator](https://districtproof.io/resources/deadline-calculator).

## Have the right people review the statement

The communications owner can check clarity and contact routes. Technology can confirm the listed web properties and test methods. The person responsible for accessibility requests can verify the help process. Counsel can review legal wording and any statements about obligations. Do not rely on a generic template to settle those questions.

A statement should be easy to find from the website and should offer a usable route for reporting a barrier. The contact method should not depend on completing the very task a person is unable to use. Confirm that the mailbox or other channel is monitored and that staff know how to route a request.

## Use known issues to describe the next action

A useful known-issue entry identifies the affected page or content type, the barrier, an available way to obtain help, and the responsible follow-up where confirmed. Avoid a vague sentence that tells the reader nothing about what they can do. Do not promise a resolution date that has not been agreed.

Review the statement when the website, contact process, or testing coverage changes. Keep a clear review date and owner. Accessibility work continues in the content and services themselves; the statement explains that work and provides a path to help.