Website Accessibility (WCAG) Scanner avatar

Website Accessibility (WCAG) Scanner

Pricing

Pay per usage

Go to Apify Store
Website Accessibility (WCAG) Scanner

Website Accessibility (WCAG) Scanner

Scan websites for WCAG (Web Content Accessibility Guidelines) compliance issues. Checks images, forms, headings, links, iframes, tables, ARIA roles, and more for accessibility violations.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Richard P

Richard P

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Built by Apify

A serverless WCAG (Web Content Accessibility Guidelines) compliance scanner built as an Apify Actor. It analyzes web pages for common accessibility issues, helping you ensure your websites are usable by people with disabilities.

Features

  • 10+ WCAG compliance checks covering:
    • Images: Missing or non-descriptive alt text (WCAG 1.1.1)
    • Forms: Inputs without accessible labels (WCAG 1.3.1)
    • Page Language: Missing lang attribute on <html> (WCAG 3.1.1)
    • Heading Hierarchy: Skipped heading levels (WCAG 1.3.1)
    • Links: Empty or vague link text (WCAG 2.4.4)
    • iFrames: Missing or insufficient title attributes (WCAG 4.1.2)
    • Tables: Missing headers or captions (WCAG 1.3.1)
    • Media: Missing captions/transcripts (WCAG 1.2.2)
    • ARIA Roles: Invalid or misspelled ARIA roles (WCAG 4.1.2)
    • Color Contrast: Informational note (requires visual testing)
  • Severity classification: Each issue is tagged as critical, warning, or info
  • Accessibility scoring: Each page receives a percentage score (0–100)
  • Multi-page crawling: Automatically discovers and scans internal links
  • WCAG conformance levels: Target A, AA, or AAA
  • Structured JSON output: Each issue includes type, severity, WCAG criterion reference, element snippet, and remediation recommendation
  • Webhook notifications: Receive scan results via POST webhook

Input

FieldTypeRequiredDefaultDescription
urlsarray[string]One or more URLs to scan
levelstring"AA"WCAG conformance level ("A", "AA", "AAA")
maxPagesint10Max pages to scan per seed URL (crawls internal links)
webhookUrlstringURL for POST notification on scan completion

Output

Each page scan produces a dataset record with:

FieldTypeDescription
timestampstringISO 8601 scan timestamp
urlstringScanned URL
totalIssuesintTotal issues found (all severities)
criticalIssuesintCount of critical-severity issues
scorenumberAccessibility score (0–100)
issuesarrayArray of individual issue objects

Each issue object contains:

FieldDescription
typeMachine-readable issue identifier
severitycritical, warning, or info
elementHTML snippet of the affected element
wcagCriterionWCAG criterion reference (e.g., "1.1.1")
recommendationHuman-readable remediation advice

A final summary record is appended with aggregate statistics across all scanned pages.

Quick Start (Local)

# Install dependencies
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
# Run locally (requires Apify API token)
apify run --purge
# Or set explicit input
echo '{"urls":["https://example.com"],"level":"AA","maxPages":5}' > INPUT.json
apify run --purge

Deploy to Apify

apify login
apify push

Example Output

{
"timestamp": "2026-07-04T12:00:00.000000+00:00",
"url": "https://example.com",
"totalIssues": 3,
"criticalIssues": 2,
"score": 57.1,
"issues": [
{
"type": "missing_alt",
"severity": "critical",
"element": "<img src=\"logo.png\"/>",
"wcagCriterion": "1.1.1",
"recommendation": "Add an alt attribute..."
},
{
"type": "missing_lang",
"severity": "warning",
"element": "<html>",
"wcagCriterion": "3.1.1",
"recommendation": "Add a lang attribute..."
}
]
}

WCAG Criteria Checked

CriterionDescriptionSeverity if Violated
1.1.1Non-text ContentCritical
1.2.2Captions (Prerecorded)Info
1.3.1Info and RelationshipsCritical/Warning
1.4.3Contrast (Minimum)Info (not checkable server-side)
2.4.4Link Purpose (In Context)Critical/Warning
3.1.1Language of PageWarning
4.1.2Name, Role, ValueWarning

Limitations

  • Color contrast cannot be checked server-side — use browser-based tools (axe DevTools, Lighthouse, Wave) for visual contrast analysis
  • Dynamic content rendered by JavaScript may not be fully captured — consider a headless browser for Single Page Applications
  • Server-side checks are a first pass — they catch common issues but don't replace manual accessibility auditing

Resources