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.
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.