ADA Title II Website & PDF Accessibility Auditor
Under maintenancePricing
Pay per event + usage
ADA Title II Website & PDF Accessibility Auditor
Under maintenanceAudit a government, school or business website for accessibility: every linked PDF checked for PDF/UA basics (tagged, scanned, language, title, bookmarks) and every page for WCAG basics. Site-wide pass rates for ADA Title II planning.
Pricing
Pay per event + usage
Rating
0.0
(0)
Developer
Musedenny
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Security
Limited permissionsShare
Audit a government, school or business website for accessibility in one run. The Actor crawls the site, checks every linked PDF against the machine-checkable PDF/UA basics and every page against core WCAG checks, then gives you site-wide pass rates and the top issues.
Built for cities, counties, school districts, special districts and universities preparing for the ADA Title II web accessibility rule, and for the consultants and remediation vendors who serve them. Most of the backlog is PDFs: agendas, budgets, forms and notices.
What it checks
PDFs (downloaded and parsed, no browser):
- Untagged (no structure tree), critical
- Image-only / scanned (no selectable text), critical
- Fillable form in an untagged PDF, critical
- Password-protected or unreadable, critical
- No document language, serious
- No document title, serious; title not displayed, moderate
- Long document without bookmarks, moderate
Web pages:
- Images without alt text, critical
- Links with no accessible text, serious
- Form fields without labels, serious
- Missing page language or
<title>, serious - No
<h1>, moderate
Example result (real run, section508.gov, 41 pages)
51 PDFs found, 18 checked: 1 failing (pass rate 94%); 2 of 41 pages with at least one issue. Top issues: pages without an <h1>, missing page language, PDF titles not displayed, PDFs without bookmarks.
Input
{"startUrls": ["https://www.examplecounty.gov/"], "maxPages": 300, "maxPdfs": 500, "onlyFailingItems": false}
Output
One row per page and per PDF:
{"type": "pdf","url": "https://www.example.gov/media/…/notice.pdf","foundOn": "https://www.example.gov/notices","sizeKB": 212,"pages": 1,"tagged": false,"hasText": true,"language": null,"title": null,"displayDocTitle": false,"hasBookmarks": false,"hasFormFields": false,"issues": [{"code": "untagged", "severity": "critical", "message": "PDF is not tagged (no structure tree), so screen readers cannot follow headings, lists or tables."},{"code": "no-language", "severity": "serious", "message": "Document language is not set."},{"code": "no-title", "severity": "serious", "message": "Document has no title in its metadata."}],"criticalIssues": 1,"passesBasicChecks": false}
The run's OUTPUT record has the site summary: PDFs found, checked and failing, untagged and image-only counts, PDF and page pass rates, and the top issues.
Pricing (pay per event + usage)
| Event | Price | When |
|---|---|---|
apify-actor-start | $0.001 | Once per run |
pdf | $0.002 | One PDF checked |
page | $0.0005 | One web page checked |
Example: a county site with 300 pages and 500 PDFs ≈ $1.15. Plus Apify platform usage (PDF parsing; typically a few cents per large site).
Important
These are automated checks of machine-detectable failures. A PDF that passes can still have issues only a person can judge (reading order, alt-text quality, table structure, colour contrast). Use the results to size and prioritise the work; full conformance needs manual review. Some sites block automated visitors; the run then fails with a clear message.