Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities
The Title II rule establishes specific accessibility requirements for covered state and local government web content and mobile applications and identifies WCAG 2.1 Level AA as the technical standard subject to the rule's scope and exceptions.
What the authority record establishes
The Title II rule establishes specific accessibility requirements for covered state and local government web content and mobile applications and identifies WCAG 2.1 Level AA as the technical standard subject to the rule's scope and exceptions.
Binding federal regulation within its stated scope; official guidance summarizes but does not replace the regulatory text
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Permit portals, plan-upload interfaces, payment flows, maps, status tools, and mobile inspection or resident applications must be evaluated as public digital services rather than optional front-end decoration.
Affected operating stages
- Service Inventory
- Accessibility Assessment
- Remediation
- Procurement
- Testing
- Ongoing Governance
Capabilities to examine
Applicant Portal And Guided Intake
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for applicant portal and guided intake.
Electronic Plan Submission And Version Control
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for electronic plan submission and version control.
Fee Calculation Payments And Reconciliation
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for fee calculation payments and reconciliation.
Public Search Status And Communications
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for public search status and communications.
Mobile And Offline Field Inspections
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for mobile and offline field inspections.
Documents Records Retention And Public Disclosure
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for documents records retention and public disclosure.
Affected buyer audiences
- digital-service owners
- permitting and licensing leaders
- IT and accessibility teams
- procurement and legal
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
The guidance page does not decide a specific entity's legal obligations, exceptions, conformance, effective communication, reasonable modification, or litigation risk.