You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current accessibility checkpoint — 20 September 2026
Exact merged heads: WebScene a46b62e14eb197603f7e227c1558afb9088633b0; AppScene 97702daeb9ad71341ced7226f0aa966dc77ea53c; unchanged Code OSS 645f29cc3176500b4b5762ba887cf2a7f0ffdf2c; local vscode-demo 123ad63a345dd77ceb0d75aed4c8eda244cf1288 (clean, intentionally unpushed). Open consolidations remain WebScene #76085bba760fa571c8f08ea866dc5dd1ec27c4d376, AppScene #65ce66ef6ceb776b3f14e129f853bfc08b5c5e608c, and vscode-demo #1; do not merge them. One-agent mode is active.
#799/#806 adds pointer identity, capture, and cancellation required for coherent touch/pen activation, but does not itself qualify keyboard navigation or native accessibility exposure. Exact AT-SPI/UIA/macOS semantics, focus restoration, pointer/keyboard parity, screen-reader behavior, package lifecycle, and cross-RID accessibility evidence remain open.
Parent epic: #227.
Related platform roadmap: SceneTech/AppScene#30.
Problem
Visual parity does not prove accessibility. The Code OSS release needs an explicit contract for DOM/ARIA semantics, native accessibility exposure, keyboard traversal, focus restoration, live regions, high contrast, and reduced motion across dynamically added and removed panels.
Investigation first
Inventory the unchanged workbench accessibility tree and keyboard flows in Chromium, then capture the WebScene DOM/ARIA state and AppScene native accessibility exposure for the same states. Map each missing role, name, state, relationship, action, live announcement, focus transition, or hidden-subtree rule to the owning layer. Link focused CSS visuals to #255 and do not duplicate its forced-colors/focus-ring work.
Scope
Editor, activity bar, side bars, trees, lists, tabs, menus, dialogs, Command Palette, Settings controls, terminal, Problems/Output, notifications, Markdown/webviews, Chat, file pickers, status bar, and panel layout changes.
Acceptance
Roles, accessible names/descriptions, value/state, levels/positions, ownership/controls relationships, selection, expansion, and disabled/read-only state match the accepted Chromium oracle.
Tab, arrow, shortcut, escape, type-ahead, and focus-trap/restore paths work without pointer input.
Hidden/detached/content-visibility nodes do not remain actionable; dynamic rows and panels expose stable identities without stale native peers.
Live regions announce deterministic terminal/problem/task/chat test events once and in order.
AppScene macOS snapshot peers #182/#188 and semantic delta child #198/#199 are merged through 7779cba5bb4cabbf9adb41600b75e62fd1dc592f. The delta consumer applies capped operations transactionally on the Cocoa main thread, checks every generation boundary, preserves surviving semantic-ID peers, and recovers with a full snapshot.
Windows UIA projection #200/#201 and COM host bridge #208/#209 are merged. Linux AT-SPI projection #204/#205 and macOS action/live #206/#207 are merged; the Linux #185 action/live controller is active. Real platform hosts and packaged assistive-technology gates remain open. Keyboard, native assistive-technology, nested-webview accessibility, package, performance, memory, lifecycle and unchanged-product acceptance remain open.
Only git diff --check ran in the latest implementation wave; authored regressions and runtime gates remain unexecuted.
The cumulative accessibility gate should compare stable semantic identities and native peer counts across initial/hide-detach/restore states, require exactly-once ordered live announcements, and report explicit pass/fail/skipped/unavailable totals with exact revisions. This avoids duplicating CSS behavior or visual oracle machinery here.
Cross-layer audit at WebScene e33fdbc6 / AppScene 50da4995 proved the first missing accessibility implementation boundary: WebScene exports preferences but no lossless semantic tree ABI, while AppScene paint commands cannot recover roles/names/states/relationships/actions. A bounded generation-stamped read-only semantic snapshot lease for top-level and nested documents is now active as the prerequisite; AppScene #30 platform peers follow. Only diff-check will run in this implementation wave.
Current accessibility checkpoint — 20 September 2026
Exact merged heads: WebScene
a46b62e14eb197603f7e227c1558afb9088633b0; AppScene97702daeb9ad71341ced7226f0aa966dc77ea53c; unchanged Code OSS645f29cc3176500b4b5762ba887cf2a7f0ffdf2c; local vscode-demo123ad63a345dd77ceb0d75aed4c8eda244cf1288(clean, intentionally unpushed). Open consolidations remain WebScene #76085bba760fa571c8f08ea866dc5dd1ec27c4d376, AppScene #65ce66ef6ceb776b3f14e129f853bfc08b5c5e608c, and vscode-demo #1; do not merge them. One-agent mode is active.#799/#806 adds pointer identity, capture, and cancellation required for coherent touch/pen activation, but does not itself qualify keyboard navigation or native accessibility exposure. Exact AT-SPI/UIA/macOS semantics, focus restoration, pointer/keyboard parity, screen-reader behavior, package lifecycle, and cross-RID accessibility evidence remain open.
Parent epic: #227.
Related platform roadmap: SceneTech/AppScene#30.
Problem
Visual parity does not prove accessibility. The Code OSS release needs an explicit contract for DOM/ARIA semantics, native accessibility exposure, keyboard traversal, focus restoration, live regions, high contrast, and reduced motion across dynamically added and removed panels.
Investigation first
Inventory the unchanged workbench accessibility tree and keyboard flows in Chromium, then capture the WebScene DOM/ARIA state and AppScene native accessibility exposure for the same states. Map each missing role, name, state, relationship, action, live announcement, focus transition, or hidden-subtree rule to the owning layer. Link focused CSS visuals to #255 and do not duplicate its forced-colors/focus-ring work.
Scope
Editor, activity bar, side bars, trees, lists, tabs, menus, dialogs, Command Palette, Settings controls, terminal, Problems/Output, notifications, Markdown/webviews, Chat, file pickers, status bar, and panel layout changes.
Acceptance
Proposed PR stack
Implementation checkpoint — 19 September 2026
WebScene's bounded provider sequence is merged: full snapshots #541/#542 at 9afd161; actions #545/#553 at b386936; live events #546/#558 at a48ce70; deltas #547/#564 at 7fa7dac.
AppScene macOS snapshot peers #182/#188 and semantic delta child #198/#199 are merged through 7779cba5bb4cabbf9adb41600b75e62fd1dc592f. The delta consumer applies capped operations transactionally on the Cocoa main thread, checks every generation boundary, preserves surviving semantic-ID peers, and recovers with a full snapshot.
Windows UIA projection #200/#201 and COM host bridge #208/#209 are merged. Linux AT-SPI projection #204/#205 and macOS action/live #206/#207 are merged; the Linux #185 action/live controller is active. Real platform hosts and packaged assistive-technology gates remain open. Keyboard, native assistive-technology, nested-webview accessibility, package, performance, memory, lifecycle and unchanged-product acceptance remain open.
Only git diff --check ran in the latest implementation wave; authored regressions and runtime gates remain unexecuted.