a11y(reports): include buyer-visible LeftoverPairList evidence in actionable button names

[seonghobae]

Current buyer-visible gap — 2026-09-21

#977 remains the single LineageWeave source owner for LeftoverPairList actionable-name accessibility and rendered browser acceptance. Current exact head is 9dbb28706a3418ef0f9500873e9e7d7417961ef3 on parent #830 bebd77c03e5beae469f42361c20bccc80787ebb5; the last source-bearing accessibility repair is bce09c145b979e348d3db3ecad01246ff2d20ed9, with the exact head adding only the live gap-baseline refresh.

The historical Label-in-Name defect is source-repaired: the button name begins with the exact visible localized Closest leftover: / Farthest leftover: label and consumes formatter-admitted persisted evidence without recomputing psychometric truth. Dense/mobile wrapping, 44px touch targets, keyboard/focus, mouse/touch, and Storybook Chromium acceptance scaffolding remain in this lane.

Current executable findings and repairs

• duplicate accessible evidence RED 2a9696b25ce2423ebfff48217ea2e0a31ee3630f → causal fix 57c60f622b0cbda0a746a99d3af9dd98b50c679b;
• ADR 0162 visual/non-finite accessibility RED 5dd4a63bb007c27c23b26e5c3895f8fa9e6abe52 → causal fix d162aaf307108fbbbda807c2dc4c0c74f33eda7a;
• docs(gaps): refresh exact-head product evidence #1041 documentation merge 73e0b59c06c1181538390fb32d79ef0c4091994b and post-merge convergence 7d052532bde0000cb96cdd57957ff20806aa5c31 removed the second live LeftoverPairList writer;
• ADR-lineage RED ff8adc587a5166c39a2d81450ab60ee602f3c9e5 → fix 724614e4d769986471fc5192285cf5d558c64ab5 restores accepted ADR 0272–0280 links dropped during documentation convergence;
• rank-zero accessible-evidence RED 7b6ff5bc16beb9c2ae91961bc753fb10ff3d7a89 → fix bce09c145b979e348d3db3ecad01246ff2d20ed9. formatLeftoverMapRank(0) visibly admits rank 0, but the localized rank-zero guidance does not literally name that value. The fix leaves rank unsuppressed only in the rank-only zero branch so the formatter badge is announced exactly once, while rank-zero + Y/E and non-zero rank keep their existing deduplication.

Relative to 724614e4..., source repair bce09c14... is ahead 2 / behind 0 and changes only the focused rank-zero regression plus a 3-addition/1-deletion component edit. Current exact 9dbb2870... is one documentation-only commit above that source repair and refreshes docs/product-technical-gap-baseline.md; predecessor workflow receipts do not transfer.

Domain / ownership boundary

LineageWeave owns this read-model composition and accessibility contract. Consume existing persisted values and existing formatters only. Do not derive psychometric values, add SQL/schema, copy fast-mlsirm/TEPP/RankWeave truth, or create translation authority competing with #929/#932. Canonical locale resources remain KO/EN/JA/ZH/VI/ES/DE/FR through the translation-ledger owner.

Remaining acceptance

Source repair is not product GREEN. No pull-request workflow receipt exists yet for exact #977 head 9dbb2870...; the last source-bearing head had Devin Review and CodeRabbit status success only, which are not focused/frontend/full-suite/Storybook/Security/SAST/CodeQL acceptance and are not independent approval.

Keep this issue open until one unchanged exact #977 head or verified successor has:

1. focused and full frontend/full-suite GREEN plus lint/build;
2. Storybook Chromium keyboard/focus/mouse/touch and dense/mobile containment GREEN;
3. accessible-name evidence proving each finite measurement, including persisted rank 0, is announced once; non-finite residual visual disclosure remains R — without entering the accessible name; and non-finite distance never becomes d NaN;
4. applicable Security/SAST/CodeQL GREEN;
5. KO/EN/JA/ZH/VI/ES/DE/FR consumer and CJK/text-expansion/font-fallback evidence where applicable;
6. no unresolved valid review finding and qualifying independent current-head approval.

No no-op wake commit, Draft/Ready cycling, predecessor-receipt transfer, self-approval, force push, destructive rebase, gate weakening, psychometric reimplementation, translation-store duplication, or second LeftoverPairList source writer is authorized.

