# WordPress 7.1 Accessibility Change May Break Some Plugins > [!info] Ported from an existing deep-read (Refactor Appendix present). This is secondary trade-press coverage of the same Trac #32892 change already covered in [[3. Resources/Literature Notes/Post List Tables Row Headers Changed (WordPress 7.1)]] — kept as a separate note because it adds distinct framing (eleven-year timeline, vibe-coding risk, an SEO-plugin spot check) that the primary dev note doesn't carry. > [!question] Lingering Questions > - Does the same row-header fix land for the plugins/users/attachments list tables, or only posts? Trac #32892's own reasoning covers all of them; the article only discusses posts. > - How many directory plugins actually target `th`/`td` in admin list tables? Mechanically answerable via a directory-wide grep; nobody has run it. > - Do AI-generated ("vibe-coded") plugins break at a measurably higher rate on 7.1 than hand-written ones? 19 August is the first real test of this. > [!tip] Article Ideas > - "The article measures the cost and skips the benefit" — a pattern-piece using this as one example: accessibility coverage that describes the broken screen-reader experience vividly ("Select All" repeated) but never describes the fixed one concretely. > - Directory-wide scan for `th`/`td` list-table selectors, run before a similar future Core change ships, to quantify blast radius pre-release instead of post-release. > [!link] Cross Reference > - [[3. Resources/Literature Notes/Post List Tables Row Headers Changed (WordPress 7.1)]] — the primary Core dev note this article reports on > - [[3. Resources/Permanent Notes/Semantic Identities Outlast Structural Selectors]] — already captures this article's dual-markup-support claim from the primary-source note > - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — the eleven-year-open-ticket data point as a concrete instance of that general pattern > [!quote] Vocabulary > - **row header** — the `<th scope="row">` cell that names a table row for assistive technology; moved here from the checkbox column to the post-title column > - **vibe coding** — building software (here, WordPress plugins) via AI generation without the author necessarily being able to read the resulting code ## Bibliographic capsule Search Engine Journal, ~920-word news piece, published 2026-08-06, reporting on WordPress 7.1 (shipped 2026-08-19) and Trac ticket #32892. Written for an SEO-practitioner audience; category: article. ## Author's thesis (as synthesized) WordPress 7.1's admin-table accessibility fix is correct and well-scoped, but it's a genuine breaking change for plugin/admin-customization code targeting the old markup — and a newly relevant population of non-developer "vibe coders" needs different upgrade guidance than developers do, because they can't read the selectors they'd need to audit. ## Key arguments (≤3) 1. **The defect and the fix**: admin post-list tables used the selection checkbox as the row header, so screen readers announced "Select All" instead of the post title — worst on locked posts, where the lock icon had no announceable label at all. 7.1 moves the row-header role to the title cell with an `aria-label`. 2. **The breaking-change disclosure is honest and scoped**: public-facing themes are unaffected; plugins/admin customizations targeting `<th>`/`<td>` in admin list tables are at risk. The recommended mitigation is supporting both old and new markup shapes simultaneously, since plugins must support multiple WordPress versions. 3. **The vibe-coding caveat is the article's most original point**: people shipping AI-generated plugins they can't necessarily read need to be told explicitly to audit CSS/JS selectors, because they can't self-diagnose the way a developer would. ## Claim atoms ### An eleven-year-old accessibility ticket just closed Where/why: Trac #32892 was reported roughly eleven years before this fix shipped. A diagnosed defect with an agreed-on solution sitting unresolved that long is a prioritization outcome, not an accident — a concrete instance of "unglamorous maintenance work goes chronically under-resourced." ### Non-developers who vibe-code plugins need explicit selector-audit guidance > [!quote] ID: rw_01kze95dz84v399k2vvezh1m0s > "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" Where/why: identifies a maintainer class that ships code it didn't write and can't necessarily read, and therefore can't self-diagnose against an upstream breaking change the way a developer auditing their own selectors would. ### The article measures the cost precisely and leaves the benefit abstract Where/why: the broken screen-reader experience is described vividly (rows announced as "Select All," worse for locked posts); the corrected experience is never described concretely — just "improves accessibility." A structural pattern in accessibility coverage generally, flagged in the deep-read's logical-validity section as an omission of the counterfactual benefit. ## Permanent candidates - **Maintainers of AI-generated code can't audit their own breaking-change exposure** — new and distinct from the vibe-coded-demo-vs-product claims already in the vault (those are about production-readiness; this is specifically about self-diagnosis capability during upstream changes). Promoted below. - The dual-markup-support and eleven-year-ticket claims are already captured by existing Permanents ([[3. Resources/Permanent Notes/Semantic Identities Outlast Structural Selectors]], [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]]) — connected rather than duplicated. ## Processing checklist - [x] Checked for an existing Literature Note on this exact doc (none found) and for the related primary-source note (found, cross-referenced) - [x] Checked existing Permanents before creating new ones — reused two, created one - [x] Connected into [[3. Resources/MOCs/Open Source Governance MOC]] ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — plugin-ecosystem compatibility cost from a Core accessibility fix, and the new AI-generated-code maintainer class this cost now reaches - [[3. Resources/Readwise/Articles/WordPress 7.1 Accessibility Change May Break Some Plugins]] — source article