-
Notifications
You must be signed in to change notification settings - Fork 0
[Frontend][A11y] Associate the post-revision Review lock reason with disabled decisions #2461
Copy link
Copy link
Closed
Labels
Priority IIIValuable but unscheduled: residuals, tech-debt, performance, depth work.Valuable but unscheduled: residuals, tech-debt, performance, depth work.bugSomething isn't workingSomething isn't workingfrontendPrimary implementation impact in Vue/TypeScript UI and client runtime.Primary implementation impact in Vue/TypeScript UI and client runtime.uxDiscoverability, accessibility, interaction model, and user workflow quality.Discoverability, accessibility, interaction model, and user workflow quality.
Description
Activity
Metadata
Metadata
Assignees
Labels
Priority IIIValuable but unscheduled: residuals, tech-debt, performance, depth work.Valuable but unscheduled: residuals, tech-debt, performance, depth work.bugSomething isn't workingSomething isn't workingfrontendPrimary implementation impact in Vue/TypeScript UI and client runtime.Primary implementation impact in Vue/TypeScript UI and client runtime.uxDiscoverability, accessibility, interaction model, and user workflow quality.Discoverability, accessibility, interaction model, and user workflow quality.
Projects
- StatusShow more project fieldsDone
Context
PR #2448 renders a live status while the post-revision truth refresh disables the Review decision rail. Independent accessibility review found the status is attached through aria-describedby to the non-focusable ReviewMain wrapper, while the four disabled decision controls only receive the older editLock description linkage. Refs #1964, #2215, and PR #2448.
Current impact
The live role=status announcement and focus restoration work, so the reviewer is not silently trapped. However, assistive technology inspecting the disabled Reject, Request edit, Defer, or Approve control does not get a direct relationship to the refresh-lock explanation.
Acceptance