microsoft / microsoft/vscode-documentdb
Table Is Not Accessible Using the Keyboard: A11y_DocumentDB for VS Code Extension_Keyboard
@tnaum-ms is already working on this.
Since Aug 18, 2026.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 22
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 21
Description
GitHub Tags
#A11yTCS; #A11yMAS; #A11ySev1; #DesktopApp; #FTP; #Win32; #DocumentDB for VS Code Extension; #SH_DocumentDB_Win32_NOV2025; #WCAG2.1.1; #Keyboard;
Environment Details:
Application Name: DocumentDB for VS Code Extension
Version 0.6.0
OS: Windows 11[Version 23H2(OS Build 22631.3593)]
Repro Steps:
- Open VS code
- Install the DocumentDB for VS Code Extension and open it
- Navigate to the DocumentDB Connections area.
- Click the New Connection action.
- Select Connection String as the connection method.
- Paste the connection string when prompted.
- Choose to authenticate with username/password and enter the credentials
- Confirm to create the connection.
- Locate the desired cluster in the DocumentDB Connections list.
- Expand the cluster entry to initiate the connection.
- Expand one of the databases under the cluster.
- Expand a collection within that database.
- Select the Documents item for that collection.
- Collection View will open
- Observe the issues Table Is Not Accessible Using the Keyboard
Actual Result:
Table Is Not Accessible Using the Keyboard
Expected Result:
Ensure users can navigate through table rows and columns using the Tab key to move between cells and the Arrow keys for finer navigation within the table.
User Impact:
Users relying on keyboard navigation cannot interact with or navigate the table's content effectively. This creates significant usability issues for individuals with motor disabilities or those who rely solely on keyboard input.
Attachment
https://github.com/user-attachments/assets/38d17568-3618-4008-babf-042f6762dd26
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.