Your ADA Title II Deadline Moved. The Work Didn't.

Updated September 21, 2026. This article originally ran on May 8, 2026 under the headline "The ADA Digital Accessibility Deadline Has Passed. Now What?" and told public entities the April 24, 2026 compliance date had arrived and they were in violation. That was wrong. The Department of Justice had already extended the Title II compliance dates in an interim final rule effective April 20, 2026 — four days before the original deadline and more than two weeks before this piece published. The article has been corrected and rewritten below. We regret the error.

Most organizations treated accessibility like a future problem. Something they would get to eventually — after the redesign, after the migration, after the budget opened up.

Then the deadline moved, and a lot of them exhaled.

That is the wrong reaction, and this article is about why.

What Actually Changed

The Department of Justice's 2024 final rule under Title II of the ADA requires every state and local public entity — parks departments, public universities, city agencies, transit authorities — to bring web content and mobile applications into conformance with WCAG 2.1 Level AA.

On April 20, 2026, the DOJ issued an interim final rule extending the compliance dates:

• Public entities serving 50,000 or more people: April 26, 2027, moved from April 24, 2026.
• Public entities serving fewer than 50,000 people, and special district governments: April 26, 2028, moved from April 26, 2027.

The standard itself did not move. It remains WCAG 2.1 Level AA — specifically the June 2018 version, incorporated by reference. Not WCAG 2.2. Not a softened subset.

The Department's stated reasoning is worth reading closely. It concluded it had overestimated how quickly covered entities could comply, citing resource constraints, staffing limitations, and the fact that automated tooling — generative AI included — still cannot reliably remediate content at scale. The date moved because the work turned out to be harder than expected. The work did not get smaller.

Why an Extension Is Not a Reprieve

Three things did not change on April 20.

The underlying obligation. Title II's non-discrimination requirement predates this rule by decades. The 2024 rule set a technical standard and a date. It did not create the duty, and the duty does not pause.

The litigation risk. Private plaintiffs do not wait for a rulemaking calendar. Demand letters from advocacy groups typically give organizations 30 to 60 days to respond before formal action, and they are still landing. Title III suits against private businesses have surged for years, and courts increasingly point to WCAG 2.1 AA as the benchmark with or without a federal mandate attached.

The volume of work. If anything, the extension is the DOJ telling you this takes longer than a year. An entity that starts in March 2027 will be in exactly the position the Department just acknowledged is unrealistic.

What the extension actually bought you is the ability to do this properly instead of in a panic. That is worth a great deal — but only if you use it.

What WCAG 2.1 Level AA Actually Requires

The guidelines follow four principles: Perceivable, Operable, Understandable, and Robust. In practice, that translates to specifics most teams have not fully addressed.

Every informational image needs meaningful alt text. Not "image_001.jpg." Not "photo." A description that conveys the same information a sighted user would get.

Video content needs captions and transcripts. Not auto-generated ones riddled with errors — accurate, synchronized captions.

Text needs a minimum contrast ratio of 4.5:1 against its background. That muted gray-on-white body text your designer loves probably does not pass.

All interactive elements — forms, navigation, modals, dropdowns — must be fully operable by keyboard alone. If someone cannot tab through your entire site and complete every action without a mouse, you are not compliant.

Proper semantic HTML structure matters. Screen readers rely on heading hierarchy, landmark regions, and ARIA labels to interpret a page. A div soup with no structure is invisible to assistive technology.

Why This Isn't Just a Public Sector Problem

The DOJ rule targets public entities, but the ripple effects reach further. Courts increasingly treat WCAG 2.1 AA as the de facto standard in private-sector litigation, even absent a specific federal mandate.

For nonprofits, the calculus is simpler. Many receive funding from or partner with municipal agencies. If your site does not meet the standard your partners are legally required to meet, that creates friction, and risk.

We have seen this firsthand. When we built the site for Hoffman Estates Park District, accessibility was not a separate workstream. It was woven into every design decision from day one — proper heading structure, keyboard-navigable program registration, contrast ratios tested across every component. The result is a site that serves every resident, not just the ones using a mouse and a 27-inch monitor.

Same approach with American Printing House for the Blind. When your organization exists to serve people with visual impairments, accessibility cannot be an afterthought. It informed the entire information architecture.

The Real Problem: Retrofitting Doesn't Work

Here is what we keep seeing. An organization realizes it needs to address accessibility, runs an automated scan, gets a report with 200 issues, and starts patching. Fix the alt text. Bump the contrast. Add some ARIA labels.

Six months later, someone publishes a new page that breaks everything the patch fixed.

Automated tools catch roughly 30% of accessibility issues. The rest require manual testing with actual humans navigating via screen readers, keyboard-only input, and voice control. A passing score on an automated scan does not mean your site is accessible. It means you have addressed the low-hanging fruit.

The organizations that get this right do not treat accessibility as a remediation project. They build it into their design system, their content workflow, and their QA process. Every new page, every new component, every content update follows the same standard.

This is precisely the work that an extra year makes possible and a three-month scramble does not.

What to Do With the Time

If your organization falls under Title II, the goal between now and your date is to build a durable process, not to generate a one-time cleanup.

Find your date first. Population served determines whether you are working toward April 2027 or April 2028. Special district governments — including many park districts — fall in the 2028 group regardless of the population they serve.

Start with a manual audit of your most-visited pages. Homepage, contact page, key service pages, any forms or applications. These are the pages most likely to generate complaints, and complaints do not wait for your compliance date.

Test keyboard navigation end to end. Can someone complete your most critical user journey without touching a mouse? Finding information, submitting a form, registering for a program. If not, that is your first priority.

Check color contrast across the entire site. Tools like the WebAIM Contrast Checker make this fast. Pay particular attention to buttons, links, and form labels.

Review your images. Every informational image should have descriptive alt text. Decorative images should have empty alt attributes so screen readers skip them.

Fix the workflow, not just the pages. Put accessibility checks into your content publishing process and your QA process. Otherwise you will be doing this audit again in eighteen months.

Document your plan. A published accessibility roadmap with specific milestones demonstrates good faith and reduces legal exposure — legal analyses from BBK Law and Duane Morris detail what compliance preparation should include. It is the difference between an organization that ignored the requirement and one actively working toward compliance.

The Bigger Picture

Compliance deadlines have a way of making organizations treat accessibility as a checkbox. Check the contrast, add the alt text, file the report.

But the organizations that actually benefit from this work are the ones that recognize what it really is — better design. Accessible sites are more usable for everyone. Clear hierarchy helps all users find information faster. Proper contrast makes content readable in sunlight. Keyboard navigation serves power users and people with disabilities equally.

We have written before about accessibility as a design discipline rather than a compliance exercise. A moved deadline does not change that position. It just means you have been handed the one thing most teams said they needed: time.

The worst outcome of this extension would be spending it the same way the last two years were spent.