EU Accessibility Privacy Lead Scanner

Point this Actor at a list of submitted URLs and it returns a deterministic, robots-aware report of accessibility and privacy exposure signals that are visible in the page HTML. It is designed for repeatable lead research with bounded network work, strict output counters, and replay-safe result delivery for automation teams.

What it does

• Reads only the URLs you submit.
• Fetches robots.txt first, then the page itself.
• Checks a fixed signal set for image alt usage, control names, document language, keyboard semantics, privacy notice links, tracker-before-choice, consent choice, and personal-data form notices.
• Emits only useful Dataset rows with result-found billing.
• Stores the compact run envelope in the default Key-Value Store key OUTPUT.
• Never uses an LLM, browser, proxy, login, side effect, or legal verdict.

Features

Robots rules are checked before the submitted path and every same-host redirect target. Public-address SSRF protection, a real connection timeout, terminal request state, and a 16 KiB compact envelope keep the result deterministic and suitable for API clients.

Input

{
  "schemaVersion": "1.0",
  "requestId": "demo-ai-001",
  "urls": ["https://www.intercom.com", "https://www.w3.org"],
  "maxResults": 10,
  "freshnessMinutes": 60,
  "detailLevel": "compact"
}

How to run

Submit the JSON input in the Apify Console or call the API endpoint shown below. Start with one or two URLs, choose compact for normal use, and use evidence when excerpts are useful. Each requestId is idempotent: a completed request is replayed without another paid result.

Output

Useful Dataset rows contain the observed signals, accessibilityGapScore, privacyGapScore, combinedExposureScore, leadTier, isLead, needsReview, and source evidence hashes. The compact OUTPUT envelope in the default Key-Value Store keeps the summary, counts, warnings, and status.

Input and output examples

The input example above is accepted as-is. A useful output summary contains sourceUrl, canonicalUrl, the accessibility and privacy gap scores, combinedExposureScore, leadTier, isLead, needsReview, and evidence hashes. Errors use a fixed enum such as ROBOTS_DENIED, SOURCE_TIMEOUT, or DELIVERY_CHARGE_UNKNOWN.

Pricing

• apify-actor-start: $0.005 minimum platform start event
• result-found: $0.05

Only useful rows create result-found charges. Garbage, robots denial, SSRF blocks, source outages, and invalid input do not create result charges, although the platform may charge the automatic start event. Request replay and cached report reuse are handled through the persistent named actor cache.

Limits

• 1..100 URLs per run
• Same-host fetch only
• 3 redirects maximum
• 5 second connect timeout, 15 second attempt timeout, 25 second per-URL work unit
• 2 MiB decoded page body limit
• 50 MiB aggregate decoded response limit and 150 second hard stop
• 16 KiB maximum for the compact OUTPUT record

Source notes

This Actor does not infer WCAG, EN 301 549, GDPR, ePrivacy, compliance, sanctions, or liability. It only reports observed exposure indicators in the submitted page HTML.

Support and limitations

This is a BYOD scanner, so the submitted page must be publicly reachable over HTTP(S) and must allow the requested path in robots.txt. Report a reproducible bug with the input, request ID, and OUTPUT error code; do not include secrets or private page content.

API example

curl https://api.apify.com/v2/acts/zinin~eu-accessibility-privacy-lead-scanner/runs \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "schemaVersion": "1.0",
    "requestId": "demo-ai-001",
    "urls": ["https://www.intercom.com"],
    "maxResults": 10,
    "freshnessMinutes": 60,
    "detailLevel": "evidence"
  }'

Related tools

Related tools for adjacent workflows in operational gap-lead generation.

Actor	What it does
EU AI Act Transparency Lead Scanner	Pair it in the operational gap-lead generation workflow: BYOD compliance scanner for observed AI transparency signals on a submitted URL. Deterministic,...
Clinic Reception Gap Lead Finder	Pair it in the operational gap-lead generation workflow: Analyze submitted clinic websites for reception-channel gaps with exact BYOD crawling and no discovery
Restaurant Booking Gap Lead Finder	Pair it in the operational gap-lead generation workflow: Analyze submitted restaurant websites for booking-channel gaps with exact BYOD crawling and no discovery
New Opening Permit Lead Radar	Pair it in the operational gap-lead generation workflow: Detect commercial permit and license openings from five fixed Socrata datasets and return evidence-backed...