Is this a state or local government entity?
Keep Title II context separate from private-sector ADA guidance.
ADA Title II web accessibility testing
Run selected WCAG 2.1 Level A and AA technical checks for state and local government web content under the versioned ADA Title II profile. Keep entity classification, exceptions, mobile apps, complete processes, and legal decisions outside the automated result.
Scanning profile
us-ada-title-ii-2026ADA Title IITechnical preflight
- Input
- State or local government web content
- Mapping
- 28 CFR Part 35 · WCAG 2.1 A and AA technical mapping
- Boundary
- Entity context and complete legal assessment remain manual
Technical standardWCAG 2.1 Level A and AA
Entity contextPopulation and special-district classification
Current datesApril 26, 2027 / April 26, 2028
Use ADA Title II through the API.
Send us-ada-title-ii-2026 with the asset and keep this profile’s evidence boundary in the returned result.
Route the entity before interpreting the deadline.
The profile records entity facts as context. It does not infer population, special-district status, an exception, or the legal consequence of a finding.
Is the entity at or above 50,000 people?
Record the relevant census-based classification outside the scan engine.
Is it a special district government?
The classification affects the current compliance date.
Could a content exception apply?
Flag claimed exceptions for qualified review and preserve the justification.
Move from a known baseline toward the required technical target.
A delta view lets public entities stop new regressions while existing technical debt and manual evaluation remain visible.
- Baseline
- Accepted remediation baseline
- Current
- Current release candidate
New failuresBlock by policy
Resolved findingsPreserve evidence
Recurring debtKeep assigned
Manual checksRemain open
The configured gate reacts to change, not a mystery score.
Join the federal rule to a reproducible WCAG result.
The profile maps the current technical standard while preserving the source rule, profile version, and unresolved human work.
28 CFR Part 35
The Title II web and mobile accessibility requirements and current context.
WCAG 2.1 Level A and AA
The web criteria used by the current rule.
Machine findings and coverage
Rendered conditions, selectors, criterion references, and baseline status.
Complete processes and exceptions
Work that cannot be decided responsibly from the submitted page.
Read the source behind this profile.
The ADA Title II source and its legal or standards context can change. AccessPreflight pins the profile version used for a scan; your organization should re-review applicability and the source when requirements change.
Run ADA Title II where content enters the workflow.
Keep the profile, coverage boundary, evidence, and human-review queue attached to every result.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.