Audit operations
Write an Evidence-Based Accessibility Statement
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Publish a statement that helps visitors understand accessibility support, known limitations and how to report a problem. Base claims on a documented evaluation and give the statement a real owner and update process.
A practical example
A site has completed a scoped audit but still has a known issue in an external booking widget.
How to check it
- Gather the evaluated scope, target standard, methods and date. Separate verified results from goals and work still in progress.
- Describe known limitations in useful language and provide a working feedback route. Include the information a visitor needs to identify the affected page and request help.
- Review the statement for accuracy, publish it accessibly and test the contact route. Update it when a significant repair or product change affects its claims.
What can be missed
A statement that says the site is fully compliant without supporting evidence can mislead visitors. Generic promises are less useful than specific scope and honest limitations.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.