ADA Web Accessibility Deadline Hits April 24: Government WordPress Sites Must Meet WCAG 2.1 AA

The clock is ticking. On April 24, 2026, the U.S. Department of Justice’s ADA Title II web accessibility rule takes effect for state and local governments with populations of 50,000 or more. Every government website — including those built on WordPress — must meet WCAG 2.1 Level AA standards or face potential DOJ enforcement actions.

What Happened

The DOJ finalized this rule in March 2024, establishing WCAG 2.1 Level AA as the mandatory technical standard for all government web content and mobile applications. After a two-year compliance window, the first deadline arrives on April 24, 2026. A second deadline — April 26, 2027 — applies to smaller governments (under 50,000 population) and all special-purpose districts regardless of size.

The scope is broad. The rule covers:

• Primary government websites
• Web-based applications and portals
• Mobile apps
• Online forms and PDF documents
• Third-party content hosted on government platforms (including content developed by outside vendors)

That last point is critical for WordPress sites. If a government agency uses a WordPress theme or plugin that generates inaccessible output, the agency is still responsible for compliance — not the theme or plugin developer.

Why It Matters

WordPress powers a significant number of government websites at every level. Many use third-party themes, page builders, and plugins that may not produce WCAG-compliant output by default. Common issues include missing alt text on images, poor heading hierarchy, inaccessible forms, insufficient color contrast, and keyboard navigation failures.

The important caveat: no accessibility plugin can make a site fully compliant on its own. Studies show automated scanning tools catch only about 30% of WCAG issues. The remaining 70% involve content decisions, design choices, and user testing that require human judgment. Organizations that installed an accessibility overlay widget and called it done are likely not compliant.

This also sets a precedent. While the April 24 deadline technically applies to government entities, private-sector ADA lawsuits have been trending upward for years. Courts increasingly reference WCAG 2.1 AA as the standard for commercial websites too. What’s mandatory for government today often becomes expected for everyone tomorrow.

What You Should Do

Government WordPress administrators: You have 34 days. If you haven’t started an accessibility audit, begin immediately. Run your site through WAVE or axe DevTools for automated scanning, then conduct manual keyboard and screen reader testing. Prioritize high-traffic pages and online services (forms, payments, applications).

WordPress developers serving government clients: Audit every theme and plugin for accessibility. Check heading structure, form labels, ARIA attributes, focus indicators, and color contrast ratios. The ADA.gov first steps guide is a practical starting point.

Everyone else: Use this as motivation to review your own site’s accessibility. Good accessibility practices — proper headings, alt text, keyboard navigation, semantic markup — also improve SEO and, as the WP:26 enterprise report noted, make your content more discoverable by AI agents.

Sources

• New Rule on Accessibility of Web Content and Mobile Apps — ADA.gov
• First Steps Toward Complying with the ADA Title II Web Rule — ADA.gov
• ADA Website Accessibility: WCAG 2.1 by 2026 — WordPress VIP