Homechevron_rightStandardschevron_rightADA Title II Web Accessibility

ActiveInternational Standardupdate Standard Updated: April 2026fact_check Fact checked: Jun 28, 2026

ADA Title II Web Accessibility

28 CFR Part 35 — Web and Mobile Accessibility for State and Local Governments (WCAG 2.1 AA)

apartmentPublishing Organization:U.S. Department of Justice (DOJ)

United States Government Education Technology Services

Standard Introduction

ADA Title II Web Accessibility is an active standard published by U.S. Department of Justice (DOJ). It is commonly used across Government, Education, Technology, Services and applies in United States.

Use this page to review the official documentation, current status, and the certification or assessment bodies most commonly associated with ADA Title II Web Accessibility.

Implementation Roadmap

Phase 1schedule Duration: 3-6 weeks

Define state and local government web and mobile accessibility scope

Identify the products, services, systems, entities, jurisdictions, teams, vendors, and stakeholders covered by ADA Title II Web Accessibility. Confirm owners, boundaries, applicable obligations, documentation, and evidence expectations for public entity web content, mobile applications, third-party arrangements, WCAG 2.1 Level AA, exceptions, accessibility statements, procurement, testing, remediation, complaint handling, monitoring, and compliance deadlines.

Phase 2schedule Duration: 4-10 weeks

Assess obligations and gaps

Compare current practices with the expected state and local government web and mobile accessibility approach. Review digital inventory, WCAG testing, accessible design system controls, procurement clauses, vendor accessibility evidence, document remediation, mobile app testing, exception review, issue tracking, complaint response, training, and governance reporting, then prioritize gaps by legal exposure, safety or rights impact, customer commitments, operational dependency, reporting deadlines, and audit readiness.

Phase 3schedule Duration: 8-24 weeks

Implement controls and evidence

Deploy required procedures, technical controls, review gates, training, supplier workflows, reporting paths, and operational records. Maintain web and app inventories, VPATs or accessibility conformance reports, test results, remediation tickets, procurement records, policy documents, training records, exception decisions, complaint logs, monitoring reports, and executive updates as traceable evidence.

Phase 4schedule Duration: Ongoing

Review, report, and improve

Run management reviews, internal checks, independent assessments where applicable, corrective actions, and change reviews. Refresh the program when products, vendors, laws, incidents, reporting cycles, or stakeholder expectations change.

Compliance Checklist

0 / 12

Frequently Asked Questions

Who needs ADA Title II Web Accessibility?

expand_more

ADA Title II Web Accessibility is most relevant to state and local governments, public entities, agencies, districts, public higher education, and vendors providing digital services on their behalf. The exact scope depends on products, services, jurisdictions, reporting duties, customer commitments, and the organization's role in the relevant ecosystem.

Is ADA Title II Web Accessibility certifiable?

expand_more

ADA Title II web accessibility is a federal civil-rights compliance obligation, not a certification. The final rule adopts WCAG 2.1 Level AA as the technical standard for covered web content and mobile apps.

What should implementation focus on first?

expand_more

Start by defining scope, obligations, accountable owners, and the evidence expected by regulators, customers, auditors, or governance bodies. Then perform a gap assessment against current controls and prioritize remediation by risk and deadline.

What evidence is useful for ADA Title II Web Accessibility?

expand_more

Useful evidence includes web and app inventories, VPATs or accessibility conformance reports, test results, remediation tickets, procurement records, policy documents, training records, exception decisions, complaint logs, monitoring reports, and executive updates. Evidence should be version-controlled, attributable to owners, linked to obligations and controls, and retained for the required review or audit period.

How often should the program be reviewed?

expand_more

Review it at planned intervals and whenever laws, products, vendors, incidents, reporting cycles, customer commitments, or assurance expectations change. Higher-risk obligations should have more frequent monitoring and management reporting.