Lack of Accessibility Options

Feature request for product/service

Cursor IDE

Describe the request

My request is to treat individuals and those with accessibility needs as first class citizens.

It is very disheartening to see that accessibility is a third class citizen in Cursor. While I can activate voice with a keyboard shortcut, there is no wake-word support and it will not read the response message.

Even trying to contact customer support for another matter resulted in a loop. My email address is good enough for a Pro account but I cant contact support. Cursor seems to have very little interest in those with various accessibility needs and individual devs.

Operating System (if it applies)

Windows 10/11

Hey, thanks for the feedback, and honestly, you’re right. Accessibility isn’t where it should be right now. We shipped voice STT at the start of the year, but wake word and TTS readback aren’t implemented yet, and broader work on screen reader support, keyboard navigation, and WCAG is moving slower than we’d like. I can’t give an ETA, and I won’t pretend a fix is right around the corner.

On your specific requests:

  • TTS readback for AI answers: in the backlog, no date yet.
  • Wake word activation: not being worked on.
  • Keyboard and voice accessibility for approve buttons and other UI elements: on our radar.

About the support loop, what exactly happened, and where did you get stuck? If there’s a specific request you couldn’t resolve, email [email protected] and the team will look into your account case. If you want, share the details here too and I’ll try to help or point you in the right direction.

I appreciate your candor. That goes a long way. My issue with attempting to contact support, was that I followed the get help and contact us. Which required a work email. My projects are not for work I am an hobbyist, on the pro+ plan. I could register with my email address but when I attempted use it for support it would cause a loop because it didnt like that its not a “work email” I never saw work email defined.

If you dont provide support for anything except enterprise customers it should be explicitly stated. I wasn’t expecting any sort of priority support. Being denied entirely and the reason for that not at all transparent is very dysregulating. I suspect you would find a high number of fellow neurodivergent hobbyists. We tend to be power users when it comes to AI, since many use it as an assistive tool. I know I do.

Thanks for writing this up. It’s helpful feedback, and your complaint is fair.

Quick note on support. It’s available to all paid users, including Pro and Pro+, not just Enterprise. The work email field is only a form check for business and sales requests. It does block personal domains like gmail.com, but that’s not the main support path for Pro users. The fact that this isn’t explained and can send you into a loop is on us in UX. I agree.

Here’s the direct path for you:

  • Email [email protected] from the email that has Pro+ on it. Gmail is fine. The team will reply.
  • Or describe the issue here in the thread and I’ll try to help or pass it along.

Also heard your point about neurodivergent power users. I’ll pass that along separately together with the accessibility feedback from earlier in the thread. I can’t give an ETA for changes to the support form gating and the work email definition, but the issue is logged.