Accessibility Statement Checker (EAA / WCAG)

What does Accessibility Statement Checker do?

Accessibility Statement Checker finds the accessibility statement on any list of websites and checks whether it covers what the EU model accessibility statement asks for. It's an API-friendly way to audit accessibility statements for the European Accessibility Act (EAA) and the Web Accessibility Directive in bulk.

For each website it:

1. 🔎 Finds the statement. It looks for footer and menu links in 10 languages ("Accessibility statement", "Toegankelijkheidsverklaring", "Erklärung zur Barrierefreiheit", "Déclaration d'accessibilité", …), follows one level of "Accessibility" hub pages, and tries common URL paths.
2. ✅ Checks the content. It looks for:
   • compliance status (fully / partially / not compliant)
   • the standard used (WCAG 2.1/2.2, EN 301 549)
   • a description of non-accessible content
   • the preparation or review date
   • a feedback contact (email or form)
   • a complaints or enforcement procedure
   • a reference to the EAA or national law
   • for Dutch sites, a link to the toegankelijkheidsverklaring.nl register
3. 📊 Scores it. You get a 0–100 score, a prioritised fix list and an optional HTML report.

Who is it for?

• 🏢 Web agencies: check every client site for an EAA-ready statement before or after a redesign.
• 🛒 E-commerce and service companies in scope of the EAA (applies since 28 June 2025): verify that the accessibility information is published and complete.
• 🏛️ Public sector auditors: check large lists of government sites against the model statement.
• 🤖 AI agents and automations: one URL in, structured JSON out. Works with Claude, ChatGPT and other agents through the Apify MCP server, and with Make, Zapier and n8n.

It complements the EU Accessibility Scanner, which tests the pages themselves for WCAG issues. This Actor checks the statement; the scanner checks the website.

What does it return?

Field	Description
statementFound, statementUrl, foundVia	Whether a statement was found, where, and how
score	0–100 completeness score
complianceStatus	full, partial, non or unknown
standardsMentioned	e.g. ["WCAG 2.1", "EN 301 549"]
hasNonAccessibleSection	Describes known non-accessible content
latestDateInStatement, monthsSinceLatestDate	Most recent date found in the statement
hasFeedbackMechanism, hasEnforcementInfo	Contact option and complaints procedure present
mentionsEaa, linksToNlRegister	Legal framework named; Dutch register link
topFixes	Plain-language list of what to add or fix
checks	Every check with status, finding, fix and legal reference

How to check accessibility statements in bulk

1. Click Try for free.
2. Paste the websites, one per line.
3. Click Start. Each site usually takes 2–10 seconds.
4. Open the Overview table, or download report.html from the key-value store.

How much does it cost?

Pay per event: you pay per website checked (see the Pricing tab), and platform usage is included. Websites whose homepage can't be loaded are free. It uses plain HTTP requests (no browser), so runs are fast and cheap.

Output example

{
  "domain": "www.example.nl",
  "statementFound": true,
  "statementUrl": "https://www.example.nl/toegankelijkheid",
  "score": 81,
  "complianceStatus": "partial",
  "standardsMentioned": ["WCAG 2.1"],
  "latestDateInStatement": "2026-03-12",
  "hasFeedbackMechanism": true,
  "hasEnforcementInfo": false,
  "topFixes": ["Explain what users can do if they are not satisfied with your response (e.g. the national enforcement body or ombudsman)."]
}

FAQ

Does a high score mean my website is accessible? No. This Actor checks the statement, not the site. Use the EU Accessibility Scanner for page-level WCAG testing.

Which elements are checked? The elements of the EU model accessibility statement in Commission Implementing Decision (EU) 2018/1523: compliance status, non-accessible content, preparation date, feedback mechanism and enforcement procedure. Under the EAA (Directive (EU) 2019/882, Annex V), businesses have to publish information on how their service meets the accessibility requirements, and many do this with a statement modelled on the same template.

My site uses JavaScript to render the footer. The Actor reads server-rendered HTML. If your links only appear after JavaScript runs, it falls back to common URL paths. You can also enter the statement URL directly.

Is it legal advice? No. The checks are automated text analysis and are indicative only.

Questions or a false result? Open an issue on the Issues tab.