The DOJ Web Accessibility Deadline, in Plain English

Which deadline applies to you

The dividing line is population, using Census Bureau figures:

• A city, county, or town uses its own population from the most recent decennial Census.
• A public school district uses the Census Bureau's population estimate for the district (its most recent Small Area Income and Poverty Estimates figure), not its enrollment. A district with 4,000 students can still serve a community of 60,000 people and fall under the earlier 2027 date.
• Special district governments (for example park districts, library districts, water and sanitation districts, and transit authorities) get the 2028 date regardless of population.

Two practical cautions. First, enrollment is not the test for schools, so do not assume a small student body means the later date. Second, edge cases exist (joint agencies, regional service centers, entities whose service area is hard to define), and the determination has legal weight. If your entity is anywhere near the line, this is a question for your counsel, not a guess.

Was the Title II deadline extended?

Yes, by one year. On April 20, 2026, the Department of Justice published an interim final rule that moved both compliance dates: from April 24, 2026 to April 26, 2027 for entities with a population of 50,000 or more, and from April 26, 2027 to April 26, 2028 for smaller entities and special district governments. Nothing else in the rule changed. The standard is still WCAG 2.1 AA, and the exceptions are the same.

DOJ's stated reason was that it had overestimated how quickly entities, with the staff and technology they have, could get there. If you read an article that cites a 2026 deadline, it was written before the extension.

Does the extension mean we can wait?

Not really. The extension moved the dates for the rule's specific technical standard. It did not pause Title II itself, which has applied to state and local governments since 1990. In the extension, DOJ said entities still have an ongoing obligation to make the services, programs and activities they offer online accessible under their existing ADA obligations, and OCR complaints about school websites were being filed for years before this rule existed.

The practical case is simpler: school and government sites are large, and the entities that struggle are the ones that start late. A year of extra runway is only useful if it gets used.

Does the rule apply to libraries, townships and fire districts?

Yes. The rule covers every state and local government entity, and there is no exemption for small ones. What varies is the date. A library or fire department that is part of a city, county or township generally shares that government's population and date. An independent library district, fire district or other special district government gets the April 26, 2028 date regardless of population. How a particular entity is organized decides which applies, so confirm it with your counsel.

The standard is WCAG 2.1, Level AA

The rule's technical standard is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. WCAG is the internationally recognized standard for accessible web content, written by the W3C, the body that maintains web standards. "Level AA" means the rule requires everything in Level A (the baseline) plus everything in Level AA (the widely adopted mid tier). In practice that covers things like:

• text alternatives for images, so screen reader users know what a picture shows;
• sufficient color contrast between text and its background;
• pages that work with a keyboard alone, without a mouse;
• captions for videos;
• headings, labels, and link text that make sense and are announced correctly; and
• forms a screen reader user can understand and complete.

A newer version, WCAG 2.2, exists, and testing against it is reasonable and forward-looking. But the rule's legal benchmark is 2.1 AA, so that is the version to cite in planning documents and vendor contracts.

What "conformance" actually means

Conformance means the web content your entity makes available to the public meets WCAG 2.1 AA. A few points that surprise people:

• It covers more than your homepage. The rule reaches your whole public site, plus mobile apps, plus documents you post, including PDFs. A newsletter PDF or board packet uploaded to the site is web content.
• It is ongoing, not one-time. The deadline is when conformance begins, not when it ends. School and government sites change constantly, and a page that was fine in April can pick up new issues in May. Whatever process you build has to keep working after the deadline passes.
• Vendor-built does not mean vendor-responsible. Under Title II, responsibility for a public entity's website stays with the entity, even when an outside vendor builds and hosts it. Your vendor may be contractually obligated to help, and a good one will, but the legal obligation to the public is yours. More in what your website vendor can and cannot cover.

The rule does contain a small set of exceptions, for things like archived web content, certain preexisting documents, and certain third-party content. They are written narrowly and each has conditions attached. Whether any exception actually applies to specific content on your site is exactly the kind of question to put to your counsel rather than answer from a summary, including this one. Our guide to old PDFs and the archive exceptions walks through the two that matter most for schools.

What happens after the deadline

After your compliance date, web content that does not conform to WCAG 2.1 AA can be the basis of an ADA Title II complaint or enforcement action. For schools, complaints commonly go to the U.S. Department of Education's Office for Civil Rights (OCR); complaints can also go to DOJ, and individuals can bring lawsuits under Title II. Anyone can file a complaint, including a parent, a resident, or an advocacy group, and there is no requirement that they warn you first.

None of that is a reason to panic, and this page is not going to quote you scary numbers. It is a reason to start early, because the entities that struggle are usually the ones that discovered the problem with months left instead of years.

A sensible way to start

You do not need to commit to anything to find out where you stand. A reasonable first sequence looks like:

• Confirm your date. Establish with your counsel whether you are a 2027 or a 2028 entity.
• Get a factual baseline. Run an automated scan to see what is actually on your site today: missing alt text, low-contrast text, unlabeled forms, inaccessible PDFs. Automated testing cannot find every barrier, but it finds the most common ones fast and gives you a concrete list.
• Sort the list by who fixes it. Some issues live in content your staff posts and can be fixed in your CMS today. Others live in the template and belong with your website vendor.
• Plan for after the deadline. Decide how new content will be checked on an ongoing basis, since the obligation does not end in 2027 or 2028.

If you want that baseline without installing anything or talking to a salesperson, we offer a free accessibility audit of your site: real pages, real findings, each with a screenshot, in plain English. It is a factual snapshot of where your site stands today, and it is yours whether or not you ever pay us anything.