ScanplyanceKnow what needs fixing before the DOJ deadline.
Scanplyance gives public agencies a WCAG 2.1 AA website snapshot, vendor-ready fix list, and recurring monitoring record — without hiring a full accessibility team.
- WCAG 2.1 AA checks
- Vendor-ready remediation list
- Weekly monitoring
- Private reports by default
- PO / invoice friendly
Built for U.S. cities, counties, school districts, courts, libraries, transit agencies, and special districts.
Built for the people who actually get the call.
City managers & administrators
See risk areas, progress, and open issues without digging through technical WCAG language.
Clerks & ADA coordinators
Maintain a documented monitoring record and export reports for internal files.
IT teams & web vendors
Get page-level issues, WCAG references, severity, and plain-English remediation guidance.
Attorneys & procurement
Document good-faith monitoring efforts and track vendor follow-through.
The DOJ standard is now concrete.
The DOJ Title II web and mobile app rule requires state and local government web content and mobile apps to meet WCAG 2.1 Level AA. Large public entities have until April 26, 2027. Smaller public entities and special district governments have until April 26, 2028.
50,000+ population
Compliance date
Under 50,000 population
Compliance date
Special district governments
Compliance date
Why agencies need more than a one-time scan
Websites change. Vendors update templates. PDFs get posted. Forms break. Staff publish new content. Scanplyance helps agencies keep watch after the first audit.
- Identify affected pages and issue types
- Prioritize resident-impacting barriers
- Send fixes to vendors or staff
- Track recurring issues and regressions
- Keep dated reports for internal records
Prior enforcement shows what public agencies are expected to document.
DOJ actions and settlement agreements have repeatedly focused on more than a one-time scan: identify barriers, fix high-impact issues, train staff, manage vendor content, provide feedback channels, and monitor over time.
Service Oklahoma
DOJ required mobile applications to conform to WCAG 2.1 Level AA, plus accessibility feedback channels, ADA coordination, staff training, and reporting.
City and County of Denver
DOJ required assessment of existing and proposed online services using automated testing and testing by people with disabilities.
County and city agreements
Project Civic Access agreements have required web accessibility policies, staff training, and processes for maintaining accessible web content.
Private by default. Public only if you choose.
Scan results are private to your team. If you subscribe to monitoring, you may optionally publish a monitoring badge or status page — but Scanplyance never exposes detailed issue data publicly without agency approval.
Automated scanning is not the whole job.
Automated scans are useful, but they cannot test every aspect of accessibility. Scanplyance supports a broader process: automated monitoring, manual review, vendor remediation, accessibility policies, and user feedback. It is a monitoring and documentation tool — not a law firm, and not a guarantee of compliance.
How it works
Crawl your public website and test rendered pages against WCAG 2.1 AA checks.
Receive a plain-English issue list with severity, page URL, WCAG criterion, and recommended fix.
Share vendor-ready fixes with your website provider, IT team, or content staff.
Run recurring scans and maintain a documented accessibility monitoring history.