Change:
Type: <bBug</bcc: Steps to reproduce: VSCode press ctrl+shift+p, choose 'profiles: show content' and press the enter key. navigating the displayed screen using the tab and shift+tab keys. In my environment, every time I press tab or shift+tab, orca just reads something like checked check box. Orca cannot inform what is associated with the checkbox. The problem also happens in version 1.76. VS Code version: Code - Insiders 1.77.0-insider (, 2023-03-15T05:21:59.212Z) OS version: Linux x64 6.1.15-200.fc37.x8664 Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (39)</summaryExtensionVersion ------ doxdocgen1.4.0 vscode-markdownlint0.49.0 vscode-chatgpt3.9.5 rest-client0.25.1 better-cpp-syntax1.17.2 azure-pipelines1.208.0 vscode-docker1.24.0 csharp1.25.4 vscode-dotnet-runtime1.6.0 vscode-kubernetes-tools1.3.11 remote-containers0.284.0 remote-ssh0.99. remote-ssh-edit0.84.0 azure-account0.11.3 cmake-tools1.13.45 cpptools1.14.4 cpptools-extension-pack1.3.0 makefile-tools0.6.0 powershell-preview2023.3.0 remote-explorer0.3. vsliveshare1.0.5834 oracledevtools21.5.0 fabric8-analytics0.3.6 java1.16. vscode-xml0.25. vscode-yaml1.12.1 sonarlint-vscode3.15.1 cmake0.0.17 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 vscode-boot-dev-pack0.2.1 vscode-spring-boot1.45.0 vscode-java-debug0.49. vscode-java-dependency0.21. vscode-java-pack0.25. vscode-java-test0.38. vscode-maven0.40. vscode-spring-boot-dashboard0.11.1 vscode-spring-initializr0.11.2 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
great catch! And thanks for trying out profiles! we should invest into making sure the profile import flow is accessible. It might be as easy as adding aria-labels. We can also sit down together for this.
Tree uses up and down arrows for navigation and I am using the custom tree view underneath. I also see the same behaviour in the PR view. So I assume this has to be fixed in the custom tree view.
is this in ? The checkbox has a that you can set. You can set the and then that should be read by screen readers. The checkbox is still proposed extension API, so before we finalize we would need to also add an aria label:
It turned out perfect, great job. I would like to add two small suggestions that I think would improve accessibility. could be moved to the first field on the page once the page is displayed. Currently, you have to press the tab key a few times to find the beginning of the page. could also have shortcut keys associated with the close and export buttons.
thanks! Could you create a new issue with these suggestions please :)

Discussion:
} else { that.excludedExtensions.add(e.identifier.id.toLowerCase()); } <del> } </del> <ins> }, tooltip: localize('exclude', "Select {0} Extension", e.displayName || e.identifier.id) </ins> } : undefined, command: { id: 'extension.open',

this.roots = await this.fetchRoots(); for (const root of this.roots) { if (this.canSelect) { <del> root.checkbox = { isChecked: true }; </del> <ins> root.checkbox = { isChecked: true, tooltip: localize('select', "Select {0}", root.label.label) }; </ins> } else { root.checkbox = undefined; }