HTML Accessibility Essentials Auditor

Accessibility Regression Gate preserving the original essentials audit while adding issue fingerprints, severity, baseline drift and release decisions. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API workflows, and AI.

Quick start

Start with this working example and replace the target values with your own:

{
  "urls": [
    "https://www.python.org",
    "https://example.com"
  ]
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• urls — URLs: Public HTTP(S) URLs to inspect
• previous_results — Previous accessibility snapshots: Optional map keyed by URL. Enables issue fingerprints, resolved/new issue detection, score drift and release gating.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include results.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.001300 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Lightweight accessibility hygiene checks for public web pages, designed for release QA, agency audits, and recurring monitoring.

Key features

• Checks document language and page title.
• Counts H1 elements and flags pages without a primary heading.
• Counts images and images missing meaningful alt attributes.
• Checks common form controls for associated labels or accessible names.
• Detects common semantic landmarks such as main, nav, and header.
• Reports viewport metadata and one structured score per URL.

Input

{"urls":["https://www.python.org","https://example.com"]}

Output

Each dataset item contains the requested and final URL, HTTP status, score, issues, heading counts, image accessibility counts, form-label counts, and landmark signals.

Example

A page with 20 images and 2 missing alt attributes returns images: 20, imagesMissingAlt: 2, an issue explaining the ratio, plus the other document-level checks in the same record.

Why use this Actor

1. Concrete counts reveal what needs fixing instead of hiding everything behind one score.
2. Fast HTTP-only checks are suitable for recurring release gates and portfolio monitoring.
3. Accessible-name checks cover labels, aria-label, and aria-labelledby for common form controls.
4. No paid accessibility API or AI dependency, keeping recurring costs predictable.

Pricing

Pay per dataset result. One URL audit produces one primary chargeable result. Pricing is optimized for repeated QA rather than a large one-off audit fee.

Good use cases

• Pre-release accessibility hygiene
• Agency website inventories
• CI regression checks
• Prioritizing pages for deeper manual or browser-based accessibility testing

Limitations

• This is not a WCAG certification or legal compliance determination.
• JavaScript-only DOM changes are outside an HTTP-only run.
• Manual keyboard, screen-reader, color contrast, focus, and usability testing remain necessary.

Privacy and safety

Only public HTTP(S) targets are accepted. Private and unsafe redirect destinations are rejected. No credentials or external AI service are required.