Accessibility Statement Generator
Answer a few questions about your website and get a structured, professional accessibility statement you can publish. It covers your commitment, conformance status, standards, measures, known limitations, assessment approach, and how people can report a barrier — generated entirely in your browser.
- Ready In Minutes
- No Sign-up
- Runs In Your Browser
Accessibility statement generator
Organisation and website
Used throughout the statement to describe who is responsible and what the statement covers.
With or without https:// — we will normalise it.
Your own wording, if you have it. Otherwise we write a neutral commitment paragraph for you.
Standards and conformance
Choose the standard you are working to and describe your current position honestly — a statement that overclaims is worse than one that admits gaps.
Measures and limitations
What you already do to support accessibility, and what you know is not working yet.
One measure per line. Each becomes a bullet in the statement.
One limitation per line. Leave blank if you have none recorded — the statement will say so and invite feedback.
Assessment
How the accessibility of the site was checked.
Only used when an external evaluation was involved.
Feedback and contact
How people can tell you about an accessibility barrier. A statement without a working contact route is not much use.
How quickly you aim to reply to accessibility feedback.
Leave blank to use today's date.
Everything stays in your browser — nothing is uploaded or stored.
Your statement will appear here
Fill in the form above and select Generate accessibility statement. You can edit your answers and regenerate as many times as you like.
About accessibility statements
What they are for, who asks for them, and how to keep yours credible.
What an accessibility statement is
A public page that explains how accessible your website is, what standard you are working to, what does not work yet, and how someone can report a barrier. It is a commitment and a contact route, not a certificate.
Why publish one
Several laws and procurement processes expect a statement. The European Accessibility Act and public-sector rules in the EU and UK require one; US buyers and enterprise procurement teams routinely ask for it alongside a VPAT.
Be honest about gaps
A statement that claims full conformance while obvious barriers remain is worse than one that lists known issues and a plan. Regulators and claimants read these pages, and an overstated claim is easy to disprove.
Keep it current
Review the statement whenever you redesign, add a major feature, or complete remediation work. A statement dated three years ago signals that accessibility is not actively maintained.
The standard behind almost every statement is WCAG, referenced in turn by the ADA, the European Accessibility Act, and Section 508. You can see how Zylyn words its own on our accessibility statement.
Want to find more accessibility issues? Run a full scan.
Contrast is one success criterion out of dozens. Zylyn checks your live page against WCAG 2.2 in about 90 seconds and returns every issue it finds — contrast, alt text, labels, headings, keyboard traps and more — grouped by severity.
Related resources
A statement is a starting point. These cover the testing and standards behind it.
- Free ToolColour Contrast Checker
Check any colour pair against WCAG 2.2 and get instant AA and AAA pass or fail results.
- Compliance GuideWCAG Compliance Guide
POUR principles, conformance levels A/AA/AAA, and which laws require WCAG.
- Compliance GuideEuropean Accessibility Act
Who the EAA applies to, what it requires, and why it expects a published statement.
- ServiceAccessibility Audit
Prioritised findings report with every issue tagged by WCAG criterion, severity, and fix.
- ServiceVPAT & ACR Services
The conformance documentation enterprise and government buyers ask for alongside a statement.
- ServiceAccessibility Remediation
Code-level fixes for the limitations your statement lists — contrast, ARIA, keyboard, forms, and media.