EAA Accessibility Statement Detector

Since 28 June 2025 the European Accessibility Act (EAA) expects in-scope online services to publish accessibility information. This actor checks, for each site, whether an accessibility statement exists and whether it contains the elements auditors look for. Useful for agencies prospecting EAA work, compliance teams monitoring suppliers and e-commerce portfolios. Plain HTTP, no browser, no personal data stored (contact details are reported only as yes/no).

What it does

1. Fetches the page you give (home page) and finds statement links in any language (EN, DE, FR, ES, IT, NL, SV, PL, PT and more), ranking footer links first; ignores overlay-widget vendors.
2. If no link is found, probes ~15 common paths (/accessibility, /barrierefreiheit, /accessibilite, /accesibilidad, ...).
3. Reads the statement and checks: WCAG / EN 301 549 reference, WCAG version and level, declared status (fully / partially / not compliant), feedback contact present, complaint/enforcement procedure mentioned, list of inaccessible content, preparation/review date (flags over 12 months).
4. Returns status (complete, partial, incomplete, no-statement-found, error), a 0-100 score and issues[].

Respects robots.txt for the pages it fetches, 1 request at a time per host with a delay (default 400 ms), private addresses blocked (SSRF guard on every redirect hop).

Limits: keyword heuristics, not legal advice or a WCAG audit; JavaScript-only sites may show no links; a statement on a different domain is found only if linked.

Input

Field	Default	Description
urls	required	Up to 2000 sites. Use a localized home URL (e.g. /nl/nl/) for locale-specific statements.
delayMs / concurrency	400 / 4	Politeness.

Output

{ "siteOrigin": "https://www.gov.uk", "status": "complete", "score": 100, "statementUrl": "https://www.gov.uk/help/accessibility-statement",
  "complianceStatus": "partially", "conformanceLevel": "AA", "wcagVersion": "2.2", "hasFeedbackContact": true, "hasEnforcementProcedure": true, "statementDate": "2026-01-29", "issues": [] }

Pricing (pay per event)

apify-actor-start $0.005 per run (per GB), site-checked $0.005 per site (invalid URLs are not charged).

Develop

npm install && npm test; local run via storage/key_value_stores/default/INPUT.json + npm start; deploy apify push (private by default).