WordPress 7.1 is shaping up as a useful accessibility release, but not a simple victory lap. The Make WordPress Core post lists 45 accessibility enhancements and bug fixes in Core and 43 in the editor, covering focus states, screen reader behavior, labels, forced colors, keyboard navigation, admin components, and block interactions.
The catch is in the Media Library. WordPress 7.1 changes the default behavior from a load more button to infinite scroll, which the source itself describes as a known inaccessible pattern. That makes this update less of a casual click-and-forget upgrade for accessibility-sensitive sites.
Key Takeaways
- WordPress 7.1 brings 45 Core accessibility fixes and 43 editor accessibility fixes.
- Media Library infinite scroll becomes the practical item to check before rollout.
- Sites with accessibility duties should decide whether to disable infinite scroll before production.
- Test admin, editor, Media Library, list tables, and user-management workflows on staging.
- New Tabs and Playlist blocks still need review in the actual theme and content context.
What WordPress 7.1 improves
The Core changes touch places site teams use every day: post list tables, media screens, the Classic Editor, user management, admin navigation, login flows, settings screens, and front-end elements such as password-protected content and comment reply behavior.
Important fixes include better focus states, improved screen reader support in post list tables, clearer labels in media and admin screens, and a standardized accessible tooltip mechanism. In plain owner language: this is not just polish for edge cases. It affects whether real people can move through the dashboard without fighting the interface.
The editor gets a broad accessibility pass
The block editor also receives a substantial accessibility update. The source says WordPress 7.1 includes 43 editor accessibility enhancements and bug fixes across screen reader feedback, forced colors, keyboard navigation, Visual Revisions, admin components, and block-level controls.
Some of the more practical changes involve focus handling, clearer labels, better help text associations, contrast improvements, and more predictable spoken feedback. These are the kinds of changes that rarely make flashy screenshots, which is probably why they matter: they reduce daily friction for editors who use keyboards, screen readers, or high contrast modes.
Media Library: the item not to ignore
The most important operational point is the Media Library regression. WordPress 7.1 changes the default Media Library behavior from a load more button to infinite scroll. The source calls infinite scroll a known inaccessible pattern.
That does not mean every site should panic. It does mean teams with accessibility obligations should not discover this after production deployment, ideally while an editor is trying to find an image under deadline. The blast radius is specific: media-heavy editorial teams, WooCommerce stores with product images, public-sector sites, education, NGOs, and any organization where accessibility is not optional paperwork.
How to reduce risk before updating
For accessibility-sensitive sites, treat WordPress 7.1 as a staging-first update. Test the editor, Media Library, post list tables, user management, admin navigation, and any custom publishing workflows before pushing it live.
- Ask keyboard-only and screen reader users to check Media Library behavior if you have access to them.
- Decide whether individual users should turn infinite scroll off in their User Profile.
- For stricter environments, consider disabling Media Library infinite scroll by default with the existing media_library_infinite_scrolling filter returning false.
- Document the choice so the next support ticket is not a scavenger hunt.
New Tabs and Playlist blocks need real-context testing
WordPress 7.1 also introduces new Tabs and Playlist blocks. The source says both have been tested for accessibility concerns, with feedback still welcome.
That is encouraging, but production sites should still test them inside the actual theme, layout, and content pattern where they will be used. Tabs in particular can become confusing fast if headings, labels, focus order, or mobile behavior are poor. A block can be sound in Core and still become awkward once a theme, plugin stack, and content team get involved. WordPress, as usual, is a team sport whether anyone asked for that or not.
Who should pay special attention
This update matters most for site owners and agencies maintaining sites where accessibility affects compliance, publishing work, or customer experience. That includes public-sector organizations, schools, universities, NGOs, healthcare and service businesses, and WooCommerce stores with large media libraries.
The WP-Dude judgment: WordPress 7.1 looks like a net accessibility improvement, but the Media Library default deserves a deliberate decision. Update, yes – but for serious sites, do it through staging and choose your infinite scroll policy before the production button gets involved.
Read the Make WordPress Core accessibility notes.
Frequently Asked Questions
Does WordPress 7.1 fix accessibility issues or introduce new ones?
Both. WordPress 7.1 includes 45 Core accessibility enhancements and bug fixes plus 43 editor accessibility enhancements and bug fixes. However, it also changes the Media Library default from a load more button to infinite scroll, which the source describes as a known inaccessible pattern.
Why is Media Library infinite scroll a concern in WordPress 7.1?
Infinite scroll can make it harder for some users to keep context, navigate predictably, or reach content with keyboard and assistive technologies. In WordPress 7.1, the practical concern is that this behavior becomes the default in the Media Library, so accessibility-sensitive sites should test it before production rollout.
How can a site disable Media Library infinite scroll in WordPress 7.1?
The source says users can turn it off in their User Profile. Site operators can also disable it by default with the existing media_library_infinite_scrolling filter returning false.
Are the new Tabs and Playlist blocks accessibility-ready?
The source says the new Tabs and Playlist blocks have been tested for accessibility concerns, with feedback still welcome. Site teams should still test them in their actual theme, layout, and content context before relying on them in production.
What should agencies and site owners test before updating to WordPress 7.1?
Test the editor, Media Library, post list tables, admin navigation, user management screens, and any custom publishing workflows on staging. For sites with accessibility requirements, decide before launch whether Media Library infinite scroll should remain enabled or be disabled by default.