Briefing

WordPress Tightens Theme Accessibility Rules, Sets June 30 Deadline

ux
by Krupa Nanda · WordPress Gutenberg

Check the updated 7.0 release party schedule and review the 22 milestoned tickets for 7.1 to ensure accessibility compliance before the release.

What to do now

Review the 22 milestoned tickets for 7.1 and test real‑time collaboration for accessibility gaps.

Summary

WordPress has rolled out a comprehensive overhaul of its theme accessibility‑ready guidelines, shifting from a mix of recommendations to a strict set of mandatory criteria that align more closely with WCAG 2.1 and 2.2 standards. The new handbook eliminates all advisory language, elevating several best‑practice items to hard requirements and re‑writing requirement titles for clearer expectations. Each guideline now follows a uniform structure: a basic principle, a detailed testing section with tools and step‑by‑step pass/fail criteria, and links to the relevant WCAG documentation.

Key mandatory checks include support for reflow, resize, and text‑spacing changes; avoidance of unexpected context changes; accessibility of content that appears on hover or focus; inclusion of an accessibility statement; and a prohibition on recommending or requiring inaccessible plugins. A Google Sheet template standardises the testing documentation process, making it easier for developers without deep accessibility knowledge to provide consistent feedback. Theme authors have until June 30 2026 to update their themes or remove the accessibility‑ready tag. A webinar on May 21, Global Accessibility Awareness Day, will walk participants through the new testing process, and the goal is to re‑test all 108 current accessibility‑ready themes.

In parallel, WordPress has expanded its accessibility documentation on the WordPress Accessibility site. April 2026 saw new sections covering WCAG introduction, alternative text for images, headings, link text, and images as links, as well as design‑related guidance on styling links. Front‑end code documentation now includes alt text for SVGs and icons, image animation accessibility, and heading structure for theme development. The team plans to add sections on web accessibility testing and update the Themes handbook’s accessibility‑ready tag information by May 2026, and is considering a “Can I Use” section for core blocks to list accessibility status per block.

These updates reinforce WordPress’s commitment to inclusive design, providing developers with clearer, more actionable guidance and a streamlined process for ensuring that themes meet the highest accessibility standards. The changes are expected to raise the overall quality of WordPress themes and improve the user experience for people with disabilities.

Key changes

  • New docs on alt text, headings, links, and WCAG intro
  • Google Doc for feedback on slider, editor, controls
  • Call for speakers for WordPress Accessibility Day 2026 open
  • Updated schedule for WordPress 7.0 Release Party
  • 22 tickets milestoned for 7.1 release
  • Focus on visual revisions, client‑side media, tabs block in Gutenberg
  • Real‑time collaboration not yet tested for accessibility
  • Admin Font Library visual history updates

Affects

wp-customers enterprise

Source angles · 4 perspectives

Make WordPress Accessibility
Independent angle

Accessibility Team Meeting Notes: April 23, 2026

Open
Make WordPress Accessibility
Independent angle

WordPress Accessibility Documentation Updates – April 2026

Open
Make WordPress Accessibility
Independent angle

WordPress Updates Theme Accessibility‑Ready Guidelines Effective Today

Open
Make WordPress Themes
Independent angle

WordPress Updates Accessibility-Ready Theme Guidelines Effective June 30, 2026

Open

Customer impact

Analyzing matches…

Ask about this story

Impact on an agency? Which customers? Compare historically Risks of waiting