Applies to WordPress 7.0 and 7.1. Last verified: 2026-09-11, against WordPress 7.1.
Short answer: WordPress 7.0 and 7.1 shipped dozens of documented admin accessibility fixes, including post lists that screen readers now identify by post title, a default color scheme with higher contrast, focus outlines of at least 2 CSS pixels, and page transitions that stay off when your operating system asks for reduced motion. One change went the other way. In 7.1 the Media Library scrolls infinitely, a pattern WordPress itself calls inaccessible, and each user can switch it off at Users > Profile.
If the redesign made your daily work harder, you are not imagining it. WordPress's own accessibility team documents both the improvements and the regression. This page separates the two, then lists the settings you can change for yourself today.
One thing this page is not: a screen-reader test of your site. It reports what WordPress has documented for 7.0 and 7.1. Your theme and plugins add their own screens and can behave differently. None of the settings below touch your content, but if you end up deactivating plugins while you investigate a problem, back up first.
The standard WordPress admin accessibility is held to
WordPress.org's accessibility statement, last updated September 19, 2024 and read on September 11, 2026, sets the target: making "the WordPress Admin and bundled themes fully compliant with Web Content Accessibility Guidelines (WCAG) 2.2 AA, where possible," and requiring that all new and updated code released in WordPress conform to those guidelines. "Where possible" matters. It is a commitment to a standard, not a certificate that every screen meets it.
What 7.0 changed
Joe Dolson's Accessibility Improvements in WordPress 7.0 on Make WordPress Core, published May 23, 2026 and read on September 11, 2026, counts 24 accessibility enhancements and bug fixes in core, plus separate fixes in the editor and the bundled themes. The changes a site owner is most likely to notice:
- Contrast. Fixes for dashboard color contrast errors raised by automated tests, and for the zero-comments notice in the admin toolbar, which had insufficient contrast. The WordPress 7.0 Field Guide, also read on September 11, 2026, describes the new default Modern scheme as "boasting a refreshed color palette, higher contrast, and upgraded typography."
- Screen readers. List tables avoid redundant Edit links and reduce noise for screen readers, the dashboard no longer confuses the published post count with all posts, and the tabs inside taxonomy meta boxes are now identified programmatically.
- Voice control. The 7.0 accessibility post includes a fix for using speech recognition software with the Add Media panel.
- Alt text. Alternative text stored in a photo's IPTC metadata is now used to pre-fill the image's alt text field.
- Keyboard. DataViews, the system behind the new Posts and Pages screens, gained grid keyboard navigation, and the table view's selection checkbox is now permanently visible.
- Motion. The fade between admin pages uses View Transitions, and the Field Guide states that "View Transitions are only activated if a preference is not set for reduced motion on the OS level."
What 7.1 changed
The follow-up, Accessibility Improvements in WordPress 7.1 (published August 13, 2026, updated August 16, read on September 11, 2026), lists 44 fixes in core and 43 in the editor. On the Posts and Pages lists, the Make Core note on list table row headers, read the same day, explains that screen readers now "consistently refer to the name of the relevant post, rather than referring to a selection checkbox." The changes that affect daily use:
| Who it helps | What changed in 7.1 |
|---|---|
| Screen reader users on Posts and Pages | The row header moved from the checkbox column to the post title, so each row is announced by the post's name. |
| Keyboard users | Focus indicators standardized to at least 2 CSS pixels; admin bar and menu focus states improved. |
| Low vision and high contrast users | Admin color scheme contrast raised for the sidebar; active buttons and tabs now identified in Windows High Contrast Mode. |
| Anyone who relies on tooltips | A standard mechanism for accessible tooltips, now used in selected screens. |
| Editors | A toggle on the Image block to mark an image as decorative; Visual Revisions adds non-color indicators for changes; Font Library focus issues addressed. |
| Site visitors | The new Tabs and Playlist blocks were introduced with accessibility testing, according to the post. |
The regression: infinite scrolling in the Media Library
In 7.1, the Media Library grid loads more items as you scroll instead of offering a load-more button. The 7.1 accessibility post is direct about it: this is "a known inaccessible pattern." The usual objection to the pattern is that content keeps arriving, so it becomes hard to reach whatever comes after the list or to know where the list ends.
Each user can switch it off:
- Go to Users > Profile.
- Under the Infinite Scrolling personal option, check Disable infinite scrolling in the Media Library grid view.
- Select Update Profile.
A developer can also switch it off for the whole site with the media_library_infinite_scrolling filter, which, according to the Make Core dev note announcing the change on July 23, 2026, takes precedence over each user's preference. The rest of that release's media work is in the WordPress 7.1 Media Library changes.
WordPress admin accessibility settings you can change yourself
Every setting here is per user and changes nothing for anyone else on the site.
| If you need | Where | What to set |
|---|---|---|
| Less motion between admin pages | Your operating system's accessibility settings | Turn on reduced motion. WordPress then skips the page fade. |
| A different contrast balance | Users > Profile > Admin Color Scheme | Pick the scheme that reads best for you. |
| No infinite scroll in media | Users > Profile | Disable infinite scrolling in the Media Library grid view |
| Words instead of icons on editor toolbars | Editor three-dot menu > Preferences > Accessibility | Show button text labels |
| A text caret that stays inside the current block | Editor three-dot menu > Preferences > Accessibility | Contain text cursor inside block |
Changing the admin color scheme shows each scheme and how to switch back. The two editor preferences come from WordPress.org's Preferences overview, read on September 11, 2026, which describes "Contain text cursor inside block" as an option that "aids screen readers by stopping the text caret from leaving blocks." Its screenshots were last refreshed for an earlier release, so if a label reads slightly differently on your screen, trust your screen.
Keyboard navigation in the new admin
A few keys do most of the work, and all of them are listed in WordPress.org's block editor keyboard shortcuts documentation, read on September 11, 2026:
- Move between regions of the editor: Shift+Alt+N for the next region and Shift+Alt+P for the previous one on Windows; Ctrl+Option+N and Ctrl+Option+P on a Mac. Ctrl+` also moves to the next region.
- Jump to the nearest toolbar: Alt+F10 on Windows, Option+F10 on a Mac.
- See every shortcut: Shift+Alt+H on Windows, Ctrl+Option+H on a Mac.
- Get anywhere in the admin by typing: Ctrl+K on Windows or Cmd+K on a Mac opens the command palette, which the 7.0 Field Guide describes as reachable from anywhere in the dashboard. For a keyboard user it is often quicker than working down the menu.
If something is still harder than before
First, find out whether WordPress is the cause. Admin plugins add their own screens, menus and scripts, and a problem that looks like the redesign may belong to one of them. A ten-minute plugin conflict test on a copy of your site tells you which.
If it is WordPress, tell the people who can fix it. The Make WordPress Accessibility team site, read on September 11, 2026, points to the #accessibility channel on the Make WordPress Slack (registration required) and to its handbook for how to contribute. Describe the screen, the assistive technology and browser you use, the steps, and what you expected to happen. Both 7.x accessibility posts include fixes for tickets that had been open for years, so reports do lead to changes.
For a broader tour of the redesigned screens, the task-by-task walkthrough of the new admin covers the everyday tasks with the same menu paths.
FAQ
Is the WordPress admin accessible to screen reader users after 7.0?
WordPress targets WCAG 2.2 AA "where possible," and 7.0 and 7.1 together documented dozens of fixes, including list tables announced by post title in 7.1. WordPress also documents a known regression, infinite scrolling in the Media Library, which you can disable for your own account. Plugins can add screens that behave differently.
How do I stop the fade animation between admin pages?
Turn on reduced motion in your operating system's accessibility settings. The 7.0 Field Guide states that View Transitions only run when no reduced-motion preference is set.
How do I turn off infinite scrolling in the Media Library?
Go to Users > Profile, check Disable infinite scrolling in the Media Library grid view, and update your profile. It applies only to your account.
Where do I report an accessibility problem in WordPress?
Through the Make WordPress Accessibility team, including the #accessibility channel on the Make WordPress Slack. Rule out plugins first so the report describes WordPress itself.
Version context. Written against WordPress 7.1, released August 19, 2026, and confirmed as the current release on the WordPress.org release archive on September 11, 2026. Every change listed here comes from WordPress's own documentation: the 7.0 and 7.1 accessibility posts by Joe Dolson on Make WordPress Core, the WordPress 7.0 Field Guide, the Make Core dev notes on list table row headers and on Media Library infinite scrolling, WordPress.org's accessibility statement, its Preferences overview, its Your Profile screen documentation and its block editor keyboard shortcuts page, all read on September 11, 2026. This page describes documented behavior and is not a test report of any assistive technology. Review trigger: the next major WordPress release or the next accessibility improvements post on Make WordPress Core.
