record:path conveys travelled / upcoming / lost stages by colour alone — the ✓ and ✗ are aria-hidden, so the state never reaches the accessible name

[claude]

Found while working the lifecycle-path readout card in packages/plugin-detail/src/renderers/record-path.tsx. Pre-existing, not introduced by that change, and outside its fence — filing rather than folding it in.

What a screen-reader user gets

record:path distinguishes travelled stages from upcoming ones with colour and a check glyph, and the glyph is aria-hidden:

<span aria-hidden="true" className="... text-emerald-600 ...">✓</span>
{stage.label}

The only programmatic signal on any stage is aria-current="step" on the current one. So a screen-reader user hears a list of six identically-announced items with one marked "current step" — and cannot tell that 草稿 and 审核中 are already behind the record while 已接受 and 已过期 are ahead of it. The same holds for a lost terminal: its ✗ is aria-hidden too, so 已拒绝 announces exactly like an ordinary upcoming stage.

Sighted users get this distinction from colour alone (emerald = travelled, muted = upcoming, destructive = lost terminal), which is WCAG 2.2 SC 1.4.1 Use of Color.

Reproduce

Any object declaring a stageField renders this chrome on its record page. Put the record on a middle stage and read the path with a screen reader, or inspect the accessible tree: the list items' accessible names are the bare stage labels.

Shape of a change

The stage's state needs a text equivalent that reaches the accessible name — e.g. visually-hidden text per stage, or an aria-label composing label + state. Both introduce user-facing strings, so this needs i18n keys rather than the hardcoded English the component currently uses for its container labels; that is why it is its own card rather than a one-line addition.

Related but distinct: #5569 tracks duplication of the approval stepper, a different surface with its own markup.

Context: the readout markup was reworked in claude/issue-5768-inert-lifecycle-path, which de-buttoned the path but deliberately did not move its accessible semantics.

---

Generated by Claude Code

---

Generated by Claude Code

[claude]

Triage (daily round, session session_01Kktexqp6uVuFMztvvTMf3V, 2026-08-24): lands in packages/plugin-detail/src/renderers/record-path.tsx → domain:ui + pm:queue, Bug (WCAG 2.2 SC 1.4.1 — travelled/upcoming/lost state conveyed by colour alone; the glyphs are aria-hidden). Fix shape: give each stage a programmatic state (visually-hidden text or aria-label), keep the glyphs decorative.

---

Generated by Claude Code

[os-warren]

