The 2027 Web Accessibility Deadline: What to Fix Now

If you thought April 2026 was the finish line for ADA web accessibility, the DOJ just moved the goalposts. On April 20, 2026, four days before the first deadline, the department issued an Interim Final Rule that pushed compliance dates to April 26, 2027, for larger entities and April 26, 2028, for smaller ones and special district governments. That extra year is not relief. It is breathing room, and what you do with it matters.

The substantive rule is unchanged. Public-facing sites must still meet WCAG 2.1 Level AA. Documents must be accessible. Vendor contracts must assign responsibility. Waiting simply compresses the work into a shorter, more expensive window.

In this post, we will unpack what changed and what did not, explain whether Title II applies to you and how it differs from Title III, and clarify which WCAG version is actually enforceable. We will look at why waiting costs more, what to fix first between now and 2027, and the two things everyone forgets: documents and vendor contracts. We will also answer common FAQs and close with the short version. Use the time. Do not spend it.

What Just Changed, and What Did Not

On April 20, 2026, four days before the first ADA Title II web compliance deadline, the DOJ issued an Interim Final Rule that pushed both dates back roughly a year. The obligation itself did not change. Only the calendar did.

The underlying rule was published in the Federal Register on April 24, 2024, adopting WCAG 2.1 Level AA (first released in June 2018) as the benchmark for web content and mobile apps.

Why the delay? DOJ pointed to four things: automated tools cannot reliably fix complex content like STEM and course materials without human review; many public entities lack staffing and budget; litigation risk was mounting; and the 2024 rule hyperlinked a "dynamically changeable" WCAG resource, creating real ambiguity about which version applied.

Here is the part worth sitting with: this rulemaking has lurched forward and stalled since 2010, across multiple administrations, and in 2025 DOJ announced a review of the economic impact of the ADA web regulations. Extensions are the pattern. Planning around the next one is a gamble.

Which raises the obvious question: does this rule even apply to you?

Does This Actually Apply to You? Title II vs. Title III

Here's the part that trips up almost everyone: Title II binds state and local governments, not every site the public can see. Nonprofits and private businesses generally fall under Title III instead. Read "public-facing" loosely and you'll spend a year worrying about a deadline that was never yours.

A public entity, in plain terms, is a state or local government or one of its arms. Cities, counties, school districts, public universities, transit authorities, and special districts are almost always in scope. Run a city portal or payment system under contract, and you inherit that exposure too.

Title III is a different story. Private-sector web rulemaking is paused indefinitely, so there's no April 2027 date waiting for a typical nonprofit or business. That isn't safety, though. Two tracks keep moving regardless.

Federal funding. If your nonprofit receives federal grants, Section 504 obligations can apply on their own timeline, and a grant agreement can impose accessibility terms independently of the ADA.

Litigation. Private enforcement actions and demand letters never paused. DOJ cited that risk as one of its own reasons for extending the Title II dates, which tells you how seriously to take it.

So here's the practical takeaway: the deadline may not be yours, but the standard still is. WCAG 2.1 AA is the benchmark courts, funders, and procurement teams already recognize, which makes it the safest target to build toward no matter which title covers you.

Which WCAG Version Is Actually Enforceable?

For now, the version question has a clean answer: WCAG 2.1 Level AA. That is the technical standard DOJ adopted, and the rule requires public entities to meet both Level A and Level AA success criteria in WCAG 2.1 (New Digital Accessibility Requirements in 2026). Measure against that, not against whatever a vendor's marketing page implies.

Here is the trap. The 2024 rule hyperlinked a "dynamically changeable" WCAG resource describing both 2.1 and later versions. DOJ itself acknowledged that this created compliance ambiguity and potential administrative-law problems, and that ambiguity factored into the April 2026 extension.

Plain-English translation: Level A is the floor, Level AA is the standard that applies to you, and Level AAA is aspirational and rarely required. Most audits, conformance reports, and vendor contracts are written against AA.

Every audit report organizes findings around four principles:

• Perceivable: content can be seen or heard.

• Operable: it works with a keyboard, not just a mouse.

• Understandable: it reads and behaves predictably.

• Robust: it works with screen readers and other assistive tech.

Concretely, AA looks like 4.5:1 color contrast on body text, keyboard operability for every interactive element, alt text on meaningful images, and captions or transcripts on video.

Build to 2.1 AA today and you are already most of the way to 2.2. Treat the version question as a reason to build durable fixes, not as a reason to wait for clarity that may never arrive.

Why Waiting Costs More Than Starting

Durable fixes are also the cheaper path, though that's an argument rather than a citation. There's no dollar figure showing that delay costs more. What follows is reasoning from how remediation actually works.

The cost curve bends one direction. Accessibility is cheap at design and build time and expensive as a retrofit across thousands of legacy pages, PDFs, and templates. You're not fixing a problem once; you're re-touching work you already shipped.

Then there's volume. Almost every organization undercounts its own content. The real backlog hides in PDFs, archived pages, course materials, and third-party embeds, and each one needs human review, not a script. Order of operations drives price, which is the same lesson behind why jumping to content first is a costly mistake.

DOJ made the argument for us. It extended the deadlines partly because automated tools cannot reliably remediate complex content without human review. That is a direct rebuttal to the last-minute overlay pitch.

Staffing is the other half. The extension was granted partly because entities lacked expertise and budget. Another year doesn't create either one unless someone starts hiring, training, or contracting now. The gap between patching and planning is the one we broke down in our DIY vs. professional website maintenance cost comparison.

