Accessibility Improvements in WordPress 7.1  🔗 **Source:** [Accessibility Improvements in WordPress 7.1](https://make.wordpress.org/core/2026/08/13/accessibility-improvements-in-wordpress-7-1/#comment-49155) > [!note]+ Document Notes > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > --- > tags: [wordpress-accessibility, wordpress-core, gutenberg, screen-readers, wcag, infinite-scroll] > author: [MISSING] > source: make.wordpress.org (Make WordPress Core) > reference: https://make.wordpress.org/core/2026/08/13/accessibility-improvements-in-wordpress-7-1/#comment-49155 > date created: 2026-08-13 22:25 > > --- > # 🏷️ Title: Accessibility Improvements in WordPress 7.1 <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Media library infinite scroll filter — `media_library_infinite_scrolling`](https://make.wordpress.org/core/2026/08/13/accessibility-improvements-in-wordpress-7-1/) - [WP Accessibility plugin](https://wordpress.org/plugins/wp-accessibility/) - [Trac #65775 — media library "load more" toggle](https://core.trac.wordpress.org/ticket/65775) - [Core Trac](https://core.trac.wordpress.org/) and [Gutenberg GitHub PRs](https://github.com/WordPress/gutenberg/) cited throughout the post (individual ticket/PR links preserved in Main Content below) ## 📝 Summary - **What happened.** WordPress 7.1's Core and Gutenberg/Editor teams shipped a combined 88 accessibility enhancements and bug fixes (45 in Core, 43 in the Editor) plus two new blocks — Tabs and Playlist — both accessibility-tested pre-release. Headline additions: a standardized accessible tooltips API, more predictable screen reader behavior, and broad labeling cleanup across the admin. - **Why it matters.** This is release-notes documentation of WordPress Core's ongoing WCAG 2.2 AA conformance work — the kind of granular, ticket-by-ticket accessibility labor that rarely gets attention outside the Accessibility team but directly affects screen reader users, keyboard-only users, and users in Windows High Contrast Mode across both wp-admin and the block editor. - **Key stakeholders.** WordPress Core and Accessibility contributor teams, Gutenberg/Editor contributors, screen reader and keyboard-only users, agencies/site builders relying on `media_library_infinite_scrolling` and similar filters, and the WP Accessibility plugin maintainers who shipped a compensating feature. - **Risks and tradeoffs.** The post itself flags a **known regression**: the media library's default interaction pattern is changing from a "load more" button to infinite scroll, which the post explicitly calls "a known inaccessible pattern." Mitigations exist (a User Profile toggle, a `false`-returning filter, and a WP Accessibility plugin feature that flips the default) but none of them are the default behavior — the inaccessible pattern ships as-is unless a site owner or user opts out. A parallel effort to add a toggle to the *existing* media library (#65775) did not reach consensus in time for 7.1. - **Bottom line.** Net accessibility gain for 7.1 (88 fixes, new tooltip API, two vetted blocks) is real, but it ships alongside one acknowledged step backward that individual users and site admins must proactively opt out of. ## 📖 Main Content WordPress 7.1 splits its accessibility work into two release trains that land together: **Core** (wp-admin, list tables, front-end templates) and **Editor** (Gutenberg — blocks, admin screens, admin components, Visual Revisions). **Core (45 fixes)** clusters into: Media (caption labeling, modal keyboard navigation, duplicate `figcaption` IDs, grid-view labeling, image editor width label, date-filter labeling, bulk-edit toolbar styling, focus indicator visibility), Classic Editor (KSES invoker-command support, `dialog` autofocus, Publish box and status-dropdown layout), List Tables (post-title cell as row header instead of the checkbox, subpage structural indicators for blind users, excerpt display for untitled posts), Labeling/Accessible Names (plural-form strings, Customizer preview icon labels, and the new **standardized accessible-tooltips mechanism** applied to metabox order buttons and the "Remember Me" login checkbox), Users (deletion guidance, login-page link identification, language switcher labels/icons, Add User screen no longer force-focusing the password field), Administration (admin color-scheme contrast, Windows High Contrast Mode support for buttons/tabs, tag-management and Quick Draft and Settings-API UI fixes, Site Editor toolbar visibility, a **2 CSS pixel minimum standard for focus indicators**, data-export-request labeling, admin bar/menu focus states, collapsed-menu cursor behavior, JS-failure fallback rendering for route-based admin pages, theme-browser navigation consistency, plugin-installer modal scrollbar visibility, and page-language exposure during setup/install), and Front-end (password-protected content styling, an RSS widget fix for multiple-instance accessibility conflicts, and a comment-reply-link fix for accidental touch triggers). **Editor (43 fixes)** clusters into: Editing Experience (template action preview keyboard activation, pattern-creation dialog focus retention, replacing localized `aria-live` regions with the `speak()` function for more reliable auditory feedback, `DataForm` panel tooltip labeling, block-movement keyboard-shortcut tooltips), visual/interaction fixes (color-picker cursor stability, relocating contrast warnings to prevent layout shift, extending advanced contrast checking to viewport and pseudo-states, preserving note selection across browser tabs, `word-break` support for screen-reader-only classes, and a spoken-message error fix during block insertion), Blocks (Breadcrumbs hiding decorative separators from assistive tech, full labels in the icon browser, an Image block toggle for marking media decorative, Cover block video-provider restrictions to prevent inaccessible embeds, removal of conflicting arrow/Home/End shortcuts in Accordion blocks, and a Stretchy Text block focus-loss fix), Admin Screens (removing centered text from Connectors, promoting Page component headers to `h1`, Font Library focus fixes, `NavigableRegion` labeling corrections), Admin Components (focus-trap fixes, `ValidatedRangeControl` label fixes, help-text association for `ComboboxControl`/`ToggleGroupControl`, `radiogroup` role for `RadioControl`, High Contrast Mode focus rings on Tab panels and `CollapsibleCard`, button-state fixes for disabled/loading/click-feedback states, `ContentEditableControl` label associations, Dialog focus priority favoring content over the close button, and standardized screen-reader text for `DataForm` card toggles), and Visual Revisions (contrast for difference-marker stripes, `title` → `aria-describedby` migration, autosave-specific labels, auto-focusing the revisions slider, non-color CSS-outline change indicators, pluralized revision-count labels, and an `aria-label` on the revisions trigger). **New blocks:** Playlist Block and Tabs Block, both accessibility-tested pre-ship, "although feedback is always welcome." **The regression:** 7.1 changes the media library's default load pattern from a "load more" button to infinite scroll — which the post itself names as "a known inaccessible pattern." Three compensating paths exist, none of them the shipped default: (1) an individual User Profile setting to turn it off, (2) the `media_library_infinite_scrolling` filter, which a site owner can hook to return `false` and disable it site-wide, and (3) a feature in the third-party **WP Accessibility plugin** that inverts the defa <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Accessibility Improvements in WordPress 7.1.md|Accessibility Improvements in WordPress 7.1 by make.wordpress.org]] ## Highlights - WordPress 7.1 continues to polish accessibility across WordPress Core and Gutenberg, advancing the goals to meet accessibility standards. In this release, high-impact changes include the new accessible tooltips API, improved predictability for screen readers, and improved labeling in many places in the admin. The editor ships with new Tab and Playlist blocks and extensive improvements to editor navigation and interaction. ([View Highlight](https://read.readwise.io/read/01kzz1nm560mqvv3nmp1pw7t6c)) - Note: Top-level summary claim for the release: 88 combined fixes plus a new accessible tooltips API. - Tags: xref, atom/literature/h1 - 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. ([View Highlight](https://read.readwise.io/read/01kzz1pj8btfr35srrnc4338qw)) - Note: The self-disclosed regression: shipped infinite scroll default despite naming it a known inaccessible pattern. Strongest atom in the piece. - Tags: atom/literature/h1, addendum