[seonghobae]

Draft successor #977 stacks this accessible-name repair on leftover-map single-writer #802. Grouping-comparison pair actions stay on #829/#830.

[seonghobae]

Fresh #977 review found two repair requirements before this issue can close. The PR carries a valid evidence-in-accessible-name delta, but its current base is still historical #802 rather than the serialized product parent required here; preserve it as Draft evidence and reconstruct after #830 converges. In addition, its explicit aria-label starts Open leftover {kind} pair… while the visible button text starts with the localized {kindLabel}: …, so the visible label is not contained in the programmatic name. That conflicts with WCAG 2.2 SC 2.5.3 Label in Name (Level A): https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html . Current-parent reconstruction should prefix the accessible name with the exact visible button label, then append localized action/evidence context, with a rendered role/name regression and the existing fail-closed non-finite metric cases. Review authority: #977 review 5131642217.

[seonghobae]

#977 has now been reconstructed non-force on current serialized parent #830 (bebd77c03e5beae469f42361c20bccc80787ebb5) and advanced by a normal fast-forward repair to exact head 8d78f22567c200e926e811a3a419a6dab60905e2. The historical evidence delta is preserved and the SC 2.5.3 finding is repaired on the current parent: the button accessible name starts with the exact rendered localized label and then carries the localized action/evidence context. Finite persisted R, Y/E, rank, U, shares, R̂, ξ/ζ and d follow the existing formatter admission; non-finite residual/distance are omitted. Follow-up review also closed the old-payload edge where no other numeric evidence is finite: it now falls back to the existing localized open action instead of exposing R — / d NaN. A focused current-parent successor regression replaces the stale #802-era component/App assertion slices. Compare from #830 has merge-base exactly #830 and behind=0; only the component plus focused regression differ. #977 is Ready for validation admission only; predecessor/Draft receipts are not GREEN and no merge is authorized.

[seonghobae]

#977 current-head follow-up closes the remaining source-level dense/mobile acceptance gap without broadening the shared post-list contract.

• RED a73b7e8abeb4f5d55a8ce853ebd108e7eef53584: adds a mobile1 Storybook path requiring the closest/farthest evidence-heavy actions to avoid internal horizontal overflow, remain at least 44px high, and preserve pointer/click selection of the exact persisted farthest pair.
• scoped repair b586ea945809bb60b68e32e17701684f29e9346c: new LeftoverPairList.css gives only .leftover-pair-action flex wrapping, the existing --size-touch-target minimum, shrinkable children and overflow-wrap.
• exact head b041ab7dfe5cea09071cdf5d36de2acafb7ae27b: activates that scoped class on the native pair button. Existing visible-label-prefix accessible names, keyboard semantics, persisted evidence values, identity and translation ownership are unchanged.

Fresh Tests 35283791337 exists, but Frontend 105411486745 and Full suite 105411487122 are still queued pre-runner. This is therefore a source/test repair awaiting hosted Storybook/full-suite evidence, not completion/merge evidence.

[seonghobae]

Follow-up current-head evidence for #977: review of b041ab7dfe5cea09071cdf5d36de2acafb7ae27b found that the inherited LeftoverPairList.test.tsx still queried three exact pre-repair accessible names (Open leftover closest/farthest pair: ...). Those selectors are incompatible with the issue's accepted visible-label-prefix contract and would make the frontend suite RED once admitted, without exercising the repaired evidence name.

Commit 55d69ebbf2c8b31a9544fef470cff099ecb83578 changes only those stale role/name selectors to anchored Closest leftover: / Farthest leftover: prefixes (+4/-4 in one test file); product code and evidence semantics are unchanged. Fresh Tests 35284829585 is materialized but both jobs remain pre-runner, so hosted GREEN/browser acceptance is still outstanding. Canonical queue-health canary: ContextualWisdomLab/.github#712 comment 5722361921.

[seonghobae]

#977 advanced non-destructively to exact 5a8deac88b4b8f8a25466b57b234f9e63b4d39c9 on unchanged parent #830 bebd77c03e5beae469f42361c20bccc80787ebb5.