Start early and you spread cost across two or three budget cycles instead of one compressed window, cut the odds of a rushed and incomplete fix, and build documentation of good-faith effort if a complaint ever lands.

What to Fix First Between Now and 2027

Once you decide to start, the order matters more than the speed. Skip the scan-and-declare-victory move. Automated tools reliably catch roughly a third of issues, so pair any scan with manual testing on your highest-traffic templates and your top twenty pages.

Then prioritize by template, not by page. Fixing your header, navigation, footer, and content components once propagates everywhere, which is the single highest-leverage move available.

Start with the big four, because they cause most real-world friction: keyboard navigation and focus order, color contrast, alt text on meaningful images, and form labels and error messages.

Documents are a separate workstream. PDFs and Word files need their own pass for headings, reading order, alt text, and tagged structure, and they are usually the largest hidden backlog. Use a content audit triage checklist to sort that pile without guessing, and a quick rewrite checklist for the Word files you keep republishing.

When the hard parts pile up, borrow a second set of eyes. A Seattle-based team that works on site design, content, and technical SEO every day can audit templates, documents, and third-party components together instead of treating accessibility as a bolt-on.

Finally, set a cadence so the fixes hold: an accessibility check inside your publishing workflow, a quarterly spot audit, and one named owner for accessibility questions. Without those, sites quietly drift back out of conformance. It is the same discipline behind making sure your website is doing its job after launch.

Documents and Vendors: The Two Things Everyone Forgets

Your template fixes don't reach the stuff living outside your page HTML. The rule covers "web content and mobile applications," and documents you serve from your site count as web content. That means the PDF you posted in 2019 is in scope.

Your document checklist:

• Tagged headings that map to real structure

• Genuine reading order, not the order a text box landed on the page

• Alt text on meaningful images

• Tables with header rows and simple structure

• Link text that describes the destination ("2027 compliance guidance," not "click here")

• A tagged, searchable PDF instead of a flat scan of paper

Vendors are the other blind spot. Buy a learning platform, a portal, a booking tool, or a CMS module, and you still own what your visitors encounter. "We didn't build it" isn't a defense when a screen reader can't use the registration form.

Clauses worth adding to new agreements:

• A named commitment to WCAG 2.1 AA conformance

• An accessibility conformance report before purchase

• Remediation timelines with dates

• An indemnification or remedy path if the product fails

Then do the unglamorous part: pull existing contracts before renewal season. Accessibility language is easy to negotiate upfront and awkward to bolt on as an amendment six months later.

There's upside too. Accessible procurement language is now standard in many public-sector and grant-funded contracts, so nailing it protects your eligibility for funding and partnerships, not just your compliance posture.

FAQs About the ADA Web Accessibility Deadlines

Contracts and documents sorted, the scope question usually comes next. Here's what people ask most.

Is my nonprofit required to comply with ADA Title II? No, not directly. Title II covers state and local government entities. Most nonprofits fall under Title III, where federal web rulemaking is paused indefinitely. If you receive federal funding, Section 504 obligations may still apply.

What is WCAG 2.1 AA? It's the standard DOJ adopted: testable success criteria for making web content and mobile apps usable by people with disabilities. AA is the middle of three conformance levels, and the one audits and contracts are written against.

When is the ADA website deadline? For public entities serving 50,000 or more people, April 26, 2027. For those under 50,000 and any special district government, April 26, 2028. An Interim Final Rule issued April 20, 2026 pushed both back roughly a year. They're current but not final, pending a 60-day comment period.

Do automated accessibility overlays solve this? Not on their own. DOJ's stated reason for extending the deadlines was that automated tools cannot reliably remediate complex content without human review. Overlays flag some issues; they don't replace manual testing.

Can I be sued if no deadline applies to me? Yes. Private enforcement actions kept moving through the Title III pause, and DOJ cited litigation risk as one of its own reasons for extending the Title II dates.

The Short Version: Use the Time, Do Not Spend It

So here is the whole thing in one breath. The deadlines moved to April 26, 2027 for public entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special district governments. The standard is still WCAG 2.1 Level AA. The obligation never changed. Only the calendar did.

And the scope line matters. Title II binds public entities. Nonprofits and businesses generally fall under Title III, where rulemaking is paused. That pause removes a deadline, not the litigation risk.

Three things worth doing this quarter:

• Run a manual audit on your top templates, not just your homepage.

• Inventory your PDF and document backlog so you know how big the job actually is.

• Add accessibility language to your next vendor renewal, before you sign.

The organizations treating this as runway rather than relief are the ones who will finish remediation inside a normal budget instead of a compressed, expensive one.

If you would rather not untangle scope, standards, and remediation alone, Watt Consulting can take a look at your site and give you a plain-language starting point. No hard sell, just a clear next step.

Conclusion

The 2027 deadline is not a reason to wait. It is a chance to fix accessibility before remediation becomes urgent and expensive. Public entities face April 26, 2027 or 2028 depending on size, but the standard remains WCAG 2.1 Level AA. Title II applies to public entities, while Title III businesses and nonprofits still carry litigation risk even without a new deadline. Start with a manual audit, a document inventory, and accessibility terms in vendor contracts. These steps turn a vague compliance burden into a manageable plan. If you need direction, Watt Consulting can review your site and offer a plain-language next step. Use the runway now, and you can enter 2027 ready instead of reactive.