# An Accessible Interface Wrapping Inaccessible Content Relocates the Barrier ## Claim A conformant, well-tested interface that links out to inaccessible content — an untagged, image-only PDF behind a perfectly-marked-up table — produces a conformant wrapper and an unreadable record at the same time, because conformance at the wrapper measures the wrapper and the user's actual goal lives in what it links to. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds wherever accessibility work is measured or audited at the interface layer while the content it links to escapes the same scrutiny — most commonly, tables or lists of documents pointing to PDFs, scans, or embeds. - The failure is structural, not a matter of the interface team trying less hard — the BoardScribe case shows genuinely careful ARIA work (live regions, focus management, explicit empty states) sitting directly upstream of exactly this gap. - Breaks once the content itself is authored inside the same accessible surface (native pages instead of linked documents) — which converts the wrapper's conformance into actual conformance, rather than moved conformance. - Distributional corollary: when the fix (native authoring) is paywalled and the wrapper is free, the population most likely to be under-resourced inherits the wrapper's conformance and not the content's. ## Evidence BoardScribe's free tier ships careful non-visual accessibility for its meeting-record tables: descriptive per-row link labels instead of repeated "View Agenda" text, a `polite` ARIA live region for pagination, focus moved to the table rather than the page top after paging, and explicit "Agenda not available" text instead of blank cells. None of that touches the actual public record, which is typically a scanned or exported PDF — frequently untagged, often image-only, unreadable by a screen reader regardless of the table's own conformance. The Pro-tier fix, BoardScribe Documents, replaces linked PDFs with agendas and minutes authored directly as WordPress pages — the one feature that closes the gap the rest of the product's accessibility work cannot reach, and it sits behind the paywall for an audience (small municipalities, volunteer nonprofits) with the weakest budgets and the strongest legal obligation to publish accessibly. ## Links - [[3. Resources/Permanent Notes/Validation That Inspects Steps Cannot See Composition]] — because applies-in; both are a check correct at its own layer and irrelevant to the outcome that actually matters — there a request-level filter blind to a composed attack, here a table-level conformance check blind to what it links to. - [[3. Resources/Permanent Notes/Accessibility Enforced at Authoring Time Beats Post-Hoc Auditing]] — because extends; BoardScribe Documents is a direct instance of that note's general claim — bringing content inside the authoring surface is what actually closes the gap a post-hoc wrapper can't. - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; plugin-directory accessibility guidance and civic-sector compliance tooling are governance questions about what gets built into the free tier versus sold. - [[3. Resources/MOCs/Accessibility & Disability Inclusion MOC]] — the verification trap this map collects: conformance at one layer moving the barrier to the next ## Tests / falsifiers - Audit a sample of public-body meeting-record pages built on WordPress: what fraction link to untagged or image-only PDFs regardless of how accessible the surrounding table markup is? - Run comparative screen-reader task completion on the same records published as (a) an accessible table linking to a PDF versus (b) BoardScribe Documents' native-page authoring — this is the test that would confirm or disconfirm the claimed gap directly. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/Introducing BoardScribe Accessible Board Meeting Minutes for WordPress|Introducing BoardScribe - Accessible Board Meeting Minutes for WordPress]] — Equalize Digital walkthrough, 2026-07-31 (recovered via machine-generated screen description; verify technical specifics against the plugin source before further reliance).