test(vscode): enforce scoped webview accessibility coverage

[marius-kilocode]

VS Code webview workflows have screenshot coverage, but it cannot catch regressions in accessible names, semantic relationships, or keyboard operation. The isolated development launch path also forces accessibility support off, leaving accessibility repairs without a durable gate or practical assistive-technology validation path.

This change adds a scoped Playwright and axe accessibility ratchet for stable webview story states, with focused keyboard coverage and a Storybook inspection panel. The scope is intentionally incremental so existing accessibility backlog does not block unrelated work, while repaired workflows can be enrolled as they land. It also adds an accessible extension launch mode that enables assistive-technology validation without changing the default development behavior.

Closes #10673

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Overview

All 2 issues from the previous review have been resolved in the follow-up commit (ffad65db):

Previous Issue	Resolution
WARNING (accessibility.spec.ts): No initial focus anchor before Tab — flaky test risk	Fixed: new reach() helper loops up to 10 Tabs to locate the target before asserting focus
SUGGESTION (launch.ts): Redundant if (enabled) assignment outside ternary	Fixed: enabled override consolidated into the keep=true spread, eliminating the dead write

Files Reviewed (3 files changed in follow-up)

• .github/workflows/visual-regression.yml — # kilocode_change marker added to two lines; no logic change
• packages/kilo-vscode/script/launch.ts — previous redundant assignment removed; logic is now correct for both keep paths
• packages/kilo-vscode/tests/accessibility.spec.ts — reach() helper added and replaces the single-Tab assumption; previous warning resolved

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-sonnet-4.6 · 279,143 tokens}

_{Review guidance: REVIEW.md from base branch main}

[kilo-code-bot]

Regression-focused subagent review: no blocking regression found in this PR. The scoped axe/keyboard test is wired into the webview visual workflow and avoids making existing untriaged stories block this change.

Non-blocking follow-up: the current ratchet allowlist does not yet include the repaired chat-decision, model-selector, prompt-suggestion, or history workflows addressed by the companion accessibility PRs. Keep the focused interaction specs in those PRs and add their stable fixtures to this axe ratchet as they land so future semantic regressions are caught centrally.