{"id":125420,"date":"2026-08-13T16:43:29","date_gmt":"2026-08-13T16:43:29","guid":{"rendered":"https:\/\/make.wordpress.org\/core\/?p=125420"},"modified":"2026-08-16T16:29:58","modified_gmt":"2026-08-16T16:29:58","slug":"accessibility-improvements-in-wordpress-7-1","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/core\/2026\/08\/13\/accessibility-improvements-in-wordpress-7-1\/","title":{"rendered":"Accessibility Improvements in WordPress 7.1"},"content":{"rendered":"

WordPress 7.1 continues to polish accessibilityAccessibility<\/span> Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both \u201cdirect access\u201d (i.e. unassisted) and \u201cindirect access\u201d meaning compatibility with a person\u2019s assistive technology (for example, computer screen readers). (https:\/\/en.wikipedia.org\/wiki\/Accessibility)<\/span><\/span><\/span> across WordPress CoreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> and GutenbergGutenberg<\/span> The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses \u2018blocks\u2019 to add richness rather than shortcodes, custom HTML etc.\rhttps:\/\/wordpress.org\/gutenberg\/<\/a><\/span><\/span><\/span>, advancing the goals to meet accessibility standards. In this release, high-impact changes include the new accessible tooltips APIAPI<\/span> An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.<\/span><\/span><\/span>, improved predictability for screen readers, and improved labeling in many places in the adminadmin<\/span> (and super admin)<\/span><\/span><\/span>. The editor ships with new Tab and Playlist blocks and extensive improvements to editor navigation and interaction.<\/p>\n\n\n\n

Core<\/h2>\n\n\n\n

Enhancements to WordPress core include 44 accessibility enhancements and bugbug<\/span> A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.<\/span><\/span><\/span> fixes<\/strong>. Major changes include enhancements to focus states, improvements to screen reader support in post list tables, and the introduction of a tooltip mechanism for exposing accessible names in WordPress core.<\/p>\n\n\n\n

Media<\/h3>\n\n\n\n

WordPress 7.1 delivers an enhanced media experience including refined labels for caption fields to provide clearer usage guidance (#43178<\/a>). Navigation within theme and media modals was adjusted to prevent single-key arrow interactions from conflicting with screen reader patterns (#63760<\/a>). Technical fixes address duplicate ID elements in figcaption<\/code> elements when reusing images (#65315<\/a>) and ensure accurate visible labeling for untitled items in the grid view (#65438<\/a>). In the image editor, the width input label was corrected (#65685<\/a>). Improvements to the Media grid include resolving unlabeled date filters (#65711<\/a>), styling fixes for bulk editing toolbars (#65732<\/a>), and ensuring focus indicators remain fully visible (#65755<\/a>).<\/p>\n\n\n\n

Classic Editor<\/h3>\n\n\n\n

The editing environment is landing with architectural improvements, such as support for invoker command attributes in KSES (#64576<\/a>) and the autofocus<\/code> attribute for dialog<\/code> elements (#65491<\/a>). Classic editor users will benefit from layout enhancements to the Publish box visibility controls (#65530<\/a>) and status dropdown menus (#65532<\/a>).<\/p>\n\n\n\n

List Tables<\/h3>\n\n\n\n

List table structures were updated to identify the post title cell as the row headerHeader<\/span> The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor\u2019s opinion about your content and you\/ your organization\u2019s brand. It may also look different on different screen sizes.<\/span><\/span><\/span> instead of the selection checkboxes (#32892<\/a>, #65743<\/a>). To assist blind users, subpages in page lists now include proper structural indicators (#64932<\/a>), while untitled posts can display an excerptExcerpt<\/span> An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin\u2019s metabox.<\/span><\/span><\/span> of the content in post lists (#65022<\/a>).<\/p>\n\n\n\n

Labeling and Accessible Names<\/h3>\n\n\n\n

Work continues on semantic clarity, addressing missing plural forms for specific strings (#29299<\/a>) and adding necessary visible text to responsive preview icons in the CustomizerCustomizer<\/span> Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site\u2019s appearance settings.<\/span><\/span><\/span> (#36447<\/a>). Core now includes a standardized mechanism for accessible tooltips (#51006<\/a>), which has been applied to metaboxMetabox<\/span> A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way.<\/span><\/span><\/span> order buttons (#50921<\/a>) and the \u201cRemember Me\u201d login option (#55343<\/a>).<\/p>\n\n\n\n

Users<\/h3>\n\n\n\n

The user management flow was improved with better guidance during user deletion (#56914<\/a>) and clearer identification of links on the login page (#65075<\/a>). The language switcher now consistently employs visible labels and icons (#65464<\/a>), and the \u201cAdd User\u201d screen no longer forces initial focus onto the password field (#65630<\/a>).<\/p>\n\n\n\n

Administration<\/h3>\n\n\n\n

Administrative improvements focus on high contrast and consistency. Contrast in admin color schemes was boosted for sidebarSidebar<\/span> A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.<\/span><\/span><\/span> compatibility with the blockBlock<\/span> Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.<\/span><\/span><\/span> editor (#65382<\/a>), and active states for buttons and tabs are now properly identified in Windows High Contrast Mode (#65153<\/a>, #65419<\/a>). UIUI<\/span> User interface<\/span><\/span><\/span> inconsistencies during tagtag<\/span> A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)<\/span><\/span><\/span> management (#63372<\/a>), Quick Draft error handling (#64952<\/a>), and Settings API section titles (#65027<\/a>) have been resolved. Further enhancements include toolbar visibility in the Site Editor (#65091<\/a>), standardized focus indicators of at least 2 CSSCSS<\/span> Cascading Style Sheets.<\/span><\/span><\/span> pixels (#65645<\/a>), and labeling improvements for data export requests (#65246<\/a>).<\/p>\n\n\n\n

Focus states on the admin bar and the admin menu have been improved (#65765<\/a>, #65726<\/a>), enhancing the usability of the now-universal toolbar. Mouse cursor interaction inconsistencies when the admin menu is collapsed have been fixed (#65250<\/a>). Route-based admin pages now all render appropriate feedback when JavaScriptJavaScript<\/span> JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user\u2019s browser.\rhttps:\/\/www.javascript.com<\/a><\/span><\/span><\/span> rendering is not available or fails (#65690<\/a>).<\/p>\n\n\n\n

The theme browser now has consistent navigation behavior when navigating from the first theme (#65715<\/a>), and the scrollbar is no longer partially hidden in the pluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span> installer modal (#65334<\/a>). When performing setup or installation, the language of the page is made available (#65454<\/a>).<\/p>\n\n\n\n

Front-end<\/h3>\n\n\n\n

On the front end, password-protected content receives styling and usability upgrades (#64569<\/a>). The RSS widgetWidget<\/span> A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.<\/span><\/span><\/span> was updated to prevent accessibility issues when multiple instances are present (#47670<\/a>), and the comment reply link no longer triggers unexpectedly on touch interactions (#46713<\/a>).<\/p>\n\n\n\n

Editor<\/h2>\n\n\n\n

The editor includes 43 accessibility enhancements and bug fixes<\/strong> covering screen reader, forced colors, and keyboard navigation improvements, as well as shipping two new front-end blocks for post content. The editor changes in 7.1 greatly improve consistency on a number of fundamental components that should lead to a better experience for all.<\/p>\n\n\n\n

Editing Experience<\/h3>\n\n\n\n

Refinements to the editing interface include fixing keyboard activation for template action previews (#78641<\/a>) and resolving focus loss issues when dismissing the pattern creation dialog (#78957<\/a>). Localized aria-live<\/code> regions were replaced with the more robust speak()<\/code> function to improve auditory feedback (#79600<\/a>). The DataForm<\/code> panel layout now correctly exposes accessible names via tooltips on edit buttons (#77024<\/a>), and tooltips now also display keyboard shortcuts for block movement (#76992<\/a>).\u00a0<\/p>\n\n\n\n

Visual and interaction fixes address cursor instability in the color picker (#80205<\/a>) and prevent layout shifts by relocating contrast warnings within the color popover (#79512<\/a>). Advanced contrast checking now extends to viewport and pseudo-states (#80223<\/a>), while note selections are now preserved across browser tab transitions (#75955<\/a>).<\/p>\n\n\n\n

Additional refinements include adding word-break<\/code> support to screen reader classes (#75539<\/a>) to prevent inconsistencies, and an error in spoken messages announced during block insertion was fixed (#79004<\/a>).<\/p>\n\n\n\n

Blocks<\/h3>\n\n\n\n

Block-level improvements focus on semantic accuracy and control. The Breadcrumbs block now hides decorative separators from assistive technologyAssistive technology<\/span> Assistive technology<\/b> is an umbrella term<\/a> that includes assistive, adaptive, and rehabilitative devices for people with disabilities<\/a> and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the\u00a0technology<\/a> needed to accomplish such tasks.\r\rhttps:\/\/en.wikipedia.org\/wiki\/Assistive_technology<\/a><\/span><\/span><\/span> (#78524<\/a>), while the icon browser provides full labels for better identification (#80256<\/a>). The Image block introduces a dedicated toggle for marking media as decorative (#78064<\/a>), and the Cover block gains attributes to restrict video providers, helping prevent inaccessible embeds (#80092<\/a>).\u00a0<\/p>\n\n\n\n

In Accordion blocks, navigation shortcuts using arrows and the \u201chome\u201d and \u201cend\u201d keys were removed (#75891<\/a>) due to conflicting behaviors, and a focus loss in settings was fixed in the Stretchy Text block (#75092<\/a>).<\/p>\n\n\n\n

Admin Screens<\/h3>\n\n\n\n

Updates to admin screens emphasize readability and standard compliance. Centered text is removed from Connectors to improve scanning (#78125<\/a>), and Page component headers are promoted to h1<\/code> by default to align with core semantic structures (#77617<\/a>). Focus issues in the Font Library (#78671<\/a>) and labeling mismatches in the NavigableRegion<\/code> (#75899<\/a>) have been addressed.<\/p>\n\n\n\n

Admin Components<\/h3>\n\n\n\n

The component library received numerous technical fixes. Focus traps broken by specific display properties were resolved (#77381<\/a>), and invalidinvalid<\/span> A resolution on the bug tracker (and generally common in software development, sometimes also notabug<\/em>) that indicates the ticket is not a bug, is a support request, or is generally invalid.<\/span><\/span><\/span> object-based labels in ValidatedRangeControl<\/code> were corrected (#77042<\/a>). Help text associations were improved for ComboboxControl<\/code> (#76761<\/a>) and ToggleGroupControl<\/code> (#76740<\/a>). RadioControl<\/code> fieldsets now properly employ the radiogroup<\/code> role (#76745<\/a>).<\/p>\n\n\n\n

For users in High Contrast mode, focus rings are now consistently rendered on Tab panels and CollapsibleCard<\/code> headers (#77469<\/a>, #77468<\/a>).\u00a0<\/p>\n\n\n\n

Button states were also refined, addressing focusable defaults when disabled (#78526<\/a>), loading indicator visibility in forced colors (#78820<\/a>), and click feedback styling (#76833<\/a>). Furthermore, label associations in ContentEditableControl<\/code> were fixed (#80344<\/a>), Dialog components now prioritize focusing content over the close button (#76910<\/a>), and screen reader text for DataForm<\/code> card toggles was standardized (#76039<\/a>).<\/p>\n\n\n\n

Visual RevisionsRevisions<\/span> The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next\/Previous buttons). The display indicates what has changed in each revision.<\/span><\/span><\/span><\/h3>\n\n\n\n

The Visual Revisions experience received significant updates. Contrast for difference position marker stripes was increased (#78473<\/a>), and title<\/code> attributes were replaced with aria-describedby<\/code> for better annotation support (#80440<\/a>). The timeline now includes specific labels for autosaves (#79950<\/a>). Navigation was improved by auto-focusing the revisions slider (#79691<\/a>) when the editor is activated.<\/p>\n\n\n\n

Non-color indicators were added using CSS outlines as secondary indicators for document changes (#78393<\/a>), and proper pluralization for revision count labels (#78382<\/a>) was added. The Post Summary sidebar now includes an aria-label<\/code> for the revisions trigger (#78140<\/a>) to provide better context for screen reader users.<\/p>\n\n\n\n

New blocks<\/h3>\n\n\n\n

WordPress introduces new interactive elements, including a Playlist Block (#80203<\/a>) and a Tabs Block (#80163<\/a>). Both blocks have been tested for accessibility concerns, although feedback is always welcome.<\/p>\n\n\n\n

Known Accessibility Regressionregression<\/span> A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers<\/a>. Recent regressions may be given higher priorities. A \"3.6 regression\" would be a bug in 3.6 that worked as intended in 3.5.<\/span><\/span><\/span><\/h2>\n\n\n\n

In WordPress 7.1, the default behavior of the media library is being changed from including a load more button to having infinite scroll, a known inaccessible pattern.\u00a0<\/p>\n\n\n\n

To compensate for this, there is an option in the User Profile allowing individual users to turn it off. You can also use the existing filter media_library_infinite_scrolling<\/code> to disable it by default<\/a>, returning the value false<\/code>.<\/p>\n\n\n\n

A feature has been added in the WP Accessibility plugin<\/a> that inverts the logic, switching the default value to \u2018false\u2019 and altering the User Profile option to allow users to turn it on.<\/p>\n\n\n\n

You can also try the Gutenberg Experiment to replace the media library. This feature is still in development, and has not had a full accessibility review. The infinite scroll in the updated media library will be governed by an in-modal toggle, and is not currently enabled.<\/p>\n\n\n\n

There is also work continuing to try to add a similar toggle to the existing media library in #65775<\/a>. That work is progressing, but the implementation did not reach consensus in time to land in WordPress 7.1<\/p>\n\n\n\n

Reviewed by <\/em>@<\/span>annezazu<\/a>, @<\/span>amykamala<\/a>, @<\/span>sabernhardt<\/a><\/p>\n

#<\/span>7-1<\/a>, #<\/span>accessibility<\/a>, #<\/span>dev-notes<\/a>, #<\/span>dev-notes-7-1<\/a><\/p>