Claim: PM loop round 34
Session: session_019ZyKZejBWZoCSj1NP35wcp
Branch: claude/issue-5916-record-path-accessible-state
Worktree: objectui-issue-5916
Domain: domain:ui
File surface: packages/plugin-detail/src/renderers/record-path.tsx (+ its tests, + the i18n keys the change needs, + a changeset) (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus
Clause-②: no — adds accessible-name text and i18n keys; no authoring key changes and no published schema surface widens.
Serial constraints cleared: packages/plugin-detail/src/renderers/record-path.tsx — no in-flight claim touches it; zero claude/issue-* branches on the remote.

⚠️ PREMISE CHECK FIRST — this file changed a few hours ago

record-path.tsx was rewritten by PR #5917 (fix(plugin-detail): render record:path as a readout, not a fake segmented control, merged 2026-08-24), which closed a different card (#5768). This card was filed from inside that work and says so: "the readout markup was reworked in claude/issue-5768-inert-lifecycle-path, which de-buttoned the path but deliberately did not move its accessible semantics."

⛔ Do not take the card's JSX snippet as current source. Re-read the landed file first and establish, against the shipped markup, whether the defect still stands: are the ✓/✗ glyphs still aria-hidden, and is aria-current="step" still the only programmatic signal? premise_still_valid: false with no PR is a legitimate and valuable delivery here — report it rather than manufacturing a diff.

If the premise holds

The requirement is that a stage's state (travelled / upcoming / lost terminal) reaches the accessible name, not just colour and an aria-hidden glyph — WCAG 2.2 SC 1.4.1. The card names two shapes (visually-hidden per-stage text, or an aria-label composing label + state); pick one and say why.

• User-facing strings mean i18n keys — ⛔ not the hardcoded English the component currently uses for its container labels. That is explicitly why this is its own card and not a one-liner.
• Verify with the accessible tree, not the DOM: the deliverable is that the stage's announced name carries its state. A test asserting a class or a span is not evidence about the accessible name.
• ⛔ [finding] The approval step stepper is hand-duplicated across apps/console and packages/app-shell, and the copies had already drifted into two different overflow behaviours #5569 (approval-stepper duplication) is a different surface with its own markup — do not touch it or fold it in.

---

Generated by Claude Code

[os-warren]

{
  "issue": 5916,
  "status": "done",
  "branch": "claude/issue-5916-record-path-accessible-state",
  "pr": "https://github.com/objectstack-ai/objectui/pull/5958",
  "premise_still_valid": true,
  "summary": "Premise re-checked against the SHIPPED file (0b12a3315, PR #5917) rather than the card's JSX snippet, and it holds unchanged: the check glyph is aria-hidden at record-path.tsx:177, the cross at :175, and aria-current='step' at :170 is still the only programmatic signal. #5917's data-stage-state / data-stage-terminal are test instruments, not accessibility — a data-* attribute is not in the accessibility tree, and its own header says so. Each stage now carries an accessible name composing its already picklist-localized label with its state, from five new detail.pathStage{Completed,Current,Upcoming,LostCurrent,LostUpcoming} keys added to all ten locale packs and mirrored byte-identically into DETAIL_DEFAULT_TRANSLATIONS. Shape chosen by measurement, not preference: listitem is not a name-from-contents role, so sr-only text inside a stage computes to an EMPTY accessible name (probed on this tree with the suite's own harness before writing the fix) — the card's first candidate shape would have satisfied a DOM assertion while delivering nothing to the accessibility tree, so the state is composed into aria-label instead. Glyphs stay decorative; the #5768 readout contract (role, aria-current, data-stage-*) is untouched. The ten packs plus the defaults map are inside the card's stated surface ('the i18n keys the change needs'): all-locales-key-parity fails a key en has that any pack lacks AND a key a pack has that en lacks, and defaults-maps-mirror-en-pack fails a map row whose key the pack lacks — five keys means fifty pack rows plus five map rows, or nothing.",
  "tests": "All at f4cb3fec4 (branch head), run from the repo root with pnpm exec vitest run per this repo's guard. SUITES: packages/plugin-detail whole package — 'Test Files 97 passed (97) / Tests 916 passed (916)'; packages/i18n/src/__tests__/ plus app-shell defaults-maps-mirror-en-pack.test.tsx — 'Test Files 52 passed (52) / Tests 893 passed (893)'; cross-package consumers of record:path (console x3, app-shell previews x1) — 'Test Files 4 passed (4) / Tests 129 passed (129)'. Two new suites add 13 cases. GATES (exit code captured by redirecting to a file first, never after a pipe; verdict lines quoted as each gate printed them): check:control-bytes 'OK (scanned 4942 tracked text file(s); skipped 85 binary)'; check:i18n-keys 'Every in-scope call-site key resolves against the en pack (2934 keys) ... every call site passes exactly the arguments that value has holes for' — this is what confirms { stage } matches the {{stage}} hole in all five keys; check:i18n-drift 'No en value changed in this range.' and '5 key(s) added, 0 removed'; check-changeset-presence.mjs '14 source file(s) of 2 released package(s) changed, and this change declares 1 changeset(s)'; turbo run type-check --filter=@object-ui/plugin-detail --filter=@object-ui/i18n — 14 tasks successful, and plugin-detail's script is 'tsc --noEmit' then 'tsc -p tsconfig.test.json', so the new suites are type-checked too; turbo run lint for both packages — 3 tasks successful, 0 errors (record-path.tsx reports 15 warnings and the merge-base version of the same file reports the same 15, so this change adds none). ABLATION: deleted the single aria-label line from renderStage and re-ran the two new suites plus the pre-existing record-path.inertReadout.test.tsx — 'Test Files 2 failed | 1 passed (3) / Tests 15 failed | 12 passed (27)', matching the direction predicted in both suite headers before running. Red: every case whose subject is the accessible name (group B 6, the three name-bearing cases of group C, group D 1, all five locale cases). Green: group A (the #5768 readout contract), group C's 'the cross stays aria-hidden' case, and the whole pre-existing inertReadout suite — none of which ever depended on the name. The mutation was confirmed ON DISK by grepping the deleted text (count 1 -> 0), not by the editor's exit code; the script carried trap ... EXIT INT TERM; the restore was verified byte-identical with diff -q against a pre-ablation copy and the marker count returned to 1. NO REBUILD claimed or needed: both suites import the subject relatively (../record-path) and resolve cross-package imports to each package's own src via the root vitest.config.mts alias table, so nothing resolves through a dist/ — the property record-path.inertReadout.test.tsx already records for itself. CI convergence not awaited, per the standing dispatch contract; gate jobs were still in_progress at report time (PR mergeable_state 'unstable').",
  "open_questions": [],
  "out_of_scope_findings": [
    "filed as #5956: record:path's three container aria-label literals are hardcoded English ('Record path' on both rows, 'Alternative terminal stages' on the lost group), and the last of those sits on a role-less div, so it is not merely untranslated but inert — browsers expose no accessible name on a generic element. Left untouched: an i18n defect rather than this card's colour-alone defect, and the div needs a decision rather than a string swap.",
    "filed as #5957: an unreached `won` terminus is still distinguished by hue alone (bg-emerald-500/30 vs bg-muted) and, after this change, still announces as a plain upcoming stage. Same WCAG 1.4.1 class as this card, but the fix is new user-facing copy in ten packs rather than a mechanical change, so it failed the bounded-in-place bar (the correct wording is pinned by nothing in the tree)."
  ]
}

Notes for the PM, outside the machine-checkable fields:

• The card body is not truncated, but its JSX snippet is sanitizer-damaged — the span aria-hidden wrappers were eaten from the fenced block, leaving a bare check glyph and {stage.label}. Prose, repro and related-cards sections are all intact. The same sanitizer ate the tags out of my own PR body's evidence block on first write; I re-read it, rewrote that block without literal angle brackets, and confirmed the repair. Worth knowing that a fence is not protection.
• File surface: no breach. 15 files — record-path.tsx, two new test files, useDetailTranslation.ts, ten locale packs, one changeset. The packs and the defaults map are the declared "i18n keys the change needs"; the parity gates make them non-optional, as the summary records.
• PR is draft, no auto-merge, Fixes #5916 on the first line. No timers scheduled.

---

Generated by Claude Code

---

Generated by Claude Code