The ADA Website Accessibility Deadline Moved. Your Risk Didn’t.

In April, the Department of Justice gave state and local governments another year to make their websites accessible. A few weeks later, Health and Human Services did the same for hospitals, clinics, and anyone else taking its funding. Plenty of marketing teams read those headlines and moved accessibility to next year's list. Here's why that's the wrong call.

What actually changed

Two federal rules set the first hard technical standard for website accessibility in the U.S. Both require WCAG 2.1 Level AA, the same set of guidelines designers and developers have been working from for years.

• ADA Title II covers state and local governments, public colleges and universities, courts, and special districts like transit and water authorities.
• HHS Section 504 covers organizations that receive funding from Health and Human Services. That includes most hospitals, health systems, clinics, and many nonprofits.

Here's the new calendar:

1. April 20, 2026DOJ publishes an interim rule pushing Title II deadlines back one year, four days before the original date.
2. May 7, 2026HHS follows with its own one-year extension for Section 504.
3. April 26, 2027Title II deadline for governments serving 50,000 people or more.
4. May 11, 2027Section 504 deadline for HHS-funded organizations with 15 or more employees.
5. April 26, 2028Title II deadline for smaller governments and special districts.
6. May 10, 2028Section 504 deadline for HHS-funded organizations with fewer than 15 employees.

One more detail worth knowing: the DOJ left the door open to revisiting the rule again before April 2027. That cuts both ways. It could get softer. It could also stay exactly as written, and a lot of organizations are betting on the first outcome.

Three reasons the delay doesn't help you

The web is getting worse at this, not better

Every year, WebAIM scans the home pages of the top one million websites. The 2026 results: 95.9% had detectable WCAG failures, up from 94.8% the year before. The average page had 56 errors.

The same six problems account for roughly 96% of everything they found:

• Low-contrast text83.9%
• Images missing alt text53.1%
• Form fields without labels51.0%
• Empty links46.3%
• Empty buttons30.6%
• Missing page language13.5%

Percentage of top one million home pages with each error. Source: WebAIM Million, 2026.

Look at the top of that list. Low-contrast text isn't a coding bug. It's a decision made in a design review: light gray body copy because it "feels cleaner," white text on a brand color that's a shade too bright, placeholder text standing in for labels. As a creative director, I'll own that our industry created a lot of this problem. The good news is that designers can fix most of it at the source by correcting a handful of color values in the design system instead of patching hundreds of pages.

Another finding worth flagging: pages that use ARIA (code meant to help screen readers) averaged 59 errors, compared to 42 on pages without it. More accessibility code, applied badly, makes things worse.

Accessible doesn't mean ugly

The most common pushback we hear from marketing teams is that accessibility will flatten the brand: bigger type, louder colors, everything looking like a government form. That's a design problem, not an accessibility problem, and it's solvable.

Look at what WCAG actually asks for. Text you can read. A clear visual hierarchy. Buttons that look like buttons. Forms that tell you what goes in each field. A visible marker showing where you are on the page. None of that is a constraint on good design. It is good design. It's what any decent art director would push for anyway.

Here's what that looks like in practice:

• Keep the brand color, adjust the shade. Most brand palettes can pass contrast with a small shift in value. Build an accessible "UI version" of each brand color for text and buttons, and keep the original for large shapes, illustration, and backgrounds.
• Design the focus state on purpose. Browsers draw a default outline that designers often remove because it looks clunky. Replace it with one that matches your brand instead of deleting it.
• Let hierarchy do the work. A strong type scale and real heading structure help screen reader users jump around the page, and they help a busy executive skimming on a phone just as much.
• Write link and button text like a headline. "Download the 2026 rate sheet" beats "Learn more" for accessibility, for SEO, and for click-through.

That last point is the bigger story. The changes that help someone using a screen reader also help someone reading your site on a phone in a bright parking lot, a buyer in their sixties who has their browser zoomed to 150%, and a procurement analyst comparing five vendors at once. You're designing for more of your audience, not less.

Your website isn't the only thing on the hook

Accessibility rules cover digital content, not just web pages. If your marketing and training materials go out to hospitals, universities, or public agencies, these need the same attention:

• HTML email. Image-only emails with the message baked into a graphic are invisible to screen readers and to anyone whose email client blocks images. Use live text, real alt text, and enough contrast in buttons and footers.
• Presentations and PDFs. Sales decks, spec sheets, and brochures get exported to PDF and emailed everywhere. Without a set reading order and tagging, a screen reader reads them out of order or not at all.
• eLearning and training courses. Onboarding modules, compliance courses, and customer training need captions, keyboard-navigable interactions, and readable text. Public universities and state agencies are covered under Title II, and their course content is part of that.
• Video. Auto-generated captions are a starting point, not a finished product. Product names and industry terms get mangled, and someone needs to review them.

The fix is the same everywhere: build accessibility into the templates and the production process so every new piece starts out right, instead of auditing each one after the fact.

Skip the overlay widget

You've probably seen the pitch: add one line of code, a little accessibility icon appears in the corner, and your site is compliant. It isn't. In January 2025, the Federal Trade Commission ordered accessiBe, one of the best-known overlay vendors, to pay $1 million over claims that its AI tool could make any website WCAG compliant. And according to EcomBack's mid-year 2025 report, 22.6% of website accessibility lawsuits targeted sites that already had an accessibility tool installed.

Overlays sit on top of the problem. The fix has to happen in the templates, the design system, and the content.

A realistic 90-day plan

You don't need to fix every page on your site by next spring. You need to fix the things every page is built from.

1. Weeks 1 to 2Scan your templates, not every pageRun free tools like WAVE, Lighthouse, or axe DevTools on one example of each template: home page, a service page, your contact form, a blog post, and your careers page. Fixing a template fixes every page that uses it.
2. Weeks 2 to 3Unplug your mouseAutomated scans catch roughly a third of real issues. Try completing your contact form and main navigation using only the keyboard. Then turn on VoiceOver (Mac) or NVDA (Windows, free) and listen to your home page for two minutes.
3. Weeks 3 to 6Fix the design system firstColor values, focus styles, button and link styles, and form components. These are small changes with site-wide reach, and they keep new pages from repeating old mistakes.
4. Weeks 6 to 9Clean up the contentAlt text, link wording, heading order, video captions, and the PDFs everyone forgets about: spec sheets, patient forms, rate tables, brochures. If you have training courses or onboarding modules, add them to this list.
5. Weeks 9 to 12Make it stickPublish an accessibility statement with a real way to report problems. Add accessibility checks to your publishing workflow and your vendor contracts. Put a quarterly re-scan on the calendar.

The bottom line

The extension is real, and it's useful if you spend it well. A year is enough time to fix a design system, clean up templates, and get your content in order without a fire drill. It's not enough time if you spend the first nine months waiting to see whether the rule changes again.

And for B2B companies, the strongest reason to do this isn't legal. It's that the people evaluating your company include people who navigate by keyboard, magnify their screens, or listen to your site through a screen reader. Some of them sign purchase orders.