# EAA Spain: Accessibility Statement & AI Notice Bulk Checker (`bigochelo/eaa-spain-compliance-checker`) Actor

Checks Spanish websites in bulk for an accessibility statement (Ley 11/2023, RD 193/2023) and an AI notice on chatbots (AI Act art. 50). Traffic light and a forwardable explanation in Spanish per site. Not an accessibility audit or legal advice.

- **URL**: https://apify.com/bigochelo/eaa-spain-compliance-checker.md
- **Developed by:** [Marcelo Palacios](https://apify.com/bigochelo) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 website checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EAA Spain: Accessibility Statement & AI Notice Bulk Checker

*Versión en español más abajo.*

Check **dozens of Spanish online shops at once** for two public documents: the **accessibility statement** (Ley 11/2023 and Real Decreto 193/2023, the Spanish rules under the European Accessibility Act) and the **AI notice on chatbots** (art. 50 of the EU AI Act). Each website gets a **traffic light** and a short **explanation in Spanish** that an agency can forward to its client as it is.

This is a check of public documents, **not an accessibility audit** (it does not test WCAG) and not legal advice.

**Why it matters:** in our own test with 23 Spanish online shops, checked by hand, **16 had no accessibility information at all** and **only 1** had a complete statement that cited Ley 11/2023.

### Quick reference for AI agents and developers

- **Minimal input:** `{"urls": ["https://www.example-shop.es"]}` (1 to 200 websites; `https://` is optional).
- **Output:** one dataset item per website. Read `trafficLight` first (`green` / `yellow` / `red` / `not_applicable`), then `explanation` (Spanish, ready to forward).
- **Statement details:** `statement.found`, `statement.location` (footer, menu, terms and conditions, legal notice...), `statement.missingElements`, `statement.citesLey11_2023`, `statement.reviewOutdated`, and `statement.pagesChecked` with every address looked at.
- **Chatbot:** `chatbot.detected`, `chatbot.providers` and `chatbot.aiNotice` (`visible` / `not_visible` / `not_verifiable`).
- **Draft statement:** with `"generateDraft": true`, red and yellow websites also get a Spanish draft in Markdown and HTML, marked **BORRADOR PARA REVISAR**.
- **Errors:** a website that cannot be read (blocked, down, timeout) is saved with `trafficLight: null` and the reason in `error`, and it is **not charged**.

### What it checks

**1. Accessibility statement.** It looks for it in the footer, the menu, links on the home page, the terms and conditions, the legal notice and usual addresses such as `/accesibilidad`. In the statement it looks for the 6 elements of the usual model:

| Element (field) | In Spanish |
|---|---|
| `complianceStatus` | situación de cumplimiento |
| `nonAccessibleContent` | contenido no accesible |
| `preparationDate` | fecha de preparación |
| `lastReviewDate` | fecha de última revisión |
| `contactChannel` | canal de contacto |
| `complaintProcedure` | procedimiento de reclamación |

It also checks whether it cites Ley 11/2023 or RD 193/2023, and whether the last review is older than 12 months. Generic uses of "accesible" (for example "documento accesible" in the terms) do not count. A generic statement written by an overlay widget vendor (EqualWeb, accessiBe, UserWay, AccessiWay and similar) is reported in `statement.widgetOnly` and does not count as the company's own statement.

**2. Online sales.** Cart, checkout, bookings or payments mean the website likely falls under the law (`onlineSales.status: likely_obligated`). Whether a company is a microenterprise cannot be seen from outside, so every explanation says the law does not apply to microenterprises.

**3. Chatbot AI notice.** It loads the home page like a visitor, detects chat widgets (Intercom, Tidio, Zendesk, HubSpot, Crisp, LiveChat, Tawk.to, Gorgias, Freshchat, Oct8ne, Chatbase, Botpress, Voiceflow, Landbot and more) and checks whether the chat says it is an AI. Many chats show that only once opened, so it **opens the chat with one click** and reads its first screen. It never types or sends anything, and if a cookie banner covers the chat it presses **Reject**, never Accept. Screenshots are kept as evidence.

### Traffic light

| Color | Meaning |
|---|---|
| `red` | Sells online and no accessibility information was found, or only the generic statement of an overlay widget. |
| `yellow` | Information found, but it misses elements of the usual model, does not cite Ley 11/2023 or RD 193/2023, its last review is older than 12 months, it is only reachable at a usual address without a visible link, or the chat does not say it is an AI once opened. |
| `green` | None of the above. |
| `not_applicable` | No online sales signals and no accessibility information. |

`aiNotice: not_verifiable` (the chat could not be checked) is reported but does not change the color.

### Example output

```json
{
  "url": "https://www.example-shop.es/",
  "trafficLight": "yellow",
  "explanation": "Se encontró información de accesibilidad en el pie de página. Le faltan elementos del modelo habitual: procedimiento de reclamación. No menciona la Ley 11/2023 ni el Real Decreto 193/2023. La Ley 11/2023 pide publicar esa información, salvo que la empresa sea una microempresa (menos de 10 empleados y un volumen de negocio o balance anual de hasta 2 millones de euros). Al abrir el chat (Oct8ne) no se ve un aviso de que responde una IA; si la usa, conviene decirlo explícitamente desde el primer mensaje.",
  "onlineSales": {"status": "likely_obligated"},
  "statement": {
    "found": true,
    "location": "footer",
    "missingElements": ["complaintProcedure"],
    "citesLey11_2023": false,
    "citesRD193_2023": false,
    "reviewOutdated": false,
    "widgetOnly": null
  },
  "chatbot": {"detected": true, "providers": ["Oct8ne"], "aiNotice": "not_visible", "openedByClick": true},
  "draft": null,
  "proxyUsed": "none",
  "error": null
}
```

### Input

| Field | Description |
|---|---|
| `urls` | Home pages to check, 1 to 200 (required). |
| `useResidentialProxy` | Default on. A website that blocks the first visit is retried once through a Spanish residential IP. |
| `generateDraft` | Default off. Adds a draft statement in Spanish to red and yellow websites. |
| `companyName` | Optional. Legal name for the draft. |
| `contactEmail` | Optional. Contact address for the draft. |

### The draft statement

The draft follows the structure of the usual Spanish model (situación de cumplimiento, contenido no accesible, preparación, contacto y reclamación). It is always marked **BORRADOR PARA REVISAR**, its compliance status is always **"sin evaluar"**, and everything the tool cannot know is left as `[COMPLETAR]`. Paid tools such as Eye-Able already write full statements; this Actor's strength is **checking many websites in one run**, with the draft as a starting point.

### Pricing

- **$0.02** per run
- **$0.05** per website checked
- **$0.05** per website that needed the Spanish residential IP retry and was read, on top
- **$0.50** per draft statement (only with `generateDraft` and a red or yellow result)

Websites that cannot be read cost nothing.

### Limitations

- It checks **public documents**, not whether the website is accessible. A green light does not mean the website meets WCAG or the law.
- Some websites block automated visits even from a Spanish residential IP. They come back with an `error` and are not charged.
- Whether a company is a microenterprise (fewer than 10 employees and up to 2 M€ turnover or balance sheet) cannot be seen from outside.
- A chat can change its first message at any time; the result describes what was seen during the run.

### More tools from this line

- **[Safe Web Reader for AI](https://apify.com/bigochelo/safe-web-reader)**: web pages and PDFs to clean Markdown, with hidden text and prompt-injection attempts removed and reported.
- **[MCP Tool Poisoning Scanner](https://apify.com/bigochelo/mcp-poisoning-scanner)**: audits MCP servers for tool poisoning, hidden instructions and silent tool changes.
- **[PDF to Markdown & Text for AI/RAG](https://apify.com/bigochelo/pdf-to-markdown-text-for-ai-rag)**: digital PDFs to Markdown for RAG, with tables and chunks.

***

## En español

Revisa **decenas de tiendas online españolas de una vez** y dice si tienen en regla dos documentos públicos: la **declaración de accesibilidad** (Ley 11/2023 y Real Decreto 193/2023, la transposición española de la Ley Europea de Accesibilidad) y el **aviso de IA del chatbot** (art. 50 del Reglamento europeo de IA). Cada web recibe un **semáforo** y una **explicación breve en español** que una agencia puede reenviar a su cliente tal cual.

Es una revisión de documentos públicos, **no una auditoría de accesibilidad** (no evalúa WCAG) ni asesoramiento legal.

**Por qué importa:** en nuestra prueba con 23 tiendas online españolas, confirmadas a mano, **16 no tenían ninguna información de accesibilidad** y **solo 1** tenía una declaración completa que citara la Ley 11/2023.

### Qué revisa

1. **Declaración de accesibilidad.** La busca en el pie de página, el menú, la página de inicio, las condiciones generales, el aviso legal y direcciones habituales como `/accesibilidad`. Comprueba los 6 elementos del modelo habitual (situación de cumplimiento, contenido no accesible, fecha de preparación, fecha de última revisión, canal de contacto y procedimiento de reclamación), si cita la Ley 11/2023 o el RD 193/2023 y si la última revisión tiene más de 12 meses. Los usos genéricos de "accesible" no cuentan. La declaración genérica de un widget (EqualWeb, accessiBe, UserWay, AccessiWay y similares) no reemplaza una declaración propia de la empresa.
2. **Venta online.** Carrito, pago, reservas o pasarela de pago indican que la web probablemente está obligada. Si la empresa es una microempresa no se puede saber desde fuera, así que todas las explicaciones aclaran esa excepción.
3. **Aviso de IA del chatbot.** Detecta el chat y comprueba si dice que responde una IA. Muchos chats lo muestran solo al abrirse, así que **lo abre con un clic** y lee la primera pantalla. Nunca escribe ni envía nada, y si un aviso de cookies tapa el chat pulsa **Rechazar**, nunca Aceptar.

### Semáforo

- **Rojo:** vende online y no se encontró información de accesibilidad, o solo la declaración genérica de un widget.
- **Amarillo:** hay información, pero le faltan elementos del modelo habitual, no cita la Ley 11/2023 ni el RD 193/2023, la revisión tiene más de 12 meses, solo está en una dirección habitual sin enlace visible, o el chat no avisa que es una IA al abrirlo.
- **Verde:** nada de lo anterior.
- **No aplica:** no hay señales de venta online ni información de accesibilidad.

### Borrador de declaración

Con `generateDraft`, las webs en rojo o amarillo reciben un borrador en español (Markdown y HTML) con la estructura del modelo habitual. Siempre va marcado **BORRADOR PARA REVISAR**, con la situación de cumplimiento **"sin evaluar"** y los huecos marcados `[COMPLETAR]`. Hay herramientas de pago, como Eye-Able, que ya redactan declaraciones completas. Lo nuestro es la **revisión en lote**, y el borrador sirve como punto de partida.

### Precio

- **US$ 0,02** por ejecución
- **US$ 0,05** por web revisada
- **US$ 0,05** adicional por web que necesitó el reintento con IP residencial española y se pudo leer
- **US$ 0,50** por borrador de declaración (solo con `generateDraft` y resultado rojo o amarillo)

Las webs que no se pueden leer no se cobran.

### Límites

- Revisa **documentos públicos**, no si la web es accesible. Un verde no significa que la web cumpla WCAG ni la ley.
- Algunas webs bloquean las visitas automáticas incluso con IP residencial española. Salen con `error` y no se cobran.
- Si la empresa es una microempresa (menos de 10 empleados y un volumen de negocio o balance anual de hasta 2 millones de euros) no se puede saber desde fuera.
- El primer mensaje de un chat puede cambiar en cualquier momento. El resultado describe lo que se vio durante la revisión.

# Actor input Schema

## `urls` (type: `array`):

Home pages of the websites to check, 1 to 200. One row per website in the results. Example: \["https://www.example-shop.es", "https://www.example-store.com/es/"]. URLs without https:// are accepted.

## `useResidentialProxy` (type: `boolean`):

If true (default), a website that blocks the first visit (HTTP 401/403/429/503 or an anti-bot check) is retried once through a Spanish residential IP. When that retry reads the website, it is charged as one extra 'residential-retry' event. If the retry is also blocked, the row is saved with the reason and nothing is charged for it. If false, blocked websites are not retried and are not charged.

## `generateDraft` (type: `boolean`):

If true, websites with a red or yellow result also get a draft accessibility statement in Spanish (Markdown and HTML), marked BORRADOR PARA REVISAR, with the compliance status 'sin evaluar' and gaps marked \[COMPLETAR]. Charged as one 'statement-draft' event per draft. Green and not_applicable websites get no draft.

## `companyName` (type: `string`):

Optional. Legal name used in the draft, e.g. "Tienda Ejemplo S.L.". Best used when checking one website; with several, the same name goes in every draft. Left as \[COMPLETAR] when empty.

## `contactEmail` (type: `string`):

Optional. Address for accessibility feedback shown in the draft, e.g. "accesibilidad@example-shop.es". Left as \[COMPLETAR] when empty or not a valid email.

## Actor input object example

```json
{
  "urls": [
    "https://www.juguettos.com/",
    "https://www.mascotaplanet.com/"
  ],
  "useResidentialProxy": true,
  "generateDraft": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://www.juguettos.com/",
        "https://www.mascotaplanet.com/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("bigochelo/eaa-spain-compliance-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        "https://www.juguettos.com/",
        "https://www.mascotaplanet.com/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("bigochelo/eaa-spain-compliance-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://www.juguettos.com/",
    "https://www.mascotaplanet.com/"
  ]
}' |
apify call bigochelo/eaa-spain-compliance-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bigochelo/eaa-spain-compliance-checker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ZF8uStyxiA8u1yHHq/builds/CuzC4rohVOFUeOd09/openapi.json
