Publishing an accessibility statement

A published statement is the cheapest compliance artefact you can produce and the first thing a regulator looks for. It is also the one place where honesty is legally safer than optimism.

What it must contain

1. The standard you are measuring against, with its level — for example WCAG 2.2 Level AA.
2. Your conformance status: fully, partially, or not conformant. Partially is the honest answer for most sites.
3. A specific list of the content that is not yet accessible, and why.
4. The date of the assessment and the method used — self-assessment or third-party audit.
5. A feedback route: an email address or form, with a stated response time.
6. The escalation route, where national law requires one.

Generating one

Open a site, choose Accessibility statement, and fill in the assessment date, contact address and known limitations. The dashboard produces HTML you can paste into a page on your own domain, then link back from the widget so visitors can reach it.

Keeping it current

Review it whenever you ship a significant change, and at least once a year. Date every revision — a statement with a stale date is the first thing a reviewer questions.