Skip to content
VerscalaScan website

Accessibility statement generator

Fill in the form and copy a ready statement — plain text or HTML. The structure follows W3C WAI's guidance, and nothing you type leaves your browser.

This is a template, not legal advice. What a statement must contain — and whether you're required to publish one at all — depends on your country and sector. In EU scope the model statement uses “compliant”; W3C's own template says “conformant”. This tool follows whichever matches the standard you pick, but the facts you put in it are yours to verify.

The statement is made on this organisation's behalf.

What this statement covers — e.g. example.com or the Acme mobile app.

Name the standard you actually test against. EU-scope statements use EN 301 549 and its “compliant” wording; WCAG-only statements use “conformant”.

Describe the real, current state. Publishing “fully” when you know of open issues is the fastest way to lose credibility with both users and regulators.

Both are valid; saying which one is what makes the claim checkable.

Plain language, not criterion numbers — “older PDFs are not tagged” beats “fails SC 1.3.1”. Leave empty and the section is omitted rather than published empty.

A working channel is a required element of a statement — both in W3C WAI guidance and the EU model.

Browser and assistive-technology combinations, e.g. “NVDA 2025.1 with Firefox”.

Your statement

Accessibility Statement for [Organisation / Site Name]

[Organisation Name] is committed to ensuring digital accessibility for people with
disabilities. We are continually improving the user experience for everyone
and applying the relevant accessibility standards.

Conformance status
This website has been evaluated against WCAG 2.2 Level AA as of [date].
Based on a self-assessment completed on [date], [site/app name] is partially conformant with this standard.

Feedback
We welcome your feedback on the accessibility of [site/app name]. Please let us know
if you encounter accessibility barriers:
- Email: [address]
We try to respond to feedback within 5 business days.

Technical specifications
Accessibility of [site/app name] relies on the following technologies to work with the
particular combination of web browser and any assistive technologies or
plugins installed on your computer: HTML, CSS, JavaScript.

Preparation of this statement
This statement was prepared on [date] and last reviewed
on [date]. It was prepared using self-assessment.

A statement is a claim — make it one you can back

Every statement names a conformance status. Writing “fully compliant” is easy; standing behind it is not. Before you publish, it's worth knowing what an automated pass actually finds on your pages — missing alt text, unlabelled form fields, contrast failures and a missing statement link are the four that regulators check first.

Scan your site — freeOr find an agency to audit it properly

An automated scan is a floor, not a ceiling: it catches what tooling can prove, which is roughly a third of the criteria. If your statement claims an external audit, it needs a real one — here's exactly what we check and what we don't.

Other free checkers

All free checkers