This issue that’s being fixed has been an open bug for eleven years but WordPress core contributors finally closed it nine days ago
The problem it solves is that the row header should have a semantic label. Screen readers read each row using the checkbox text instead of the post title. Locked posts made this worse. When a post is locked, the lock icon has no label a screen reader can announce. So instead of hearing the post title, users heard the column header, “Select All,” a phrase that says nothing about the post in front of them.
One of the edge cases that the core trac ticket described mentioned how a “Select All” label creates a problem for WordPress users with screen readers because it does not describe what that column header is about.
“In all the List Tables in the admin, the “Select %s” (where %s is the name of the Post, Attachment, Plugin, User, etc,) is used as row header:
What Should Plugin Users Do?
Plugins that use CSS or JavaScript to target specific
You may be affected if you use a plugin that adds information or controls to WordPress admin post lists and relies on the existing
Review that plugin’s changelog once WordPress 7.1 rolls out. To do that, just Google the name of the plugin plus the keyword “changelog” in order to find the log of changes made to the plugin as well as information about compatibility. Most plugins test for compatibility. If the plugin is marked as compatible, update it before installing WordPress 7.1. If compatibility has not been confirmed, use a staging site to test whether the plugin breaks the WordPress 7.1 admin post list.
The three most popular SEO plugins, Yoast SEO, Rank Math, and All in One SEO, have functionality related to the admin post list, but they are unlikely to break. A review of their publicly available code found no selectors that appear to rely on the
Even if a plugin breaks with WordPress 7.1, the change is unlikely to be an issue on the public-facing side of the website.
What Should Plugin Developers Do?
WordPress software developers should already know to audit their software for changes. But there are many people nowadays who are vibe coding their own plugins so it’s important for non-developers who rely on AI to code their plugins to also audit any CSS or JavaScript selectors that specifically target
The official WordPress announcement offered the following before and after examples of how the code will change:
Code Before Change
Hello world! admin The
this in the first column, followed by atdwith the column title.Code After Change
Hello world! admin
The checkbox cell is changing from a
Featured Image by Shutterstock/Konstantin Kolosov
Roger Montti
Owner – Martinibuster.com at Martinibuster.com
I have 25 years hands-on experience in SEO, evolving along with the search engines by keeping up with the latest …