Four days before the April 24, 2026 compliance deadline, the Department of Justice quietly dropped a bombshell: ADA Title II web accessibility deadlines have been extended by one year. If your state or local government WordPress site has been racing to comply, you just got a reprieve. But before you exhale completely, there is a critical caveat — and the lawsuit landscape has never been more dangerous for any public-facing website.
What the DOJ Actually Changed
On April 20, 2026, the Department of Justice published an interim final rule in the Federal Register extending the compliance dates under its ADA Title II web and mobile app accessibility rule. The new deadlines are:
- Large public entities (population of 50,000 or more): Extended from April 24, 2026 to April 26, 2027
- Small public entities and special district governments (population under 50,000): Extended from April 26, 2027 to April 26, 2028
The DOJ cited two main reasons for the delay. First, the Department acknowledged it may have overestimated how available and mature the technology for web accessibility remediation actually is. Second, public entities reported significant resource constraints and staffing limitations that made hitting the original deadlines unrealistic as they approached.
Disability rights advocates were not pleased. Organizations representing users of assistive technology called the delay “unconscionable,” noting that people with disabilities have been waiting years for government websites to meet basic accessibility standards. The legal framework requiring WCAG 2.1 Level AA compliance under Title II has not changed — only the enforcement timeline has shifted.
The Deadline That Did NOT Move: HHS Section 504
Here is where WordPress site owners — particularly those in healthcare, education, or social services — need to pay close attention. The Department of Health and Human Services published its own Section 504 rule in May 2024, imposing parallel web and mobile accessibility requirements on any organization that receives HHS funding. That rule’s first compliance deadline is May 11, 2026, and HHS has not issued any extension.
This means hospitals, community health centers, universities, and nonprofits receiving federal health funding cannot treat the DOJ extension as a blanket all-clear. If you receive HHS funding, your accessibility obligations under Section 504 remain firmly on the original schedule. Non-compliance with WCAG 2.1 Level AA by May 11, 2026 could expose your organization to enforcement actions and civil complaints regardless of what the DOJ announced.
Private Sector Sites: Lawsuits Are Accelerating, Not Slowing Down
The DOJ extension applies only to state and local government entities under Title II. Private businesses operating under ADA Title III — meaning virtually every commercial website — have no equivalent deadline extension. What they do have is a rapidly growing pool of plaintiffs and an increasingly sophisticated legal infrastructure targeting inaccessible sites.
Plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025 — a 27% increase over 2024. Early 2026 data suggests that number could exceed 5,500 filings this year. Key patterns from the lawsuit data:
- E-commerce sites account for nearly 70% of all ADA web lawsuits
- Food and service businesses make up roughly 21% of filings
- New York, Florida, and Illinois lead in filing volume
- AI tools are enabling individuals to draft and file pro se complaints, contributing to a 40% increase in self-represented ADA lawsuits in 2025
- An increasing number of lawsuits explicitly name accessibility widgets and overlays as failed remediation attempts — with some filings claiming widgets interfere with screen readers or introduce new barriers
That last point deserves emphasis: courts are now looking at overlay-reliant sites and seeing not a good-faith compliance effort, but evidence that the underlying code was never fixed. Installing a widget does not reduce your litigation risk — in some documented cases, it has been used against defendants.
What This Means for Your WordPress Site Specifically
Whether you are running a government WordPress site that just got an extension or a commercial site that never had a hard deadline to begin with, the practical calculus is the same: use the time to fix the actual code, not to delay or deploy a band-aid.
If you run a government or public sector site
The one-year extension is real breathing room — use it for a proper audit and remediation cycle rather than waiting until early 2027. The original deadline created a last-minute scramble that produced a lot of low-quality, overlay-dependent compliance theater. A more deliberate approach — audit, fix, re-test, document — will hold up better under scrutiny and will actually serve your users with disabilities.
If you receive HHS funding
Do not confuse the DOJ extension with relief from your Section 504 obligations. Confirm with your legal counsel whether your organization falls under HHS’s rule and, if so, treat May 11, 2026 as a firm date. An audit completed now can identify your highest-risk issues in time to remediate them before the deadline.
If you run a private commercial site
No federal rule gives you a compliance date to aim for — which means lawsuit exposure is your primary risk driver. Given current filing volumes, the safest posture is to treat WCAG 2.1 Level AA as your operational baseline and document your remediation efforts. Courts look more favorably on defendants who can show ongoing, good-faith compliance work backed by real code changes.
What Good-Faith Remediation Actually Looks Like
Accessibility compliance on WordPress is not a single event — it is a maintenance discipline. Themes update, plugins introduce new components, and content editors add images without alt text. An audit you ran six months ago does not reflect the site that exists today.
Effective remediation starts with finding the actual WCAG violations in your markup: missing form labels, insufficient color contrast, images lacking descriptive alt text, keyboard traps, missing ARIA landmarks. You fix them at the code level — editing templates, configuring plugins correctly, training content editors. You do not layer a script on top of a broken page and call it done.
The tools that help are the ones that show you the specific lines of code that fail, explain which WCAG criterion is violated, and give you actionable guidance on how to fix it. The tools that create risk are the ones that promise “instant compliance” without touching a single line of your theme or content — the exact type of solution that is now being cited in lawsuits.
Take Action
Whether you are working against a May 2026 HHS deadline, planning for the extended April 2027 Title II date, or simply trying to reduce private lawsuit exposure, the path forward is the same: find your real accessibility issues and fix them. LEWCA’s free WordPress plugin scans your site for actual WCAG violations at the code level — surfacing the specific issues you need to fix, not just presenting a compliance score. LEWCA Pro adds AI-powered code fix suggestions, scheduled scanning so you catch regressions before they become liabilities, and compliance reports you can show auditors or legal counsel. Start with a free scan today and know exactly where your site stands.