Issues Explorer Rescans and Better Builder Support  🔗 **Source:** [Issues Explorer Rescans and Better Builder Support](https://www.youtube.com/watch?v=dZPQX-2yt84) > [!note]+ Document Notes > tags: [wordpress-accessibility, accessibility-checker, page-builders, automated-scanning, plugin-changelog, meeting-minutes] > author: Steve Jones & William Patton (Equalize Digital) > source: Equalize Digital (YouTube) > reference: https://www.youtube.com/watch?v=dZPQX-2yt84 > date created: 2026-09-25 08:58 > > > [!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. > > # 🏷️ Title: Issues Explorer Rescans and Better Builder Support > <!-- 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) - [🔄 Refactor appendix](#-refactor-appendix--issues-explorer-rescans-and-better-builder-support) ## 📝 Summary - **What happened.** Equalize Digital streamed its Accessibility Checker changelog show on 2026-09-24, 1:04:48 long, with Steve Jones (CTO) and William Patton (Senior Developer). The stream covers a grab-bag of shipped changes across Accessibility Checker Free, Accessibility Checker Pro, and the newer BoardScribe meeting-minutes plugin, plus a preview of BoardScribe Pro. This is first-party product content: the people who wrote the code describe it, and the stream closes with a request for five-star reviews on WordPress.org (01:03:02). No third-party voice appears. - **The claim.** Accessibility Checker now works better inside page builders and lets you re-verify fixes without leaving the Issues Explorer. Concretely: per-issue "Rescan page" in Pro's Issues Explorer (00:09:48), Elementor save/publish now triggers a rescan (00:19:13), a two-color highlighter outline that passes contrast on any background (00:24:21), a Simplified Summary block and shortcode in Free 1.49.0 (00:28:42), six scanner-accuracy fixes (00:36:01), new-window-warning re-application after Ajax rerenders (00:43:20), and BoardScribe 1.1.0's CSV import (00:45:32). - **The mechanism.** The through-line is rerender awareness. The scanner previously took one snapshot of a page at load or save time. Builders (Elementor, Oxygen, Divi), Ajax form plugins (Gravity Forms multi-page), and faceted search (FacetWP) all change the DOM after that snapshot. The fixes hook into each tool's own save or rerender event, or expose a callable method so a developer can trigger re-application from custom code (00:44:06). - **Why it matters.** For a plugin maintainer, the episode is a catalog of how a scanner has to integrate with a host it doesn't control: hook the host's save event, exclude the host's chrome from scans, raise CSS priority so the host's theme kit can't restyle your panel, and re-run fixes when the host rerenders. For an accessibility-tooling reviewer, it shows a vendor tuning out false positives (1x1 tracking pixels, Ogg audio flagged as video, Query Monitor markup, aria-hidden on core blocks) by mechanism rather than by wholesale rule removal. - **Key stakeholders.** Equalize Digital (vendor), Accessibility Checker Free and Pro users, agencies doing audit and remediation on Elementor, Oxygen, and Divi sites (the stated reason for builder work, 00:18:30), Gravity Forms and FacetWP users, and public bodies posting board minutes under Section 508, ADA Title II, and the European Accessibility Act (00:45:32). - **Risks and tradeoffs.** Version numbers are partly garbled by auto-captions: the Elementor fixes are attributed to a release "that came out yesterday" whose number the transcript renders as "1.0" (00:19:13). Contrast ratios are spoken as "71" and "31," almost certainly 7:1 and 3:1 (00:26:32, 00:27:15). Neither speaker gives a Pro version number for the rescan feature. The bulk rescan and BoardScribe Pro are described as near-future, not shipped. Nothing is benchmarked; the speed claim at 01:02:17 is anecdotal. - **Bottom line.** Shipped and demonstrated: per-issue rescan, image column, Elementor save-rescan and link fix, dual-color outline (Free 1.47.0), Simplified Summary block (Free 1.49.0), tracking-pixel skip (Free 1.47.0), BoardScribe CSV import (1.1.0), affected-code search (release day). Planned: bulk rescan with per-page progress, BoardScribe Pro (alpha, "very shortly after this live stream"), and BoardScribe Free UI overhaul. Treat the planned items as roadmap statements from the vendor. ## 📖 Main content **Who is talking and why.** Equalize Digital makes Accessibility Checker, an automated scanning plugin with a free tier on WordPress.org and a paid Pro tier, plus add-ons (Audit History, Multisite, Exporter) and two adjacent plugins (Archive WP, BoardScribe). Steve Jones is CTO; William Patton is Senior Developer and does most of the demos. This is their recurring changelog livestream; the vault already holds notes from an earlier episode, "Who Can Do What? Accessibility Checker Permissions" (2026-08-26). Everything below is the vendor describing its own work. Where a claim is checkable from the described mechanism, this note says so; where it's a roadmap promise, this note says that too. **Issues Explorer: the consolidation that makes rescanning possible.** Two or three streams ago (00:05:22) Pro replaced its separate Fast Track, Open Issues, and Ignore Log tables with a single "Issues Explorer" application. This episode adds three things to it. First, an image column, off by default, toggled via a Display Options button with no page reload (00:06:51 to 00:08:18); the old Issues Log had this column, the team removed it thinking nobody used it, and users asked for it back (00:09:03). Second, per-issue rescan: opening any issue's drawer shows a "Rescan page" button above the existing "View on page" and "Edit page" buttons (00:10:32). Clicking it rescans the page that issue lives on, posts a notice ("Rescan complete. No changes to this page's issues" or "Rescan completed, five resolved, the issue list has been updated"), announces the notice to screen readers, and updates the counts in place. The drawer stays open even if the issue it was opened for is now resolved, so you keep context until you close it (00:14:08 to 00:15:39). Third, released the day of the stream: search by affected code snippet, not just by snippet description (01:01:34 to 01:02:17). The demo is instructive about the intended use case. Patton fixes issues via WP-CLI in the background rather than through the editor, because saving in the editor already triggers a rescan and you'd never need the button (00:11:57). The button exists for the case where the fix happens outside the page: a theme update, a plugin update, or a code change that affects many pages at once. That's a real gap in most scanners, which tie rescans to content saves. **Planned: bulk rescan.** Jones and Patton describe a bulk action next to the existing "dismiss selected" and "clear selection" options: select N issues, rescan every page they appear on, watch per-page progress, and get a summary of issues found and resolved (00:15:39 to 00:17:05). Jones names the reason it isn't shipped yet: "a lot of UI states to handle" because every page's status has to display as it scans. This is a roadmap statement with no date. **Builder support, part one: Oxygen and duplicate file labels.** Accessibility Checker has a "fix" that appends file size and type to links pointing at downloadable files. Oxygen Builder runs `the_content`-style filters more than once, so the label was appended more than once per link (00:17:47). The fix detects an existing label and skips re-adding it (00:18:30). The transcript renders the detecting party as "EarthX," which is caption noise; the described behavior is "detect if we already applied it." Filters exist to exclude content, per the developer docs (00:18:30). **Builder support, part two: Elementor.** Four changes, all in Free, in a release the transcript dates to "yesterday" (2026-09-23) with a garbled version number (00:19:13). One: clicking Save or Publish in Elementor triggers a rescan "right there live in the editor," hooked to Elementor's save process (00:19:57). Two: opening an element's panel clears the highlighter targets and paging shows "element is not visible" until you save again, because Elementor rebuilds the element on every edit and the plugin can't know whether the issue still exists (00:21:26 to 00:22:10). Three: links inside the highlighter panel (to WCAG criteria and Equalize's documentation) now open in a new tab; Elementor blocks in-editor link navigation, so these links had been dead "for some time" (00:22:54). Four: the rescan had to exclude Elementor's own top toolbar and left sidebar from the scan, which Jones calls "an interesting technical solve" (00:23:37), the same logic used for Query Monitor later in the stream. **Builder support, part three: style hardening and the dual-color outline.** Elementor site kits and theme kits were restyling the highlighter's Previous and Next buttons, so the plugin raised the priority of its own styles (00:24:21 to 00:25:04). Separately, Free 1.47.0 added a second stroke to the highlighter outline: a magenta dotted border with a white border behind it, roughly eight pixels total (00:25:50 to 00:27:58). The reasoning is the same as native browser focus rings, which pair blue and white: magenta passes on light backgrounds, white passes on dark, and the two colors contrast with each other at a ratio the speakers give as "71" (7:1 is the likely intended figure; "31" at 00:27:15 is likely 3:1, the WCAG 1.4.11 non-text minimum). If the two strokes contrast with each other above 3:1, at least one of them contrasts with any background. That's a mechanism argument and it holds. **Simplified Summary block and shortcode (Free 1.49.0).** Accessibility Checker's readability check flags posts above a configured grade level and offers a Simplified Summary field, scanned for grade level itself, output before or after content per a setting (00:28:42). Version 1.49.0 adds a block and a shortcode so you can place the summary anywhere, including in a full-site-editing template (00:33:03). The block is not editable inline; the text lives in the plugin's sidebar Readability tab (00:30:08). The heading is a single translated string ("Simplified summary," H2) editable only in Pro's settings page, and filterable in code without Pro; Jones states that gate has existed since the plugin's start "nearly six years ago" and is not a new upsell (00:32:20 to 00:33:03). Placement priority: an explicit block, shortcode, or template function call wins; if none is detected, the before/after default applies; the plugin never outputs the summary twice (00:34:29 to 00:35:15). Setting "always require" on the demo site was a demo choice, not a default (00:29:25). **Scanner accuracy: six fixes.** Jones frames these against a stated philosophy: the plugin doesn't inject the axe-core ruleset wholesale, it uses some axe-core rules plus its own (00:36:01). The fixes: 1. **1x1 tracking pixels skipped** (Free 1.47.0, roughly two months prior). Previously only Google Tag Manager pixels were special-cased; now any genuine 1x1 image is skipped because screen readers don't announce it (00:36:46 to 00:37:29). 2. **Ogg files no longer flagged as video.** The transcript says "OG files"; Ogg is a container that can hold video frames but is used almost exclusively for audio, so the "video present" flag was a false positive (00:37:29 to 00:38:13). 3. **Video detection regex fixed.** Images with "YouTube" or "Vimeo" in the filename were matched as videos by a source-string regex (00:38:13). 4. **Query Monitor exclusions updated.** The plugin excludes Query Monitor's developer-only markup by class and ID, the standard axe-core include/exclude mechanism. Query Monitor changed its containers for accessibility reasons, which broke the match. The transcript renders the plugin as "Grady Monitor" at 00:40:23 (00:38:56 to 00:40:23). 5. **aria-hidden on core blocks.** Spacer and cover-block backgrounds output `aria-hidden` by design; more core blocks were added to the valid-use list so users stop having to dismiss the flag manually (00:40:23 to 00:41:08). The transcript renders this as "area hidden" and "Arya hidden." 6. **Unicode-aware ambiguous link text.** Detection previously matched only ASCII (transcript: "ASKI," "asy"); it now evaluates any character set, prompted by a user report, with a test suite added (00:41:51 to 00:43:20). **New window warnings after rerender.** Both Free's built-in fix and the standalone Accessibility New Window Warnings plugin share code that parses the page at render time and appends a warning to links opening new windows. Gravity Forms Ajax multi-page forms rerender page two without a page load, so the warning never applied there. The fix hooks Gravity Forms' rerender, BoardScribe's own renders, and FacetWP (already supported), and adds a callable method for developers who rerender their own markup (00:43:20 to 00:45:32). Patton's summary line at 00:44:48, that load-time state is no longer page state, is the episode's most reusable idea. **BoardScribe Free: CSV import and admin columns.** BoardScribe is a meeting-minutes and agenda plugin aimed at organizations that must post minutes under Section 508, ADA Title II, or the European Accessibility Act, though Patton notes many users just want a simple meetings manager (00:45:32 to 00:46:59). CSV import was planned as a Pro feature and moved to Free in 1.1.0, released about three weeks before the stream (00:47:42). The import columns shown: title, date, agenda URL, minutes, not-held, publish date; only date is required (00:49:11). The demo imports 105 rows, skips zero, and schedules three for future dates, with the result announced to screen readers (00:49:54). New admin columns: meeting date (sortable), cancelled, agenda, minutes, with direct links to agenda and minutes files (00:50:38). **BoardScribe Pro preview (alpha, unshipped).** Pro adds Locations (a custom post type with in-person, virtual, and hybrid variants and optional address, room, phone, email, and instructions fields), Documents (a post type so agendas and minutes can be written in the block or classic editor instead of linked as PDFs), and two taxonomies, Types (prefilled: regular meeting, retreat, special meeting) and Groups (00:51:22 to 00:53:35). The meeting edit screen is rebuilt into a componentized UI: agenda, minutes, supporting documents, live stream, recording, and transcript fields, each accepting a BoardScribe document, a media library file, or an external URL as appropriate (00:55:45 to 00:57:13). Patton notes on air that the recording field should also accept media library items and takes a note (00:56:27). Jones says the UI overhaul comes to Free "very soon" and Pro drops "very shortly after this live stream" (00:59:26). A follow-up stream on BoardScribe Pro is planned for the following month with block, shortcode, and table, list, and timeline templates (01:00:50). **Contested or unverifiable in this source.** The 7:1 and 3:1 contrast figures are inferred from garbled speech. The Elementor release version is not recoverable from the transcript. No Pro version number is given for the rescan feature or the image column. The "146,000 issues, same speed" claim at 01:02:17 is a hypothetical, not a measurement. "30 or so languages" for translations (00:31:37) is stated without a source. Release dates are relative ("yesterday," "two months ago," "three weeks ago") and should be pinned against the WordPress.org changelog before citing. ## 🗒️ Notes #### ⏱️ [00:00:02](https://www.youtube.com/watch?v=dZPQX-2yt84&t=2) Stream setup and the plugin family - Roughly four minutes of going live on X and YouTube, then a rundown of the product line: Accessibility Checker Free (WordPress.org and equalizedigital.com), Accessibility Checker Pro, and add-ons Audit History (charts and exports over time), Multisite (licenses, permissions, and stats across a network), and Exporter (CSV). - Two adjacent plugins named: Archive WP (archiving content) and BoardScribe (accessible meeting minutes and agendas), the latter introduced in a prior stream. - Framing for the episode at 00:03:55: "better builder support" means page builders, which Jones says a large share of their users rely on heavily. He describes the episode as many small changes rather than one big feature (00:04:39). #### ⏱️ [00:04:39](https://www.youtube.com/watch?v=dZPQX-2yt84&t=279) Issues Explorer image column - Context: two or three streams back, Pro consolidated Fast Track, Open Issues, and Ignore Log into one "Issues Explorer" application (00:05:22). The demo site shows 183 issues, 9 dismissed. - New image column: a thumbnail for image-related issues, toggled via a Display Options button without page reload, off by default to avoid odd column sizing (00:07:34 to 00:08:18). Clicking opens a larger version. The image was always visible in the issue drawer; the column is what's new. - The column existed in the old Issues Log and was removed to save space. > [!quote] [00:09:03] > also because we thought no one ever relied on it but it turns out that was a mistake. #### ⏱️ [00:09:48](https://www.youtube.com/watch?v=dZPQX-2yt84&t=588) Per-issue rescan - Before: remediate, then run a full-site scan or open the edit page and rescan there. Goal stated at 00:09:48: make the Issues Explorer the one place to do everything remediation needs. - Mechanism: open an issue's drawer; a "Rescan page" button sits above "View on page" and "Edit page." Click, button reads "rescanning," a notice posts at top and is announced to screen readers: "Rescan complete. No changes to this page's issues" (00:11:14). After background WP-CLI fixes: "rescan completed, five resolved, the issue list has been updated" (00:12:42). Counts update in place. Rescan is per page, initiated per issue (00:10:32). - Why WP-CLI in the demo: an editor save already rescans, so the button's real audience is fixes made outside the page. > [!quote] [00:11:57] > this is a good um a good synonym for if someone fixes an issue in their theme - The "View on page" layer is now draggable by its title (00:13:26). After Patton removes a broken Twitter link and saves: "Nine issues resolved. 10 new issues were found," and the drawer stays open for the now-resolved issue until closed (00:14:54). #### ⏱️ [00:15:39](https://www.youtube.com/watch?v=dZPQX-2yt84&t=939) Planned bulk rescan, and the Oxygen duplicate-label fix - Bulk rescan (planned, no date): select issues via checkboxes, choose a new bulk action beside "dismiss selected," rescan every affected page with per-page progress, then a summary of found and resolved (00:15:39 to 00:16:22). Blocker named by Jones: "a lot of UI states to handle" (00:17:05). - Oxygen fix (Pro): the file size and type label fix was appended multiple times per link because Oxygen applies content filters repeatedly. Now the fix detects an existing label and outputs once (00:17:47 to 00:18:30). Filters documented in developer docs control which content it touches. - Stated motivation: audit and remediation clients on Elementor, Oxygen, and Divi (transcript: "Divvy") (00:18:30). #### ⏱️ [00:19:13](https://www.youtube.com/watch?v=dZPQX-2yt84&t=1153) Elementor: rescan on save, cleared state, working links - Release: "the recent version that came out yesterday," version garbled as "1.0" in captions (00:19:13). These are Free features. - Save or Publish now triggers a rescan inside the Elementor editor, hooked to Elementor's save process (00:19:57). Demo: add an HTML widget with `<a href="#">bad link</a>`, publish, and "improper use of links" appears highlighted (00:20:42 to 00:21:26). - Opening an element panel clears highlighter targets; paging shows "element is not visible" until the next save, because Elementor rebuilds the element each time it's edited. > [!quote] [00:22:10] > we don't know whether it's still an issue at that point. - Link fix: Elementor blocks in-editor link clicks, so the highlighter's links to WCAG criteria and Equalize documentation were dead. They now open in a new tab (00:22:54). - Dev note: the publish-triggered scan initially picked up Elementor's own toolbar and sidebar; those had to be excluded (00:23:37). #### ⏱️ [00:24:21](https://www.youtube.com/watch?v=dZPQX-2yt84&t=1461) Style hardening and the two-color outline - Elementor site kits and theme kits were restyling the highlighter's Previous and Next buttons; the plugin raised its own CSS priority (00:24:21 to 00:25:04). - Free 1.47.0: highlighter outline gains a white border behind the magenta dotted one, about one pixel each side, roughly eight pixels total (00:25:50, 00:27:58). Motivation: internal accessibility testing of the plugin itself. > [!quote] [00:25:50] > we don't just make a plugin that helps you check accessibility. We try to make accessibility checker actually accessible itself. - Contrast logic, modeled on native browser focus rings (blue plus white): magenta passes on light, white passes on dark, and the two contrast with each other at "at least 31, but I believe it is high 71" (00:27:15). Read as 3:1 minimum and about 7:1 actual; the transcript drops the colons. #### ⏱️ [00:28:42](https://www.youtube.com/watch?v=dZPQX-2yt84&t=1722) Simplified Summary block and shortcode (Free 1.49.0) - Background: the readability check flags posts over a configured grade level and offers a summary field, itself grade-checked, output before or after content by setting; a template function has existed for manual placement (00:28:42 to 00:29:25). - New: a `/simplified summary` block and a shortcode equivalent. The block isn't editable inline; the text lives in the sidebar Readability tab (00:30:08 to 00:30:52). Works in FSE templates (00:33:03). - Heading: one translated string, H2, "Simplified summary," changeable in Pro settings or via filter in code; the gate has existed since the plugin's start about six years ago (00:31:37 to 00:33:03). Translation coverage stated as "30 or so languages," unsourced. - Dedup rule: block, shortcode, or code placement takes priority; default before/after applies only when none is detected; the summary never outputs twice (00:34:29 to 00:35:15). #### ⏱️ [00:36:01](https://www.youtube.com/watch?v=dZPQX-2yt84&t=2161) Scanner accuracy: six false-positive fixes - Philosophy stated up front. > [!quote] [00:36:01] > we don't just inject uh axe core rule set wholesale. We actually use some axe core and we use a whole bunch of our own stuff - 1x1 tracking pixels skipped entirely (Free 1.47.0, about two months old); previously only Google Tag Manager was special-cased (00:36:46 to 00:37:29). - Ogg ("OG") files no longer flagged as video; images with "YouTube" or "Vimeo" in the filename no longer regex-match as video (00:37:29 to 00:38:56). - Query Monitor ("Grady Monitor"): exclusions by class and ID stopped matching after Query Monitor changed its containers for accessibility; exclusions updated for old and new versions (00:38:56 to 00:40:23). Same reasoning as excluding Elementor's editor frame: visitors never see it. - aria-hidden ("area hidden"): more core blocks (spacer, cover backgrounds) added to the valid-use list (00:40:23 to 00:41:08). - Unicode-aware ambiguous link text: previously ASCII-only ("ASKI"); now any script (Cyrillic, Chinese, accented characters), prompted by a user report, with a test suite added (00:41:51 to 00:43:20). #### ⏱️ [00:43:20](https://www.youtube.com/watch?v=dZPQX-2yt84&t=2600) New window warnings after Ajax rerender - Shared code between Free's fix and the standalone Accessibility New Window Warnings plugin. Warnings are applied at render time, so Gravity Forms Ajax multi-page forms never got them on page two (00:43:20 to 00:44:06). - Now triggers on Gravity Forms rerender, BoardScribe renders, and FacetWP (already supported). A callable method lets developers trigger re-application after their own rerenders (00:44:48). > [!quote] [00:44:48] > what the state of the page is at load time is not the state of the page as people interact with it. #### ⏱️ [00:45:32](https://www.youtube.com/watch?v=dZPQX-2yt84&t=2732) BoardScribe Free: CSV import and admin columns - Purpose: accessible posting of board minutes and agendas for bodies under Section 508, ADA Title II, and the European Accessibility Act; audits found this is often done inaccessibly (00:45:32 to 00:46:16). Patton: many users just want a simple meetings manager (00:46:16). - Pro is in alpha nearing beta, releasing "very shortly after this live stream" (00:46:59). Jones finds bugs, Patton fixes them. - CSV import was going to be Pro; moved to Free in 1.1.0, about three weeks earlier (00:47:42 to 00:48:26). Columns: title, date, agenda URL, minutes, not held, publish date; only date is required (00:49:11). Demo result: 105 rows imported, 0 skipped, 3 scheduled for the future, announced to screen readers (00:49:54). - New admin columns: meeting date (sortable), cancelled, agenda, minutes with direct links; previously only title and date (00:50:38 to 00:51:22). #### ⏱️ [00:51:22](https://www.youtube.com/watch?v=dZPQX-2yt84&t=3082) BoardScribe Pro preview (alpha) - New menu items: Locations, All Documents, Types, Groups. Types and Groups are taxonomies; Types prefilled with regular meeting, retreat, special meeting (00:52:07). - Documents: a post type edited in the block or classic editor so agendas and minutes don't have to be PDFs (00:52:50). > [!quote] [00:52:50] > You don't need to have your agendas be PDFs anymore. - Locations: in-person, virtual, or hybrid, with fields adjusting per type; all optional; reusable across meetings and assignable from a meta box (00:53:35 to 00:54:19). - Meeting screen rebuilt as a componentized UI: location modal (choose or create), agenda and minutes accepting BoardScribe documents, media library, or URL; supporting documents (unlimited, retitleable); live stream (URL only), recording (URL; Patton notes media library support is missing and takes a note), transcript (document, media, or URL) (00:55:02 to 00:57:13). - Sidebar taxonomy boxes map to Groups and Types and drive filtering in the block and shortcode (01:00:08). UI overhaul comes to Free "very soon" (00:59:26). #### ⏱️ [01:00:50](https://www.youtube.com/watch?v=dZPQX-2yt84&t=3650) Affected-code search, speed, and close - Next month's stream: BoardScribe Pro in detail, including block, shortcode, and table, list, and timeline templates, possibly building a meeting-minutes site live (01:00:50). - Issues Explorer addition released the day of the stream: search by affected code markup, not just snippet description; "hotly asked for" (01:01:34 to 01:02:17). - Speed claim, anecdotal. > [!quote] [01:02:17] > I only have 146 issues, but remember if there was 146,000 issues, how slow it would be to use the old interface? - Close: download Accessibility Checker Free and BoardScribe Free from WordPress.org, leave a review ("We prefer fivestar reviews only," 01:03:02, played for laughs), contact via equalizedigital.com and X. Stream ends at 01:04:31 with a promise to go deeper on BoardScribe Pro next time. ## 📚 References The transcript itself contains no links; the following come from the video description or are primary sources for named entities. - [Issues Explorer Rescans and Better Builder Support](https://www.youtube.com/watch?v=dZPQX-2yt84): the source stream, 1:04:48, uploaded 2026-09-24 by Equalize Digital. - [Equalize Digital](https://equalizedigital.com): vendor site named at 00:02:25 and 01:03:48 as a download and contact point. - [Accessibility Checker on WordPress.org](https://wordpress.org/plugins/accessibility-checker/): the free plugin; the changelog there is the place to pin the version numbers the captions garble. - [BoardScribe on WordPress.org](https://wordpress.org/plugins/boardscribe/): the free meeting-minutes plugin described from 00:45:32; verify the slug, since the transcript renders the name six different ways. - [axe-core](https://github.com/dequelabs/axe-core): the ruleset the plugin partially uses and whose include/exclude mechanism drives the Query Monitor and Elementor-frame exclusions (00:36:01, 00:39:39). - [Query Monitor](https://querymonitor.com): the developer plugin whose container change broke exclusion matching (00:38:56). - [Elementor](https://elementor.com), [Oxygen Builder](https://oxygenbuilder.com), [Divi](https://www.elegantthemes.com/gallery/divi/): page builders named at 00:18:30 as the audit-client stack driving builder work. - [Gravity Forms](https://www.gravityforms.com) and [FacetWP](https://facetwp.com): the Ajax rerender sources hooked for new window warnings (00:44:06). - [WCAG 2.2, SC 1.4.11 Non-text Contrast](https://www.w3.org/TR/WCAG22/#non-text-contrast): the 3:1 minimum that the dual-color outline argument at 00:27:15 rests on. - Earlier episode in the vault: "Who Can Do What? Accessibility Checker Permissions" (Equalize Digital, 2026-08-26), which covers the permissions model the Issues Explorer sits behind. ## 🗣️ Paraphrase Jones and Patton spend an hour walking through a release cycle's worth of small changes, and the pattern under them is one idea: a page's accessibility state isn't fixed at load. Builders rewrite the DOM on save. Ajax forms swap in a second page without a reload. Faceted search replaces result lists. A theme update fixes a navigation bug on every page at once. A scanner that takes one snapshot misses all of that, so the work this cycle is about hooking the moments when the page changes. In Elementor, that's the save event. In Gravity Forms, it's the Ajax rerender. In the Issues Explorer, it's a button that says "I changed something outside this page, check it again," plus a planned bulk version for when you changed something that touched fifty pages. The second thread is noise reduction by mechanism. Rather than dropping rules, the team narrows what a rule fires on: 1x1 images are invisible to screen readers, so skip them; Ogg is almost always audio, so don't call it video; Query Monitor's panel is never seen by visitors, so exclude it; spacer blocks hide themselves on purpose, so don't flag it. Each fix names the reason a flag was wrong, which is the right way to prune a scanner. The BoardScribe section is a different product but the same philosophy applied to content: a PDF agenda is usually untagged, so give people a post type and an editor instead. ## 📰 Newsletter **Accessibility Checker learns that pages change after they load.** Equalize Digital's latest changelog stream (1:04:48, Steve Jones and William Patton) is a bundle of small fixes with one theme: re-verify when the page changes, not just when the content saves. Pro's Issues Explorer gets a per-issue "Rescan page" button aimed at theme and plugin fixes that land outside the editor, and a bulk version with per-page progress is on the roadmap. Elementor users get a rescan on every Save or Publish, working documentation links inside the highlighter, and a highlighter outline that pairs magenta with white so it clears contrast on any background (Free 1.47.0). For WordPress folks specifically: Free 1.49.0 adds a Simplified Summary block and shortcode that work in FSE templates and refuse to output twice; six false positives are gone (1x1 tracking pixels, Ogg audio flagged as video, Query Monitor markup, aria-hidden on spacer and cover blocks, and ASCII-only ambiguous-link detection); and new window warnings now re-apply after Gravity Forms Ajax pages and FacetWP refreshes, with a callable method for your own rerenders. BoardScribe, their meeting-minutes plugin, got CSV import in Free 1.1.0 and a Pro tier in alpha that replaces PDF agendas with editable documents. Caveat: this is the vendor describing its own work, and the auto-captions garble version numbers and contrast ratios, so pin anything you cite against the WordPress.org changelog. Links: [the stream](https://www.youtube.com/watch?v=dZPQX-2yt84), [Accessibility Checker](https://wordpress.org/plugins/accessibility-checker/), [BoardScribe](https://wordpress.org/plugins/boardscribe/). ## ✅ Action items #### DevRel - Developer advocacy: a short demo of "scan on host save" (Elementor hook at 00:19:57) and "re-apply after Ajax rerender" (callable method at 00:44:48) would show plugin authors how to integrate with tools they don't control. Measurable outcome: one published example repo. - Education: use the dual-color outline (00:27:15) as a five-minute teaching case for WCAG 1.4.11; the mechanism argument is complete and needs no vendor context. - Developer experience: the stream mentions developer docs listing filters (00:18:30) and a new callable method (00:44:48) without URLs. Request the doc pages and link them from any writeup. - Developer marketing: no direct action. If citing version numbers, verify against the WordPress.org changelog first; the captions garble at least one. - Community management: no direct action from this source; nearest relevance is that two of the six accuracy fixes came from user reports (00:09:03, 00:42:35), a pattern worth naming when asking for feedback. - Internal/external: no direct action. #### OSPO - Policy and governance: no direct action from this source; nearest relevance is BoardScribe's Section 508 and ADA Title II framing (00:46:16) for any org publishing governance minutes. - License compliance: no direct action. - Security management: the Simplified Summary shortcode and BoardScribe supporting-document URL fields (00:58:40, where a sanitizer is confirmed on air) are user-input surfaces; if adopting either plugin, include them in the plugin review. - Software inventory: if Accessibility Checker is in a site's plugin inventory, record that 1.47.0 changed scan output (tracking pixels skipped), so score drops after that version reflect rule changes, not fixes. - Developer support: no direct action. - Community engagement: no direct action. - Strategic alignment: no direct action. #### Community - Maintainers: the image-column reversal (00:09:03) is a clean case study in "we removed it because we assumed nobody used it." Worth citing in any deprecation-policy discussion. - Contributors: no direct action from this source. - Sponsors: no direct action. - Ecosystem: the Query Monitor exclusion break (00:39:39) is a cross-plugin coordination case: one plugin improving its accessibility silently broke another's exclusion list. A shared convention for marking developer-only markup would prevent it. #### WordPress - Core: no direct action. The aria-hidden fix (00:41:08) is the scanner adapting to core block output, not a core change request. - Core Performance: none from this source. - Core AI: none. - **Core Program Team:** none. - Mobile: none. - Playground: a Playground blueprint with Accessibility Checker Free, Elementor, and a seeded bad link would let people reproduce the 00:19:57 save-rescan demo in one click. - Community: none. - Training: the Simplified Summary block (00:30:08) fits any plain-language lesson; the readability check plus summary field is a concrete workflow. - Marketing: none. - Support: the "why did my issue count drop after updating" question is predictable after 1.47.0 (tracking pixels, Ogg, Query Monitor). A knowledge-base note would pre-empt it. - Design: none. - Documentation: none directly; nearest relevance is that Equalize's own filter docs are referenced but not linked (00:18:30). - Photos: none. - TV: none. - Polyglots: the Unicode ambiguous-text fix (00:42:35) is relevant to any locale using non-Latin scripts; worth a note to teams testing accessibility tools in those locales. - Accessibility: the dual-color outline pattern (00:27:15) is a candidate for the team's focus-indicator guidance. The tracking-pixel skip (00:37:29) is a defensible false-positive policy other tools could adopt. - Meta: none. - CLI: Patton fixes issues via WP-CLI in the demo (00:11:57); no CLI change is described. - Hosting: none. - Tide: the six false-positive fixes (00:36:01 onward) are the kind of false-positive review loop Tide would benefit from documenting. - Openverse: none. - Themes: the Elementor theme-kit style leak (00:25:04) is a reminder that theme CSS specificity reaches into plugin admin panels. - Plugins: none from this source. #### The WPOCC - Programs: no direct action from this source; nearest relevance for The WP Open Community Collective is that BoardScribe targets public bodies with statutory minutes obligations (00:46:16), a constituency that overlaps with civic WordPress users. - Projects: none. - Funding experiments: none. ### FAIR - Technical independence: no direct action. Both plugins are distributed via WordPress.org and equalizedigital.com; no third-party runtime dependency is described. - Policies and covenants: none. - Productized governance artifacts: BoardScribe's Documents post type (00:52:50) is a small example of replacing PDF governance artifacts with semantic HTML; relevant if FAIR publishes minutes. ## 🧪 Hypotheses 1. On Elementor sites, the share of issues first detected in the editor (versus in a later full-site scan) rises by at least 30 percentage points after the save-triggered rescan (00:19:57), because detection now happens at the moment of authoring. 2. The 1.47.0 tracking-pixel skip reduces "image missing alt text" counts by 5 to 20 percent on sites running two or more marketing pixels, with no change on sites running none (00:37:29). 3. The magenta-plus-white outline (00:27:15) passes WCAG 1.4.11's 3:1 non-text contrast against 100 percent of sampled background colors, because two strokes that contrast with each other at 3:1 or more cannot both fail against the same background. 4. Per-issue rescan is used mostly after code-level fixes: fewer than 25 percent of rescan clicks follow an editor save on the same page within the previous five minutes, since editor saves already rescan (00:11:57). 5. Ambiguous-link-text detections on non-Latin-script sites increase by an order of magnitude after the Unicode fix (00:42:35), revealing previously invisible issues rather than new ones. 6. New window warnings appear on page two of Gravity Forms Ajax multi-page forms in 0 percent of installs before the fix and above 95 percent after (00:44:06). ## 📊 Methodology - **H1.** Instrument 20 Elementor test sites before and after the release. Log each issue's first-detection context (editor scan versus full-site scan). Compare proportions with a two-proportion z-test. - **H2.** Take 50 sites with known pixel counts from their tag managers. Run Free 1.46.x and 1.47.0 against identical snapshots. Diff alt-text issue counts, stratified by pixel count. - **H3.** Sample 1,000 background colors uniformly in sRGB. Compute contrast of magenta and of white against each; record whether at least one meets 3:1 and whether the two strokes meet 3:1 against each other. This is a calculation, not a study; a spreadsheet settles it. - **H4.** With consent, log rescan button clicks and page save events in Pro with timestamps; compute the fraction of clicks preceded by a save on the same post within 300 seconds. - **H5.** Run the ambiguous-text rule on 100 Cyrillic, CJK, and Arabic-script pages with the pre-fix and post-fix builds; count detections; hand-verify a 10 percent sample for precision. - **H6.** Build a Gravity Forms Ajax multi-page form with a target="_blank" link on page two. Advance to page two on 20 installs per version; check for the warning in the DOM. - **Controls throughout.** Pin plugin versions from the WordPress.org changelog, not from the stream's relative dates. Freeze page snapshots so both builds scan identical DOM. ## ❓ Questions - What is the actual version number of the Elementor release the transcript renders as "1.0" at 00:19:13, and which Pro version shipped per-issue rescan? - Are the contrast figures at 00:26:32 and 00:27:15 really 7:1 and 3:1, and were they measured against the specific magenta hex value shipped? - How does the per-issue rescan handle a page that has been unpublished or deleted since the issue was recorded? - When bulk rescan ships, does it run server-side in batches or client-side per page, and what happens on a 50-page selection with a 30-second PHP timeout? - Does the callable rerender method (00:44:48) fire the full scanner or only the new-window-warning fix? - The Query Monitor break (00:39:39) came from another plugin's accessibility improvement. What's the detection strategy for the next such break: tests against latest versions, or waiting for user reports? - The tracking-pixel skip assumes 1x1 images are never meaningful content. What about a 1x1 image used as a spacer with a title attribute, or a lazy-load placeholder that later resizes? - BoardScribe Documents replace PDF agendas with HTML. Is there an export path back to PDF for bodies that must file a fixed-format record? ## 🔮 Future research - **Rerender-aware scanning as a category.** Patton's line at 00:44:48 names a general problem: scan results are a function of DOM state, and DOM state changes continuously. No WordPress scanner documents a complete list of the events it listens for. A comparative table across Accessibility Checker, WP Accessibility, and Equalize's competitors would show the coverage gap. - **False-positive pruning by mechanism.** The six fixes at 00:36:01 each name why the flag was wrong. A taxonomy of false-positive causes (invisible to AT, misclassified media type, developer-only markup, intentional hiding, character-set assumption) would let other tools audit their own rules systematically. - **Host-editor integration patterns.** Excluding the host's chrome (00:23:37), hooking the host's save (00:19:57), and defending against the host's CSS (00:25:04) recur for every builder. A written pattern with code for Elementor, Oxygen, Divi, Bricks, and the block editor would save every scanner author the same discovery. - **Cross-plugin markup contracts.** The Query Monitor case suggests a convention: a `data-` attribute or class that says "developer-only, exclude from accessibility scans." Whether plugin authors would adopt one is an open question. - **Semantic minutes versus PDF minutes.** BoardScribe bets that HTML documents beat PDFs for accessibility of public records (00:52:50). A study of how many public bodies' minutes are tagged PDFs versus HTML, and how each fares under screen readers, would test the bet. ## 💡 Implications - **Practice.** If you maintain a scanner or any plugin that decorates page output, assume the page rerenders after load and expose a public re-application hook. Equalize added one (00:44:48); most plugins in this space have not. - **Policy.** Scan-score trend lines break at rule changes. A site that dropped 15 percent of issues at 1.47.0 did not get 15 percent more accessible; it stopped being flagged for tracking pixels (00:37:29). Anyone reporting scores over time needs a rule-change annotation layer, which is what the Audit History add-on would need to show. - **Security.** New input surfaces arrived this cycle: a shortcode, a block, CSV import (00:49:11), and URL fields in BoardScribe (00:58:40). The sanitizer is confirmed on air for one field. A review should cover the rest before deployment on a public body's site. - **Education.** The dual-color outline (00:27:15) is a complete, self-contained lesson in non-text contrast. The image-column reversal (00:09:03) is a complete lesson in deprecation humility. Both fit in a five-minute slot. - **Funding.** Moving CSV import from Pro to Free (00:47:42) and keeping the summary-heading filter free (00:32:20) are pricing decisions stated on air. For plugin businesses, the stream is a data point on where a vendor draws the free/paid line: general utility free, agency-scale management paid. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level on the transcript body: approximately grade 7 to 8. Flesch Reading Ease near 72. The register is conversational two-person speech with short sentences; domain terms (aria-hidden, axe-core, Ajax, custom post type, taxonomy) raise effective comprehension to a WordPress-developer audience. #### 👀 Visual learners - Present: live screen shares of the Issues Explorer, Elementor editor, block inserter, BoardScribe import, and Pro meeting UI; the outline demo zooms in on the magenta and white border (00:26:32). - Improve: no diagram of the rescan flow or the rerender hooks. The speakers say "our heads are in the way" at 00:14:08; a picture-in-picture layout would fix that. Chapter markers would let viewers jump to the eleven distinct topics. #### 🔊 Aural learners - Present: two voices in dialogue, which carries reasoning better than a monologue; the "I find them, William squashes them" exchange (00:47:42) is a memorable summary of roles. - Improve: about four minutes of setup before content (00:00:02 to 00:04:39). Trim it in the VOD or mark it as skippable. #### 🗣️ Verbal learners - Present: each fix is explained with its reason (tracking pixels are invisible to screen readers; Ogg is almost always audio; Query Monitor is never seen by visitors). - Improve: version numbers and product names come through garbled in captions. A pinned comment or description listing versions and slugs would anchor the terms. #### 🧩 Kinesthetic learners - Present: every feature is demonstrated live, including a failure ("not in this build apparently," 01:01:34) and an on-air note-to-self (00:56:27). - Improve: no test site, blueprint, or CSV sample to download. The 105-row test file at 00:49:54 would be a useful hands-on artifact. #### 🧠 Logical learners - Present: the contrast argument at 00:27:15 is a complete proof; the dedup priority order at 00:35:15 is an explicit precedence rule. - Improve: the speed claim at 01:02:17 is a hypothetical, not a measurement. One timing number would satisfy this group. #### 🧑‍🤝‍🧑 Social learners - Present: live chat invited at 00:01:41; two user-driven fixes credited (00:09:03, 00:42:35); review and feedback requested at 01:03:02. - Improve: no questions from chat are read on air, so the interaction is one-directional in the recording. #### 🧘‍♀️ Solitary learners - Present: self-contained; every feature is shown end to end. - Improve: no summary slide or written changelog to review afterward. The description repeats the show format but lists no changes. #### 🌿 Naturalistic learners - Present: nothing explicit. - Improve: the false-positive work is a signal-to-noise story; reframing rule pruning as reducing wasted remediation effort (and the energy behind repeated scans) would land here. ## 📊 Accessibility assessment #### Screen reader semantics - Present: the plugin features demonstrated announce their notices to screen readers (rescan result at 00:11:14, import result at 00:49:54), and the speakers say so on air. The YouTube page supplies player landmarks. - Improve: most of the hour's information is on screen (issue tables, button labels, admin columns). The narration names buttons but not table structure. WCAG 2.2 AA 1.2.5 (Audio Description, Prerecorded) is not met; a described version or a written changelog would close it. #### Keyboard navigation - Present: the YouTube player is keyboard operable. The plugin UI shown has paging buttons (Previous, Next) and a drawer, described as accessible by the team. - Improve: nothing in the video adds barriers. 2.1.1 and 2.4.7 pass via the platform. The video does not demonstrate keyboard operation of the Issues Explorer, which would have been on-topic. #### Contrast and readability - Present: the outline change at 00:25:50 is itself a contrast fix, explained with ratios. - Improve: screen-share text at YouTube default resolution is small; admin tables and the CSV column list are hard to read without zoom. 1.4.3 (Contrast Minimum) is unverifiable from the transcript; zoomed cuts on key UI would help. #### Text resizing and reflow - Present: player scales; captions resize independently. - Improve: on-screen admin text is baked into the video frame and does not reflow. 1.4.4 (Resize Text) and 1.4.10 (Reflow) fail for burned-in text, as with any screen recording. #### Media and captions - Present: auto-generated captions exist and produced the transcript used here. - Improve: the captions garble the product under discussion ("Bors Grae," "Bor Graeme," "BoardsCribe," "Borscribe," "bescribe," "BCR Pro," "Boards Sky Pro" for BoardScribe), "Grady Monitor" for Query Monitor, "Arya hidden" for aria-hidden, "OG" for Ogg, "ASKI" for ASCII, "Divvy" for Divi, and drop the colons from contrast ratios. That's a 1.2.2 (Captions, Prerecorded) failure in substance: captions exist but misname most technical terms. Human-corrected captions are the fix and the video is about accessibility, so the gap is notable. #### Forms and interactions - Present: the CSV import form (00:49:11) has one required field and announces results; the BoardScribe URL field rejects empty input (00:58:40). - Improve: not applicable to WCAG in-video; 3.3.2 (Labels or Instructions) applies to the plugin UI, which the demo suggests meets it. #### Standards reference - Primary gaps against WCAG 2.2 AA for the video as published: **1.2.2** (captions inaccurate on proper nouns and technical terms), **1.2.5** (no audio description for on-screen tables and UI), **1.4.4 / 1.4.10** (burned-in text doesn't resize or reflow). No chapters and no changelog in the description compound the navigation cost (2.4.5 Multiple Ways is platform-level, but chapters are the practical fix). The captions failure is the highest-impact and cheapest to fix. ## 🌍 DEIB assessment #### Cultural breadth - Present: the Unicode fix (00:42:35) explicitly widens the scanner beyond ASCII to Cyrillic, CJK, and accented scripts, credited to a user report. Regulatory framing names both US (Section 508, ADA Title II) and EU (European Accessibility Act) law (00:46:16). Translations stated at "30 or so languages" (00:31:37). - Improve: all demo content is English; a non-Latin demo of the ambiguous-text fix would have shown the change rather than describing it. #### Inclusive language - Present: plain, direct speech; no exclusionary terms. "Yolo mode" (00:11:14) and "big beautiful faces" (00:36:01) are informal but harmless. - Improve: the running "we prefer five-star reviews only" joke (01:03:02) is clearly humor but reads as pressure in text form. Low severity. #### Neurodiversity support - Present: each topic is introduced by name, demonstrated, and closed ("So that is the rescan," 00:15:39), a predictable pattern across eleven topics. - Improve: four minutes of setup, off-topic hat banter (00:00:02), and no chapter markers raise the navigation cost. Topic-level chapters would help most. #### Representation - Present: two named speakers with stated roles; users are credited for two fixes. - Improve: no user, client, or disabled person speaks. For a stream about accessibility tooling, a short clip from a screen reader user testing the rescan notice would improve both representation and evidence. #### Psychological safety - Present: mistakes are owned on air ("it turns out that was a mistake," 00:09:03; "not in this build apparently," 01:01:34). Patton takes a feature note live (00:56:27). The tone toward users is grateful. - Improve: none needed beyond the review-joke note above. ## ✅ Logical validity #### Strong reasoning - **Deductive, 00:27:15.** If the magenta stroke passes on light backgrounds, the white stroke passes on dark backgrounds, and the two strokes contrast with each other at 3:1 or better, then at least one stroke passes against any background. Valid, and modeled on an existing precedent (native browser focus rings, 00:27:15). To clarify: publish the hex values and computed ratios. - **Causal, 00:11:57.** Editor saves already rescan, so the per-issue rescan button is for fixes made outside the editor (theme and plugin updates). The demo method (WP-CLI fixes in the background) is chosen to isolate that case. Sound experimental reasoning. - **Mechanism-based pruning, 00:36:46 to 00:41:08.** Each false-positive fix states why the flag was wrong (screen readers don't announce 1x1 images; Ogg is almost always audio; visitors never see Query Monitor; spacer blocks hide themselves on purpose). Each is a checkable premise, and the conclusion (don't flag) follows. - **Generalization from instance, 00:44:48.** Gravity Forms page two is one case; Patton generalizes to "load-time state is not interaction state," names FacetWP and BoardScribe as further instances, and ships a general hook. The generalization is supported by three instances and a mechanism. - **Concession against interest, 00:09:03 and 00:21:26.** Admitting the image column removal was a mistake, and that Elementor state clearing "is something we actually can't work around," raise the credibility of the surrounding claims. #### Fallacies - **Unsupported quantification, 01:02:17.** "if there was 146,000 issues, how slow it would be to use the old interface? Now it is literally the same speed." No timing, no dataset size tested, and "literally the same speed" at 146 versus 146,000 rows is an extraordinary claim about pagination and query performance. *Fix:* state the measured load time at two or three dataset sizes. - **Unsourced figure, 00:31:37.** "30 or so languages" for translation coverage. *Fix:* cite the translate.wordpress.org project page, where the count is public. - **Hasty attribution, 00:38:56.** "I actually think they recently changed their containers to be more accessible" is offered as the cause of the Query Monitor break with a hedge ("I think") but then treated as established. *Fix:* link the Query Monitor changelog entry. - **Ambiguity from uncorrected captions, throughout.** Not the speakers' fallacy, but the "1.0" version at 00:19:13 and the "71"/"31" ratios at 00:27:15 are unusable as cited facts. *Fix:* corrected captions or a written changelog in the description. - No appeal to authority, straw man, or false dilemma was found. Checked: every comparison to competitors (none are named), every reason given for a fix, and the free/pro framing at 00:32:20, which is stated with its history rather than as a sales line. #### Tone of voice - Collegial, unhurried, and self-deprecating. Jones drives the agenda; Patton demonstrates and corrects details ("It is off by default. Yeah," 00:07:34). Contractions and second person throughout ("you can toggle this column on or off"). Humor sits at the edges (hats at 00:00:02, five-star reviews at 01:03:02) and the middle is careful engineering talk with explicit reasons. The register shifts to mild pride at 00:25:50 ("We try to make accessibility checker actually accessible itself") and to candor at 00:59:26 ("A lot of extra work"). Sales language is limited to a closing call for downloads and reviews; there's no competitor disparagement and the one upsell moment (00:32:20) is immediately qualified with "No need to have pro." ## 🛡️ DARVO analysis Not applicable to this source. DARVO (Deny, Attack, Reverse Victim and Offender) describes a response pattern to accusation or criticism, and this is a product changelog stream with no accuser and no defensive posture. The nearest thing to criticism is self-directed: the image column removal "was a mistake" (00:09:03) and the Elementor documentation links "probably been nonfunctional for some time" (00:22:54). For completeness across the three prongs: **Deny**: nothing is denied; limitations are volunteered (Elementor state clearing can't be worked around, 00:21:26; bulk rescan is blocked by UI complexity, 00:17:05; the code search "not in this build apparently," 01:01:34). **Attack**: no critics, competitors, or users are attacked; the Query Monitor change that broke exclusions is described as done "for accessibility reasons" without blame (00:39:39). **Reverse victim/offender**: no such move appears. Emotional cues are limited to laughter and mild self-deprecation. ## 🎯 Conclusion The episode's durable idea is Patton's at 00:44:48: the state of a page at load is not its state as people use it, so a scanner or a fix that runs once is incomplete by design. Every shipped change follows from that. Elementor's save event triggers a rescan (00:19:57). Gravity Forms' Ajax rerender re-applies new window warnings (00:44:06). The Issues Explorer's rescan button (00:10:32) covers the case where the change happened in a theme or plugin rather than on the page. The planned bulk rescan extends the same idea across many pages at once. The second idea is that false positives should be removed by naming the mechanism that made them wrong, not by deleting rules. Six fixes at 00:36:01 onward each do that, and two came from user reports. The dual-color outline at 00:27:15 is a small, complete piece of reasoning worth reusing anywhere a focus or highlight indicator has to survive an unknown background. Treat this as first-party content. Version numbers in the captions are unreliable ("1.0" for the Elementor release; "71" and "31" for ratios), no Pro version is named for the rescan feature, and the one performance claim (01:02:17) is a hypothetical. Bulk rescan, BoardScribe Pro, and the BoardScribe Free UI overhaul are roadmap statements with no dates. **Next steps for readers:** if you maintain a plugin that decorates front-end output, check whether it re-applies after Ajax or builder rerenders and, if not, expose a public hook the way Equalize did. If you review accessibility tooling, pin the version numbers from the WordPress.org changelog before citing this stream, and test the 1x1 tracking-pixel skip against a lazy-load placeholder to see whether the assumption holds. If you publish meeting minutes anywhere, note that BoardScribe Free's CSV import is already shipped and Pro's Documents post type is not. ## 🔄 Refactor Appendix — Issues Explorer Rescans and Better Builder Support > Density: 2–5 Literature atoms (H3 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 5 Literature, 2 Permanent. Resonance filter applied — the speed claim at > 01:02:17 and the BoardScribe Pro preview were dropped as unshipped or unmeasured. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] Load-time page state differs from interaction state > [!quote] [00:44:48] > what the state of the page is at load time is not the state of the page as people interact with it. **Context & use**: - 00:44:48, closing the new-window-warnings segment after naming Gravity Forms Ajax pages, FacetWP, and BoardScribe as rerender sources. - The organizing principle for every fix in the episode. Any scanner or output-decorating plugin that runs once at render is incomplete by this reasoning; the callable re-application method is the practical consequence. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H2] Builder save events become scan triggers > [!quote] [00:19:57] > Now, whenever you click the save or in this case, the publish button actually just performed a rescan right there live in the editor. **Context & use**: - 00:19:57, the first Elementor change, described as hooked directly to Elementor's save process. - Pattern for integrating with a host editor you don't control: subscribe to its save, exclude its chrome from the scan (00:23:37), and clear state when it rebuilds elements (00:21:26). **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H3] Two contrasting strokes pass on any background > [!quote] [00:27:15] > So the magenta always passed on white. The white will always pass on dark. **Context & use**: - 00:27:15, explaining the Free 1.47.0 highlighter outline; the two strokes contrast with each other at a ratio spoken as "71" (read: 7:1), modeled on native browser focus rings. - A complete, reusable argument for any focus or highlight indicator that has to survive unknown theme colors. Applies to WCAG 1.4.11. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> #### [H4] Invisible-to-AT images are skipped, not flagged > [!quote] [00:37:29] > If it is genuinely a one by one image as a tracking pixel, it just will be skipped in the scanner. **Context & use**: - 00:37:29, the first of six scanner-accuracy fixes, shipped in Free 1.47.0; previously only Google Tag Manager pixels were special-cased. - The template for pruning false positives by mechanism: state why the flag was wrong (screen readers don't announce it), then narrow the rule. The open question is lazy-load placeholders that start at 1x1. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H5] Removing an unused-looking feature was a mistake > [!quote] [00:09:03] > also because we thought no one ever relied on it but it turns out that was a mistake. **Context & use**: - 00:09:03, on the image column that was dropped from the old Issues Log to save space and restored to the Issues Explorer after users asked for it. - A concession against interest, stated by the CTO on air. Useful as a deprecation-policy case: absence of telemetry is not evidence of absence of use. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] Scan results expire on rerender **Claim** (one sentence, Courtney's voice): An accessibility scan describes one DOM state, so any tool that scans or patches at load time has to re-run on every event that rewrites the page. **Evidence pointer**: [[#H1]] · [[#H2]] **Scope & conditions**: Holds for any front-end decorator or scanner in a page that uses Ajax, builders, faceted search, or client-side templating. Weakens for fully static pages with no post-load DOM changes. The cost is an event inventory: you have to know which host events rewrite the DOM, and hosts don't publish that list. **Links**: - [[WordPress accessibility tooling]] — because extends - [[Post Kinds build copies drive PHPUnit]] — because contrasts on where stale state hides — build artifacts versus rendered DOM - [[Plugin integration with page builders]] — because applies-in Elementor, Oxygen, and Divi hosts <!-- atomicity: 1 idea ✓ --> #### [P2] Dual-stroke indicators guarantee contrast **Claim** (one sentence, Courtney's voice): A focus or highlight indicator built from two strokes that contrast with each other at 3:1 or more passes non-text contrast against any background without knowing the background. **Evidence pointer**: [[#H3]] **Scope & conditions**: Holds when both strokes are visible at the rendered size (the episode uses about eight pixels total) and the pair meets WCAG 1.4.11's 3:1 between themselves. Breaks if one stroke is clipped or if the indicator is a fill rather than an outline. Native browser focus rings (blue plus white) are the precedent. **Links**: - [[WCAG 1.4.11 non-text contrast]] — because evidence-for - [[Focus indicator design]] — because applies-in any themeable UI - [[wordpress-accessibility skill]] — because extends the focus-visibility checklist <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Pin the Accessibility Checker Free version that shipped the Elementor save-rescan (captions say "1.0," release "yesterday" relative to 2026-09-24) against the WordPress.org changelog — https://wordpress.org/plugins/accessibility-checker/ #fleeting #inbox - [F2] Confirm the magenta hex value and computed ratios behind the "71" and "31" figures at 00:27:15 before citing 7:1 and 3:1 #fleeting #inbox - [F3] Open question: does the 1x1 tracking-pixel skip (00:37:29) also skip lazy-load placeholders that start at 1x1 and later resize? Test on a site using a lazy-load plugin #fleeting #inbox - [F4] Check whether Post Kinds or Post Formats output anything that runs once at render and would need a rerender hook of the kind described at 00:44:48 #fleeting #inbox - [F5] Article seed: "Prune false positives by mechanism, not by rule deletion," using the six fixes at 00:36:01 onward as the worked example #fleeting #inbox #articleseed - [F6] Link this note to the earlier episode "Who Can Do What? Accessibility Checker Permissions" in the vault; the Issues Explorer sits behind that permissions model #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Verify Accessibility Checker Free 1.47.0, 1.49.0, and the 2026-09-23 release notes on WordPress.org and record the real version behind the Elementor save-rescan — research, 15 min #things - [ ] Audit my plugins' front-end output decorators for post-load rerender coverage and note which need a public re-application hook — plugin maintenance #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Issues Explorer Rescans and Better Builder Support.md|Issues Explorer Rescans and Better Builder Support by Equalize Digital]] ## Highlights - [00:09:03] issue is and what image it pertains to. Um this was this was actually um this was a feature we had before in our old issues log and uh we removed it to kind of save space in the table and then through >> also because we thought no one ever relied on it but it turns out that was a mistake. >> Yep. So we quickly had some users ask where could why can't I see the image so we're like we need to bring that back. So, um, but the next feature I think is probably a little bit more of an exciting feature and it's actually something we're bringing new into the issues explore where we did not have something like this before in the in the [00:09:48] old open issues uh and fasttrack uh pages that we have since deprecated um and that is uh rescans. So before you would make changes and then you would have to um you'd have to go do a full-sight scan or go to the page and rescan the you know you'd have to go to the edit page and rescan the page. And what we're trying to do with the issues explore is we're trying to make it like the one-stop one you know one-stop shop where you can do everything you need to do to remediate your website in one place. So the first step in that was bringing in rescanning and this is per issue rescanning. Actually it's per page but like you ([View Highlight](https://read.readwise.io/read/01m3catmrvr1p1zefv2341btzm)) - Note: [H5] Removing an unused-looking feature was a mistake - Tags: atom/literature/h3 - [00:19:13] things like Elementor or Oxygen or Divvy. Um so we're doing a lot inside the plug-in to help facilitate those builder tools. Um so with that said, let's move on to Elementor. So, uh, this would be in accessibility checker free, >> correct? >> Um, and these these fixes, uh, I think these came in the recent version that came out yesterday in uh, 1.0. So, Elementor highlighter improvements. What did we do? >> Yeah. So the the main one is that if you were to save this page right now, it [00:19:57] will actually trigger the rescan right away. Previously, you would have to manually rescan a page in Elementor as you were making changes. Now, whenever you click the save or in this case, the publish button actually just performed a rescan right there live in the editor. So nothing um it works how you would expect previously. I guess it did not work how it would have been expected. You would have had to manually rescan the page after saving it. Now it just scans. >> Yeah, we we've hooked it directly up to Elementor's save process. Right. >> Exactly. So, whenever I click this button, it's rescanned. It's highlighted all the issues on the page. Now, if we were to um let's just ([View Highlight](https://read.readwise.io/read/01m3catdkr55c44m0vgk6t9km9)) - Note: [H2] Builder save events become scan triggers - Tags: atom/literature/h2 - [00:26:32] >> uh maybe >> it may be slightly more than that. >> Yeah. >> But it is at least contrasting between the magenta and the white color. And previously it would just have been the magenta border around that. And this passes on dark backgrounds. Um the magenta color itself passes on light. So now we cover both situations here. >> Are you able to zoom? >> Oh yeah, probably can zoom. Yeah, I can zoom in. can drag this out of the way. >> So basically there's um there's no chance that that there would be a color contrast issue any longer. >> Correct. So the magenta always passed on white. The white will always pass on dark. And because the contrast between [00:27:15] these two is at least 31, but I believe it is high 71. They they will always contrast each other regardless of what the background is. >> Right. So this is this is kind of our own kind of mimic of how like native browser uh outlines work. They they have they have the blue and the white outline. They have both. That way if the blue contrast actually fails, the white will pass. So there's almost no scenario where your your outline would fail color contrast. And we've kind of done a similar approach here. >> Yep. So now this can never they contrast against each other sufficiently. So regardless of what background you have, you will be able to see this. So this ([View Highlight](https://read.readwise.io/read/01m3catfxa59c39ecdj1nwg37x)) - Note: [H3] Two contrasting strokes pass on any background - Tags: atom/literature/h3 - [00:36:46] run through it. Let's kind of like just rapid fire some of these, William. Let's start with >> So, the one by one tracking pixels are common on almost all websites these days. Facebook pixel, YouTube trackers, all kinds of marketing pixels are one by one tracking pixels. They are actual pixels by definition. And, you know, they are they're images that lack alt text. Um, but they are generally invisible from screen readers and as such we actually skip one by one tracking pixels now in our scanner. They will no longer get flagged regardless of how you add them. Previously we had some handling specifically for Google Tag Manager. But now none of them will will [00:37:29] track. If it is genuinely a one by one image as a tracking pixel, it just will be skipped in the scanner. Screen reader won't access it. We shouldn't flag it as a problem. There you go. And that is available as of version 1.47.0 of free. >> That was like two months ago. >> Yeah. [laughter] So, it's been out for a little while. >> Yeah. The the the next one in our list here is OG files. So, OG is capable of containing video or audio, but it is very uncommon to be used for actual video files. It's almost exclusively being used for audio forever. it just is capable of containing frames as well. Um, previously because it was capable of ([View Highlight](https://read.readwise.io/read/01m3catjhm4qpcxfe4k4hjbz71)) - Note: [H4] Invisible-to-AT images are skipped, not flagged - Tags: atom/literature/h3 - [00:44:06] Gravity Forms and you have multi- page forms, your second page would never have the new window warning applied because we parse the page at render time and apply your new window warning fix there. um if you were to change your Gravity Forms to page two of that form in a m multi-art form, it wouldn't trigger again. So now we actually will trigger on gravity forms rer render for Ajax forms um also in borch renders which we'll show in a minute and um we were already doing this for facet WP and yeah now there is for a developer there is actually now a callable method [00:44:48] if you're building a system that will rerender after the page loads you will be able to just trigger this new window warning on them whenever you do your own rerender. >> Yep. So just another way we're expanding support of accessibility checker into builders into you know gravity forms we already do it for facet WP we do it for our own plugins so we're just trying to make sure that accessibility checker plays well with others >> and it is becoming far more common now where what the state of the page is at load time is not the state of the page as people interact with it. So now we're trying to make sure that we catch those interactive elements. Yep. Cool. Well, finally, let's talk a little bit about ([View Highlight](https://read.readwise.io/read/01m3catb2dkj81akfd6gxt4vny)) - Note: [H1] Load-time page state differs from interaction state - Tags: atom/literature/h1