Fresh review found the remaining material-UI evidence gap was test-source only: NarrowDenseEvidence proved dense-mobile width/touch-target and generic click behavior, but did not explicitly exercise mouse-pointer vs touch-pointer activation. The new commit changes only LeftoverPairList.stories.tsx, using Testing Library/Storybook userEvent.pointer with [MouseLeft] and [TouchA] and requiring exact pair identity for each. Production source/CSS/copy/psychometric evidence/translation ownership are unchanged.

Fresh Tests 35288624582 exists; Full suite 105426396094 and Frontend 105426396348 are still queued pre-runner with no steps. All predecessor receipts are historical. Canonical runner canary: ContextualWisdomLab/.github#712 comment 5722794842. Keep #976 open until current-head hosted Storybook/frontend/full-suite plus required security/review evidence actually settle.

[seonghobae]

Fresh #977 review found the material-UI acceptance source was still not executable in hosted CI: repository Tests built Storybook but never ran the keyboard/focus/pointer/touch play contracts. #977 now carries RED 1463c94... requiring browser execution and exact head d08cb70f498c3afa4e4a1d7b9318a131caa36b1d reusing pinned Playwright/Chromium against built storybook-static. Browser-only .pw.ts + Playwright testMatch keeps it out of Vitest discovery. Fresh Tests 35293139866 is still pre-runner (105440086877, 105440087005), so the repair is not hosted GREEN yet; no merge/approval claim.

[seonghobae]

2026-09-18 fresh hosted validation changed the #977 classification. Tests 35293139866 finally reached hosted runners on exact d08cb70f498c3afa4e4a1d7b9318a131caa36b1d. Frontend job 105440087005 failed in Vitest before build/Storybook/Chromium: the dedicated LeftoverPairList suites were GREEN, while two inherited frontend/src/App.test.tsx cases still queried the historical Open leftover closest/farthest pair: ... accessible names instead of the repaired visible-label-prefix contract (Closest leftover: / Farthest leftover:). Full suite job 105440086877 ran PostgreSQL but was cancelled after the frontend failure/head movement and is not GREEN evidence.

A candidate whole-file edit d76f021c... was rejected after compare exposed unrelated broad App-test churn (+273/-1135). It was neutralized forward-only, without force/rebase, by 640ee39fef7a49cbe5d86468b203e5232c96724b, which restores the exact predecessor App.test.tsx blob; d08cb70f... → 640ee39f... is tree-identical. #977 is now Draft on 640ee39f.... The remaining valid repair is intentionally narrow: update only the stale App integration selectors/accessible-name expectation to the same visible-label-prefix contract already proven by the focused component regressions, then obtain fresh hosted frontend/full-suite/browser evidence. No product-source regression is currently indicated.

[seonghobae]

Documentation-currentness follow-up is now repaired without touching the active #977 product writer. #1041 commit 91a66bf69e200615f890177b4cfd2a5a6686dd64 updates ADR 0049 so the normative accessible-name contract matches LeftoverPairList: exact localized visible Closest leftover: / Farthest leftover: label first, localized action/evidence after it, formatter-admitted finite persisted evidence only, and no R — / d NaN placeholder announcement. The live gap baseline is refreshed at b3d844d085f871aba529fcfda9cdfbfc9c2301fa. This is docs-only evidence; #977 remains cf3bc986... with its sole one-shot selector repair still queued pre-runner, so no product acceptance or head movement is claimed.

[seonghobae]

#977 repair execution is no longer queued. One-shot run 35316632816 / job 105509597284 obtained a hosted runner and completed every step GREEN, including the exact stale-occurrence guard, narrow App.test.tsx selector edit, diff guard, locked frontend install, focused App + both LeftoverPairList regressions, frontend lint, and commit/push. It produced exact head c614d683414b0af1af006c96ed53169ab5b21ee2, exactly one commit ahead of cf3bc986...; the delta is five App selector/assertion changes plus deletion of the purpose-complete one-shot workflow. No open descendant is based on #977.

This closes the stale App-selector causal RED, but not final acceptance. Current-head Tests run 35340400072 is action_required with zero jobs, so it is control-plane evidence rather than repository/full-suite/browser GREEN. #977 remains Draft. Next valid gate is final-head repository/full-suite + Chromium execution, applicable security/CodeQL evidence, locale/font-fallback acceptance, and qualifying independent current-head approval. No wake commit/rerun/lifecycle churn is being used.