By Nilesh Gadekar, Founder · Last reviewed .
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 and review the deadline estimator.
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.