When to use this

Before publishing a new statement or updating an old one. Compare the draft against actual test results and known limitations.

What to include

  • Honest current status
  • Known limitations (PDFs, third-party widgets, etc.)
  • Clear feedback method
  • Last reviewed date
  • Caution against over-claiming

What not to claim

Never claim “WCAG 2.1 Level AA compliant” or “fully accessible” without qualified human testing and ongoing monitoring. Automated tools alone are not enough.

# Accessibility statement review — [Organization / Site]

**Organization/site:** [Name]
**Stated target:** [e.g., WCAG 2.1 Level AA]
**Current status:** [Automated check complete / Manual review in progress / Known limitations documented]
**Known limitations:** [List honestly]
**Feedback method:** [Email / form / phone]
**Last reviewed date:** [YYYY-MM-DD]
**Review notes:** [What to improve or clarify]
**Caution:** Do not claim conformance without evidence from qualified human testing. This template helps keep statements accurate and useful.

---
*Generated with SiteCheck Canada*

Related: Accessibility statement generator · How to write an accessibility statement

Recommended next steps

Generate statement Create a draft statement. How to write a statement Best practices for honest statements. Run the checker Document current automated status.