Key points
- The technical standard is WCAG 2.1 Level A and AA.
- The rule covers web content and mobile apps a public entity provides directly or through contractual, licensing, or other arrangements.
- The compliance date is April 26, 2027 for public entities with a population of 50,000 or more, other than special district governments.
- The compliance date is April 26, 2028 for public entities with a population under 50,000 and for all special district governments.
What does the ADA Title II web rule require?
Subject to the rule’s provisions, exceptions, and limitations, covered state and local governments must ensure that their web content and mobile apps conform to WCAG 2.1 Level A and AA by the applicable compliance date.
Title II applies to state and local government entities. The web rule includes websites and mobile apps provided through contracts, licenses, or other arrangements. Its technical standard is WCAG 2.1, not WCAG 2.2. Read 28 CFR 35.200 and the DOJ web rule fact sheet for the rule’s scope, exceptions, and limitations.
Does Title II apply to software vendors?
The Title II obligation belongs to the public entity, not to a software vendor merely because it sells to government. However, the rule covers technology the public entity provides through contractual, licensing, or other arrangements, so public buyers may incorporate accessibility requirements into RFPs, contracts, renewals, and vendor reviews.
A buyer may request testing evidence, an ACR, known limitations, and remediation information. These are possible procurement expectations, not a claim that Title II requires every private vendor or every contract to provide an ACR.
What are the Title II compliance deadlines?
The compliance dates are April 26, 2027 or April 26, 2028, depending on the public entity’s population and whether it is a special district government.
On narrow screens, scroll the table horizontally to read all columns.
| Public entity category | Compliance date | Technical standard | Official source |
|---|---|---|---|
| Population of 50,000 or more, other than a special district government | April 26, 2027 | WCAG 2.1 Level A and AA | 28 CFR 35.200(b)(1) |
| Population under 50,000 | April 26, 2028 | WCAG 2.1 Level A and AA | 28 CFR 35.200(b)(2) |
| Special district government | April 26, 2028 | WCAG 2.1 Level A and AA | 28 CFR 35.200(b)(2) |
The Department of Justice extended both dates by one year through an interim final rule effective April 20, 2026.
What might public buyers ask vendors to provide?
The rule does not prescribe one universal vendor evidence package. In procurement, a public buyer may ask vendors for information that helps it evaluate whether the technology will support the entity’s accessibility obligations.
- A current ACR for the relevant product and version.
- The standards and VPAT edition covered.
- Evaluation methods and test scope.
- Known accessibility limitations.
- Supporting findings or issue details.
- A remediation roadmap or status update.
- Responses to an accessibility questionnaire.
- Retesting or updated reporting after material product changes.
These are possible buyer requests, not universal legal requirements. Read How procurement teams review a VPAT/ACR and How software vendors should answer accessibility questions in an RFP for procurement preparation.
What does Title II mean for public colleges and universities?
Public colleges and universities are public entities under Title II. The applicable deadline generally depends on the population used for the state or local government of which the institution is part, not the institution’s student enrollment.
Public institutions should evaluate their own websites, mobile apps, documents, and online services. Vendor-provided learning platforms and other technology may be covered when provided through contractual, licensing, or other arrangements. DOJ’s first steps toward compliance explains population-based timing, including public institutions.
Private institutions may have different legal requirements; not every college is a Title II entity. Explore Accessibility services for education and EdTech and the EdTech accessibility audit and ACR case study for evaluation context.
How does Title II compare with Section 508 and HHS Section 504?
Title II, Section 508, and the HHS Section 504 web rule cover different entities and have different technical and timing requirements. This is a high-level comparison, not legal advice.
On narrow screens, scroll the table horizontally to read all columns.
| Rule | Who is directly covered | Web or ICT standard | Current compliance timing |
|---|---|---|---|
| ADA Title II | State and local governments. | WCAG 2.1 Level A and AA for covered web content and mobile apps. | April 26, 2027 or April 26, 2028, depending on the public entity. |
| Revised Section 508 | Federal agencies’ information and communication technology. | Revised Section 508 Standards, including incorporated WCAG 2.0 Level A and AA requirements and additional ICT provisions. | Current standards applicable since 2018. |
| HHS Section 504 web and mobile rule | Recipients of HHS federal financial assistance. | WCAG 2.1 Level AA. | May 11, 2027 for recipients with 15 or more employees; May 10, 2028 for recipients with fewer than 15 employees. |
The Section 508 compliance guide for software and ICT vendors explains federal ICT requirements and the buyer’s use of an ACR.
How should software vendors prepare?
Vendors can prepare by connecting customer requirements to a defined evaluation scope and keeping accessibility evidence aligned with the product.
- Identify which customers are public entities and which requirements appear in their RFPs or contracts.
- Confirm the product, version, platforms, roles, and workflows buyers use.
- Evaluate relevant web content and mobile-app functionality against WCAG 2.1 Level A and AA when Title II buyer requirements apply.
- Review or update the product’s ACR.
- Document known limitations accurately.
- Develop and track a remediation plan.
- Retest material fixes.
- Keep the ACR and supporting evidence aligned with the current product version.
Related support includes Website and web application accessibility audits, VPAT testing and ACR services, and the Procurement readiness program.
Does Title II require WCAG 2.2?
No. The Title II web and mobile accessibility rule specifies WCAG 2.1 Level A and AA. A public entity or buyer may choose to request WCAG 2.2 testing as an additional requirement, but that does not change the technical standard incorporated into 28 CFR 35.200.
What are the ADA web accessibility requirements in 2026?
The Department of Justice’s April 2026 interim final rule moved the first Title II web and mobile accessibility compliance date to April 26, 2027 and the second to April 26, 2028. No Title II WCAG compliance date now falls in 2026. Public entities still have ongoing ADA obligations to provide accessible programs, services, and activities.
Common Title II questions
When is the ADA Title II web accessibility deadline?
April 26, 2027 applies to public entities with a population of 50,000 or more, other than special district governments. April 26, 2028 applies to public entities with a population under 50,000 and all special district governments. See the Title II deadline table.
Does Title II apply to private software companies?
Title II directly applies to public entities. A private software company can be affected through procurement and contractual requirements when its technology is used by a public entity, but the public entity retains the Title II obligation.
Does Title II cover mobile apps?
Yes. The rule covers web content and mobile apps that a public entity provides or makes available, including through contractual, licensing, or other arrangements.
What WCAG version does Title II require?
WCAG 2.1 Level A and AA.
Does a VPAT or ACR prove Title II compliance?
No. An ACR documents a vendor’s conformance claims for a particular product and scope. A public entity must evaluate that evidence in the context of the technology, its use, and the entity’s obligations.
Were the Title II deadlines extended?
Yes. The April 2026 interim final rule extended the two compliance dates by one year, to April 26, 2027 and April 26, 2028.
