The WordPress Accessibility Team has its first shot at an official plugin, and this time the team itself is behind it.
What happened
Automattic contributor Anne McCarthy published a prototype called the Accessibility Lab plugin, posting it to GitHub on August 21 with backing from the WordPress Accessibility Team. According to the announcement on the Make WordPress Accessibility blog, the prototype bundles three tools: view options for the Media Library, real-time validation that warns editors when a heading level skips a step, and a block accessibility checker contributed by developer Troy Chaplin from his existing Block Accessibility Checks plugin. That checker runs real-time WCAG (Web Content Accessibility Guidelines) validation on blocks, and third-party blocks get checked too.
McCarthy was direct about what the plugin is not: “This is not ‘install this plugin to have accessibility needs met’ or ‘to make WordPress accessible.’ That approach causes real harm,” McCarthy wrote. “The Accessibility Lab plugin is not a substitute for fixing accessibility in Core. It is a place to test new ideas, gather feedback, and develop features that need real-world testing before they are ready for Core.”
The plugin is still a prototype. It lives on McCarthy’s personal GitHub account for now, and the team plans to move it into the official WordPress.org plugin directory once it’s ready. When it does, it becomes the third canonical plugin maintained by a WordPress Make team, following the Performance Team’s Performance Lab plugin and the AI Team’s AI plugin.
Why this is a change from before
Two weeks ago, WPWithin reported that Matt Mullenweg had called a separate WordPress Accessibility Team initiative “permanently delayed” and accused the team of overstepping its authority. That fight was about theme review standards, not a plugin, but it left theme authors and accessibility advocates unsure how much authority the Accessibility Team still had.
This time is different. The Accessibility Lab plugin has the team’s own buy-in from the start, and core committer Joe Dolson, who pushed back hard on Mullenweg in the earlier dispute, has given this concept conditional support, provided its features have a real path into WordPress core and the plugin doesn’t get used to override core decisions.
What this means for your site
There’s nothing to install today. The plugin isn’t in the WordPress.org directory yet, so this doesn’t change anything on your site right now. What it signals is useful anyway: WordPress is building real tooling to catch common accessibility mistakes, like a blog post that skips from an H2 heading straight to an H4, before they go live. Skipped heading levels confuse screen reader users and are a common target in accessibility lawsuits, so a feature that warns editors in real time is worth watching for a future release.
McCarthy also flagged what could come next: making image alt text searchable. Right now alt text lives in a database field that can’t be searched at scale, so a site with thousands of images has no easy way to find which ones are missing alt text. That’s the kind of practical fix this plugin is meant to test before it reaches WordPress core.
End of article