Accessibility Statement Generator
Generate an accessibility statement that carries every element the EU Web Accessibility Directive and Section 508 expect, including the honest disclosure of known non-conformances.
Last reviewed by the Radiatus Cloud team
Going for ISO 27001, SOC 2, HIPAA or GDPR?
Radiatus runs end-to-end compliance & GRC programs.
A statement that claims full conformance is usually wrong
Very few sites of any size fully conform to WCAG 2.2 at level AA, and a statement asserting that they do is the fastest way to turn an accessibility complaint into a misrepresentation complaint. The model statements published under the EU Web Accessibility Directive expect a conformance status of fully, partially or non-conformant, and partially is the honest answer for most organisations. Naming the specific failures is not an admission of weakness; it is the required content.
The feedback mechanism is the part that gets used
Most of a statement is read by nobody. The contact route for reporting an inaccessible page is read by exactly the people who need it, and it is the element most often missing or broken. The Directive requires a feedback mechanism and an enforcement procedure to escalate to when the response is inadequate, and a statement offering a general contact form without either does not meet the requirement.
Disproportionate burden must be argued, not asserted
Where a component cannot reasonably be made accessible, the Directive permits a disproportionate burden claim, but it must set out the assessment behind it and it does not extend to the whole site. Claiming disproportionate burden for a core function is not credible and invites the scrutiny it was meant to avoid. A dated commitment to fix, with a specific date, is almost always the better statement.
Related tools
- SOC 2 Evidence Readiness — Interactive checklist to gauge your SOC 2 evidence readiness.
- Privacy Policy Checker — Check if your policy covers standard requirements (GDPR/CCPA basics).
- Compliance Req Finder — Find which standards (ISO, SOC2, HIPAA) apply to your industry/region.
- Audit Readiness Planner — Plan your compliance audit timeline (SOC2, ISO) backwards from deadline.
Frequently Asked Questions
Should I claim full conformance?
Only if you have tested and it is true, which is rare for a site of any size. Claiming it wrongly converts an accessibility complaint into a misrepresentation complaint, and partially conformant is the expected honest answer.
What must the statement contain?
The conformance status against a named standard, the specific known non-conformances and why, a feedback mechanism, an enforcement procedure to escalate to, and the dates of preparation and last review.
What is a disproportionate burden claim?
A documented argument that a specific component cannot reasonably be made accessible. It must set out the assessment behind it and cannot cover the whole site, and claiming it for a core function invites scrutiny rather than avoiding it.
Does Section 508 need the same statement?
Section 508 does not mandate a published statement in the same way, but it applies the same WCAG success criteria, so one statement can cover both if it names the standard and version precisely.
How often should it be reviewed?
Annually at minimum, and after any significant change to the site. A statement whose review date is years old undermines the rest of its content.
Privacy & Security
Everything runs in your browser; nothing is uploaded.
How to Use
Enter your site details and known issues to generate a statement.
Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.
Related Tools
SOC 2 Evidence Readiness
ComplianceInteractive checklist to gauge your SOC 2 evidence readiness.
Privacy Policy Checker
ComplianceCheck if your policy covers standard requirements (GDPR/CCPA basics).
Compliance Req Finder
ComplianceFind which standards (ISO, SOC2, HIPAA) apply to your industry/region.