WordPress Just Raised the Bar on Accessibility-Ready Themes: What the June 30 Deadline Means for Your Site

Tomorrow — June 30, 2026 — WordPress is pulling the accessibility-ready tag from themes that haven’t met its updated requirements. If your site runs one of those themes, you may wake up to discover your “accessible” theme no longer carries that designation. Here’s what changed, who’s affected, and what you should do before the deadline hits.

What the Accessibility-Ready Tag Actually Means

The WordPress theme directory has offered an “accessibility-ready” tag since 2012. When a theme carries this tag, it signals that the theme has been reviewed against a set of baseline accessibility requirements — things like keyboard navigation, visible focus states, correct heading hierarchy, and sufficient color contrast.

The tag is not a guarantee of full WCAG compliance. It’s a starting point — a signal that the theme developer has made accessibility a deliberate consideration, not an afterthought. For site owners who aren’t accessibility experts, it’s often one of the first filters they apply when choosing a theme.

That’s exactly why the quality of the tag matters. An accessibility-ready label on a theme with real accessibility gaps doesn’t just mislead site owners — it misleads the disabled users those owners are trying to serve.

What WordPress Changed (and Why)

On May 6, 2026, the WordPress Accessibility Team published updated requirements for the accessibility-ready tag. The changes reflect how much web accessibility standards have evolved since 2012 — and how much more capable today’s tools and developers are at actually meeting them.

The core changes include:

• Recommendations removed, requirements tightened. Previously, the tag review mixed hard requirements with softer recommendations. The updated guidelines strip out the recommendations entirely. If something wasn’t important enough to be a requirement, it’s gone. If it was important enough to stay, it’s now a requirement.
• Standardized testing format. Each requirement now includes a clear description of what’s expected, step-by-step testing instructions, explicit pass/fail criteria, and links to the relevant WCAG success criteria. Reviewers and theme developers are working from the same playbook.
• WCAG 2.2 alignment. WordPress targets WCAG 2.2 Level AA as its development standard. The accessibility-ready requirements have been updated to reflect 2.2, not the older 2.1 baseline many themes were reviewed against.

The team gave theme authors until June 30, 2026 to bring their themes into compliance with the new requirements — or have the accessibility-ready tag removed from their listing.

What Happens to Non-Compliant Themes

Themes that don’t meet the updated requirements and show no active engagement from their authors will have the accessibility-ready tag removed. The theme itself stays in the directory — it just loses the tag.

For site owners, this creates a real problem: you may have chosen your theme specifically because it was labeled accessibility-ready. If the tag is removed, that designation no longer applies. You don’t get an automatic notification. You may not notice until an accessibility audit — or worse, a demand letter — surfaces the gap.

It’s also worth understanding what “the tag gets removed” doesn’t mean: it doesn’t mean your site becomes newly non-compliant overnight. The theme’s actual code hasn’t changed. If it had accessibility problems before June 30, it had them before the deadline too. The deadline is about WordPress cleaning up its directory labels, not about creating new legal exposure for site owners — but it is a useful signal that your theme’s accessibility may never have been as solid as you thought.

How to Check Whether Your Theme Is Affected

If you’re running a theme from the WordPress.org directory, here’s how to assess your situation:

1. Check your theme’s directory listing. Go to wordpress.org/themes, search for your theme by name, and look at the tags listed on its page. If “accessibility-ready” appears today but disappears after June 30, your theme didn’t pass the updated review.
2. Look for active maintenance. Themes that haven’t been updated in over a year are unlikely to have been reviewed against the new requirements. A stale, unmaintained theme is a flag regardless of what tags it carries.
3. Run your own accessibility audit. Don’t rely solely on the tag as your signal. A tool like LEWCA can scan your site against WCAG 2.2 criteria and surface real code-level issues — keyboard traps, missing focus styles, unlabeled form fields, contrast failures — independent of what the theme’s tag says.

What the Accessibility-Ready Tag Can’t Tell You

Even a theme that passes the updated review with flying colors only gets you part of the way to an accessible site. Here’s what the tag doesn’t cover:

• Your content. Theme-level accessibility and content-level accessibility are two different things. A heading hierarchy broken in your page editor, an image uploaded without alt text, a video embedded without captions — none of that is the theme’s responsibility. It’s yours.
• Your plugins. Every plugin you add to your site introduces its own accessibility characteristics. A contact form plugin with unlabeled fields, a popup plugin that traps keyboard focus, a slider that auto-plays without pause controls — these can undermine an otherwise accessible theme entirely.
• Your customizations. If you’ve modified your theme’s CSS, added custom code blocks, or used a page builder on top of the theme, you’ve taken on responsibility for the accessibility of those additions.

The accessibility-ready tag is a useful baseline filter when choosing a theme. It was never meant to be a compliance certification. Treating it as one is one of the most common mistakes site owners make — and one the WordPress Accessibility Team is actively trying to correct with these updated standards.

What to Do If Your Theme Loses the Tag

If your theme drops the accessibility-ready designation after June 30, you have a few options:

• Contact the theme author. Some themes will be in active review and simply haven’t completed the process by the deadline. Check the theme’s support forum on WordPress.org to see if the author is engaged.
• Audit what you actually have. Use a scanner to identify what accessibility issues exist in your current site. You may find the issues are minor and fixable without switching themes.
• Consider your options if the theme is abandoned. A theme with no active maintenance and failing accessibility is a liability worth addressing — not just for accessibility reasons but for security and compatibility as well.
• Don’t assume switching themes solves everything. A different accessibility-ready theme will have a baseline advantage, but your content-level and plugin-level issues come with you regardless of which theme you’re running.

Take Action

Whether your theme keeps its accessibility-ready tag or loses it tomorrow, the only way to know the actual accessibility state of your WordPress site is to scan it. LEWCA’s WCAG scanner checks your site against real WCAG 2.2 success criteria at the code level — across your theme, content, and plugins — and identifies actual issues rather than relying on a directory label. LEWCA Pro adds AI-powered fix suggestions and scheduled scanning so you stay current as your site changes over time. Download LEWCA free to run your first scan today, or see the pricing page to explore what Pro adds to your accessibility program.