A11y | Bump design-system for D3 divider color - #61
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughThe design-system submodule now points to the merged D3 revision. A characterization test verifies that the split-panel divider uses the Merge Risk: ⚪ Minimal · up to The PR makes a localized design-system reference update and adds a focused divider-color characterization check. No actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Comment |
Summary
Closes #59. This app now consumes the design-system D3 Split Panel change: the divider line is
Neutral-800at ≥3:1 against both pane surfaces. D2 name and 24×24 hit target are unchanged.Also records A17 as closed (PR #60) on the issue map. That number is not on the D3 or bump D3 rows.
Changes
Submodule
public/design-systempoints at0e02e04(DS PR #33). No app widget changes.Characterization locks the divider
::afterso it cannot regain#2b3b52.Axe floor stays
color-contrast1 (Sort empty-dropzone placeholder, A21). Split-shell scenarios had 0 violations.Test plan
npm test— D2 hit target/name still hold; D3 token lock passesPORT=3010 A11Y_BASE_URL=http://127.0.0.1:3010 SIM_PORT=8081 SIM_ORIGIN=http://127.0.0.1:8081 npm run a11y:ci— baseline unchanged