Accessibility Statement Generator
Pricing
from $250.00 / 1,000 statement generateds
Accessibility Statement Generator
Writes a ready-to-publish accessibility statement for the European Accessibility Act, in English or Dutch, as HTML, Markdown and text. One statement per run, so agencies can call it from the API or a schedule for every site they manage. $0.25 per statement. Not legal advice.
Pricing
from $250.00 / 1,000 statement generateds
Rating
0.0
(0)
Developer
Vi Zellie
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Built for agencies and site owners with many websites. Each run writes one ready-to-publish statement, in English or Dutch, and the same job can be scheduled or called from the API across a whole portfolio.
General information only, not legal advice.
The statement follows the European Accessibility Act, which has applied since 28 June 2025. When the country is the Netherlands, the statement also names the Implementatiewet toegankelijkheidsvoorschriften producten en diensten. EN 301 549 v3.2.1 uses WCAG 2.1 level AA. WCAG 2.2 level AA also covers the WCAG 2.1 AA criteria used by EN 301 549.
What you get
The key-value store receives the same statement in three forms:
STATEMENT_HTMLSTATEMENT_MDSTATEMENT_TXT
When the HTML record is opened inline in the Apify console, the platform adds its own script to the page. Download it with the download link, which adds ?attachment=1, to get the clean file.
The dataset has one row with counts and the choices you made: language, conformance, standard, how many limitations you listed, how many were skipped, how many the optional page check suggested, and whether that check ran, succeeded, or failed. It does not contain the statement text, the organisation name, or the feedback contact.
How to use it
- Enter the organisation or brand name and the public website URL.
- Set the statement date as
YYYY-MM-DD. - Choose full, partial, or not for conformance, and choose WCAG 2.1 AA or WCAG 2.2 AA. EN 301 549 v3.2.1 uses WCAG 2.1 level AA. WCAG 2.2 level AA also covers those criteria.
- Add known limitations as short items: area, issue, workaround, and a planned fix date when you have one.
- Say whether the assessment was done by you or by an external party.
- Give a feedback contact. A contact page URL or a role mailbox such as
accessibility@example.comis recommended. - Choose the enforcement country. The list is Netherlands (ACM), Belgium (FPS Economy) and Ireland (CCPC). These bodies supervise e-commerce accessibility. Another service in the same country can fall under a different authority.
- Choose English or Dutch.
- Leave Check one page off unless you want a light look at that one URL. It can suggest limitations for a missing page language, a missing title, images without alt text, form fields without a label, and heading order. It does not judge colour contrast.
- Run the Actor and copy the statement into your site.
Pricing
You pay a small fee when the run starts, plus a fee when a statement is saved. A run that does not produce a statement is not charged the statement fee.
| Event | Price |
|---|---|
| Run start | $0.00005 |
| Statement generated | $0.25 |
What is not collected
The statement is stored only as this run's output. Logs contain the website domain and the language. They do not contain the organisation name, the limitations, or the feedback contact. The dataset row does not contain those fields either.
Limits
One statement per run. The optional check reads one public page, follows a limited number of redirects, and stops at a size cap. Only http and https on ports 80 and 443 are accepted. Private and internal addresses are refused.
