For state and local government

Prepare public digital services for Title II

The DOJ rule uses WCAG 2.1 AA for covered state and local government web content and mobile apps. Current dates are April 26, 2027 or April 26, 2028, depending on population and entity type.

Work through citizen services

Scan public forms

Find automated issues in permit applications, tax portals, and feedback forms, then test complete tasks with people and assistive technology.

Prioritize severe barriers

Triage critical and serious barriers first, assign owners, and re-scan changed pages without hiding the manual-review backlog.

Maintain public statements

Keep a reviewed accessibility statement and dated evidence that reflect current findings without promising legal compliance.

See the evidence before signing up

The sample is a real report view: severity, affected element, rule, and a practical direction for the fix. Automated coverage is clearly separated from manual review.

Preview of a wcagc scan report
Preview of a wcagc scan reportOpen sample report

Common questions

Is this only for accessibility specialists?
No. The workflow is written for developers, product teams, operators, and delivery leads, with the underlying rule and evidence kept visible.
Does a clean scan mean the site conforms?
No. Automated checks cover only part of WCAG. Manual review is still required for a conformance assessment.
What can the team do after a scan?
Save the site, scan more pages, track recurring rules and regressions, follow the manual checklist, and draft an accessibility statement from the evidence.