Accessibility Statements
AllyProof generates public accessibility statements for your sites with one click. Each statement gets a permanent URL that you can link from your site's footer, demonstrating your commitment to accessibility.
What Is an Accessibility Statement?
An accessibility statement is a public page that describes a website's accessibility conformance status, known limitations, and contact information for reporting barriers. Accessibility statements are:
- Required by the EU European Accessibility Act (EAA) for public sector websites
- Required by EN 301 549 for EU public procurement
- Recommended by WCAG 2.2 as a best practice
- Strongly recommended for ADA compliance — demonstrates good faith effort
One-Click Publishing
To publish an accessibility statement for a site:
- Navigate to the site detail page
- Click Publish Statement
- Review the auto-generated content (pre-filled from scan results and org settings)
- Optionally edit the contact email or add custom notes
- Click Publish
The statement is immediately available at its public URL. You can update it at any time — the URL stays the same.
Public URL
Each published statement gets a permanent public URL:
https://app.allyproof.com/statement/{slug}
Example: https://app.allyproof.com/statement/acme-corpThe slug is derived from your organization name and can be customized. Link this URL from your site's footer or accessibility page.
Statement Content
The generated statement includes the following sections:
Header
- Organization name — Your organization's display name
- Site URL — The website the statement applies to
- Last updated date — When the statement was last generated or edited
Conformance Status
The statement declares the conformance level based on the most recent scan results:
| Score | Conformance status |
|---|---|
| 90-100 | "Partially conforms to WCAG 2.2 Level AA" |
| 70-89 | "Partially conforms to WCAG 2.2 Level AA with known exceptions" |
| Below 70 | "Does not yet conform to WCAG 2.2 Level AA — remediation in progress" |
Note that even a score of 100 uses "partially conforms" because automated testing covers only 57-70% of WCAG criteria. Full conformance requires manual testing.
Known Limitations
A summary of open violations grouped by category (images, forms, navigation, contrast, etc.), with a note that remediation is ongoing.
Feedback Contact
- Contact email — The email address for reporting accessibility barriers (from org settings)
- Response commitment — Statement that accessibility feedback will be addressed within a specified timeframe
Assessment Method
Describes that the site was evaluated using automated scanning tools (axe-core, HTML_CodeSniffer, APCA) and notes that manual testing is recommended for complete coverage.
Footer
The statement footer includes:
- Date of the most recent scan
- A "Powered by AllyProof" attribution with link (can be removed on Enterprise plan)
Updating Statements
Statements can be regenerated at any time from the site detail page. When you run a new scan, the statement does not auto-update — you choose when to republish with updated results. This prevents unexpected changes to a public document.
The statement editor also allows manual text overrides for any section, so you can add context that automated tools cannot provide (e.g. manual testing results, remediation timelines, alternative access methods).
Legal Considerations
- Accessibility statements demonstrate good faith effort in ADA litigation — courts have looked favorably on organizations that publish statements and demonstrate ongoing remediation
- The EU EAA requires a published accessibility statement — AllyProof generates content that follows the W3C model accessibility statement structure
- Statements should be honestabout limitations — overstating conformance can be worse than having no statement at all (see the FTC's action against accessiBe for misrepresenting compliance)