Accessibility Evidence EU - Static WCAG Signals

Turn static accessibility issues into reviewable QA tickets

Accessibility Evidence EU checks public HTML pages for common static accessibility signals and returns structured evidence for QA, release checks, agency reporting, and recurring monitoring. Every issue includes a rule, severity, selector, WCAG reference, and practical remediation so teams can move from a score to an actionable backlog.

This Actor is designed as a fast first-line audit. It is not a legal WCAG or European Accessibility Act compliance certificate and it does not replace testing with people with disabilities, assistive technologies, or qualified accessibility specialists.

Try it in 30 seconds

1. Click Try for free and keep the prepared W3C “Before” demonstration page.
2. Start the Actor. It needs no browser, proxy, AI model, or third-party API key.
3. Open the dataset. The table shows the score, grade, errors, warnings, and total issue count.
4. Open issues to copy a selector, WCAG reference, and remediation into a QA ticket.

You can also start from the public Audit website accessibility signals task. One successful page emits one page-audited event at the price shown above; failed pages do not emit that event.

In a verified W3C demonstration run, the Actor returned 43 static errors, including missing alternative text, unnamed controls, an unlabeled form control, and a missing document language. The target can change, and the result is QA evidence rather than a compliance verdict.

Importable n8n workflow

The public OmniAPI Apify examples repository includes a ready-to-import Accessibility Evidence n8n workflow, a monitoring tutorial, and a verified W3C demonstration summary. The workflow applies a configurable QA threshold and prepares findings for alerts, tickets, and human review.

What it checks

The current deterministic rules cover frequently missed static signals such as:

• Missing or empty document language.
• Missing or unclear page title.
• Images without alternative text.
• Links and buttons without accessible names.
• Form controls without associated labels.
• Invalid or skipped heading structure.
• Iframes without descriptive titles.

Each successful page produces a dataset item containing score, summary, structured issues, the audited url, and processedAt for traceability.

Typical use cases

Website accessibility monitoring

Schedule daily or weekly audits for important pages and compare the score or issue count over time. Trigger an alert when a release introduces a new high-severity signal.

Agency and client QA evidence

Audit landing pages before delivery, export the dataset as JSON, CSV, or Excel, and attach the findings to a human review. The structured output makes it easier to assign each issue to a developer or content editor.

Pre-release accessibility checks

Run the Actor from n8n, Make, Zapier, GitHub Actions, or another automation tool. Use a minimum score or maximum issue count as a review gate while keeping final compliance decisions with your accessibility team.

European Accessibility Act preparation

Use repeatable static checks to identify obvious issues and build an evidence trail during remediation. Regulatory scope and legal obligations vary by organization and service, so obtain professional advice for compliance decisions.

Input example

{
  "urls": [
    { "url": "https://www.w3.org/WAI/demos/bad/before/home.html" }
  ],
  "maxIssues": 100
}

Start with representative public pages such as the home page, navigation, contact form, checkout, account entry point, and key conversion pages.

Output example

{
  "success": true,
  "url": "https://www.w3.org/WAI/demos/bad/before/home.html",
  "scoreValue": 0,
  "scoreGrade": "F",
  "errorCount": 43,
  "warningCount": 0,
  "issueCount": 43,
  "score": { "value": 0, "grade": "F", "errors": 43, "warnings": 0, "infos": 0 },
  "summary": { "images": 42, "imagesWithoutAlt": 33, "controls": 56, "unnamedControls": 8, "formControls": 1, "unlabeledControls": 1, "headings": 1, "totalIssues": 43, "returnedIssues": 43, "issuesTruncated": false },
  "issues": [
    {
      "id": "html-lang-missing",
      "severity": "error",
      "selector": "html",
      "wcag": "3.1.1",
      "message": "The document does not declare its primary language.",
      "remediation": "Add a valid lang attribute to html."
    }
  ],
  "processedAt": "2026-09-08T20:17:08.859Z"
}

The example is shortened to one issue. summary.totalIssues counts every detected issue even when maxIssues limits the returned list. Use the published dataset schema when building a typed integration.

Use with n8n, Make, Zapier, or the API

A practical monitoring workflow is:

1. Schedule Trigger.
2. HTTP Request to the Apify synchronous dataset endpoint.
3. Calculate whether score.value is below your threshold.
4. Send the structured issues to email, Slack, Teams, a ticketing system, or a database.
5. Route the result to a human reviewer before making compliance claims.

Store the Apify token in a credential or secret environment variable. Do not include it directly in a workflow exported for customers.

Pricing and cost control

The launch price is $0.02 per successfully audited page. Failed URL items are returned for diagnosis without charging the page-audited event. Your own Apify platform usage follows the plan and estimated cost shown in the Console.

Test a small set first, confirm that the evidence matches your workflow, and use a maximum run charge before scheduling large recurring audits.

Important limitations

• Static HTML checks cannot prove conformance with WCAG, EN 301 549, or the European Accessibility Act.
• The Actor does not test keyboard navigation, focus order, screen-reader announcements, color contrast, captions, cognitive accessibility, authenticated flows, or every WCAG success criterion.
• Client-rendered interfaces may require additional browser-based testing.
• Automated tools produce false positives and false negatives; findings require human review.
• Website layouts change, so recurring jobs should be monitored.

Only audit pages you are authorized to access. You remain responsible for source-site terms, privacy, retention, regulatory interpretation, and remediation decisions.

FAQ

Is the score a compliance percentage?

No. It is a deterministic QA indicator for comparing runs and prioritizing review. It is not a legal compliance score.

Can this replace an accessibility audit?

No. Use it to find obvious static issues faster and to monitor regressions. Complete audits require manual and assistive-technology testing.

Can I export the results?

Yes. Apify datasets can be consumed by API or exported to common formats such as JSON and CSV for reporting and automation.

Will failed pages be charged?

No paid event is emitted for a failed page. The diagnostic item remains in the dataset so you can investigate the URL or network error.