Approval / submit buttons are not accessible to keyboard or OS voice control

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Summary:
Certain action buttons in the UI are not reachable by keyboard navigation and are not exposed properly to OS-level voice control tools. This blocks hands-free use for approving actions and sending messages.

Affected products:

  • Cursor

Observed behavior:

  • Action buttons such as “Run”, “Allow list”, and “Submit/Send” are not reachable with Tab or Shift+Tab
  • They are not consistently discoverable by Windows Voice Access “Show numbers”
  • Voice commands like “Click Run”, “Click Allow list”, “Click Send”, or “Click Submit” do not work
  • In some cases, “Show numbers here” also fails to assign a target to the control
  • As a result, critical actions require a mouse or brittle grid/coordinate targeting

Expected behavior:

  • All actionable buttons should be keyboard focusable
  • Buttons should appear in a logical tab order
  • Buttons should expose a stable accessible name to the OS accessibility tree
  • Buttons should be discoverable and invokable by OS voice-control tools such as Windows Voice Access or macOS Voice Control
  • Dialogs that require approval should move focus into the dialog and trap focus until dismissed

Why this matters:
This prevents reliable hands-free use for users who rely on voice dictation and voice control to operate the application. It affects core flows such as approving agent actions and submitting messages.

Suggested technical checks:

  • Ensure interactive controls use proper button semantics
  • Ensure controls are keyboard focusable
  • Ensure accessible names are exposed, for example “Run”, “Allow list”, “Send”, “Submit”
  • Verify correct UI Automation / accessibility tree exposure on desktop and web
  • Verify focus management in approval dialogs and composer action areas

Steps to Reproduce

Repro summary:

  1. Open a view with a Run / Allow list / Send / Submit button
  2. Try to reach it with Tab/Shift+Tab
  3. Try Voice Access commands such as “Show numbers”, “Click Run”, “Click Allow list”, “Click Send”
  4. Observe that the control is not focusable and not voice-targetable

Impact:
High for accessibility and hands-free workflows, because it blocks completion of essential actions without a mouse.

Expected Behavior

Be able to use voice controls to activate buttons in the UI

Operating System

Windows 10/11

Version Information

Version: 2.6.22 (user setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hi @Jason_Neal,

Thank you for reporting this. You’re right that the approval and submit buttons in Cursor are not properly accessible to keyboard navigation or OS voice control tools like Windows Voice Access. This is a bug on our end.

As a partial workaround, these keyboard shortcuts are available when a terminal command is waiting for approval:

  • Enter — approve and run the command

  • Escape — skip the command

  • Shift+Enter — add to allowlist and run

These shortcuts work without needing to click on the buttons directly. For sending messages in the composer, Enter (or Cmd/Ctrl+Enter depending on your settings) submits the message from the input field.

That said, these shortcuts don’t solve the voice control issue, since tools like Windows Voice Access need proper button semantics in the UI to discover and target interactive elements. We’ve noted this for our team.

If you run into any other areas where accessibility is blocked, please let us know.