Accessibility: Improve screen reader support in kilo-vscode

[kilo-code-bot]

Problem

A customer who uses a screen reader reported issues with the Kilo VS Code extension. Several areas of the extension's webview UI are not accessible to assistive technologies, making it difficult or impossible to use for screen reader users.

Current State

What is covered:

• Core interactive primitives (dialogs, menus, tabs, checkboxes, tooltips, etc.) are built on @kobalte/core, which provides ARIA roles, focus traps, keyboard navigation, and Esc-to-close out of the box.
• Some custom widgets already have proper ARIA attributes applied.

Gaps identified (packages/kilo-vscode):

• Several areas in the extension lack proper accessibility support for screen readers.
• Missing ARIA labels, roles, or keyboard navigation in various components.
• Accessibility coverage lags behind kilocode-legacy in some areas.

What's Needed

A focused accessibility audit and remediation pass on packages/kilo-vscode to:

1. Add missing ARIA labels and roles to interactive and informational elements.
2. Ensure keyboard navigation is complete and consistent throughout the UI.
3. Close the gaps identified relative to kilocode-legacy.

Note: A full internal accessibility audit has been conducted. Reference that audit for the specific component-level findings and prioritized list of gaps to address.

References

• Customer support report: https://app.usepylon.com/support/issues/views/9966ba78-b33f-425c-b8e9-0235c4d7f07d?issueNumber=20456
• Relevant package: packages/kilo-vscode/webview-ui/