Accessibility Team Meeting Notes – WordPress 7.0 RC3 & Updated Accessibility‑Ready Requirements
Patch your theme to include the updated accessibility‑ready metadata and run the accessibility test suite against WordPress 7.0 RC3 to ensure compliance.
Patch your theme to include the updated accessibility‑ready metadata and run the accessibility test suite against WordPress 7.0 RC3 to ensure compliance.
Summary
The Accessibility Team held its bi‑weekly meeting on Thursday, sharing key updates for WordPress 7.0 and the accessibility ecosystem. The Global Accessibility Awareness Day 2026 event was highlighted, and the Accessibility‑Ready Requirements were officially updated, adding new criteria that theme developers must meet. WordPress 7.0 RC3 (“new Beta 1”) was released on May 8th, bringing a suite of accessibility fixes to core and Gutenberg.
The meeting also covered documentation updates on wpaccessibility.org, including new testing guidance and cross‑linked internal resources. Work on the 7.0 release is progressing, but uncertainty around the 7.1 cycle means new feature work will pause in favor of milestone issues. Gutenberg accessibility issues identified by @joedolson are being addressed, with several critical fixes slated for 7.0. Themes are urged to adopt the updated accessibility‑ready metadata immediately.
A discussion on automated contribution tracking for the Five for the Future (FFTF) initiative was introduced, aiming to shift from self‑reported hours to measurable data such as commits, PRs, and ticket participation. The team emphasized that the initiative will not alter contributor participation but will better represent existing contributions. No immediate action items were assigned, but the topic may appear in future agendas.
Key changes
- Accessibility‑Ready Requirements updated with new criteria for theme support
- WordPress 7.0 RC3 (“new Beta 1”) released May 8th, adding core and Gutenberg accessibility fixes
- wpaccessibility.org documentation updated with testing guidance and internal resource links
- Gutenberg accessibility issues prioritized; several critical fixes will ship in 7.0
- Themes must adopt the updated accessibility‑ready metadata immediately
- Automated contribution tracking introduced for the FFTF initiative, shifting to measurable data
- Uncertainty around the 7.1 cycle will delay new feature work, focusing on milestone issues