Use of native terminal's cursor

[shindere]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

For context, I am running Claude Code under Linux's virtual text console.
I am blind and use BRLTTY to render the content of the screen in braille.
As many screen reading programs, BRLTTY by default uses the terminal's native cursor to decide which portion of the screen to show to the user.
As Claude Code does not use the terminal's native cursor, it is not convenient ot enter prompts as you don't know where your cursor is.
The native cursor remains stuck at the bottom of the screen and, should you want to fix a typo you have no clue where the cursor is.
Ideally, using the terminal's native cursor should be the default but, at the very least there should be a way to configure Claude to do that.
In particular, at the beginning when choosing Claude's configuration, there is no option to make it screen-reader friendly and there would certainly be space for such options, because some features of Claude Code like the use of Unicode characters or the display of ephemeral messages is not so convenient when using a screen reader.

What Should Happen?

See above.

Error Messages/Logs

Steps to Reproduce

Simply run Claude under Linux's virtual console and maybe use BRLTTY.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.80

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. bad terminal hard cursor placement #910
2. [BUG] Accessibility: macOS Zoom caret tracking broken — terminal cursor not placed at text input position #29065
3. Accessibility Issue: macOS Zoom Always Focuses Bottom-Left in Claude Code CLI (Cursor Tracking Broken) #2237

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[shindere]

Yes, it is correct that the present issue is a duplicate of #910, #2237 and #29065. But those have been closed and locked due to lack of activity and #2237 and #29065 actually show that the problem reported by the present issue also occurs on Mac. In addition, I have been told that the same goes for Windows so the problem is really OS-independent and is an annoyance for all users of assisitive technologies, no matter theoperating system or screen reader they are using. Cc @npitre @csabyke @tugberkayartextcortex @fcnjd @yplassiard

[yplassiard]

Hi, I confirm the issue is platform / screen reader independent: I’ve successfully reproduced it on: - Windows using Jaws, NVDA, and Narrator. - MacOS using VoiceOver - Linux using BrlTTY (text mode) and Orca (GTK).

[shindere]

A bunch of thanks for having taken the time to do such a complete testing!

[fcnjd]

@yplassiard Thank you very much for testing, as a user I also confirm to have that problem and would be very happy to see a fix soon.

[Cleversn]

I'm a screen reader user, namely NVDA on Windows, Orca and Fenrir on Linux. This problem affects me as well; please fix.

thanks!

[BFW-Wuerzburg]

I bought claude pro and unfortunately I am also affected by this error under NVDA. I know that many in Germany have already complained about this bug.
It would be nice if the problem with tracking was fixed so that I can continue to use my Claude Pro access.

[devinprater]

I'm a Claude Pro subscriber. Claude is the least accessible AI. Please care about disabled users.

[l3land]

I am a low-vision Claude pro subscriber and this problem affects me on MacOS and Linux (Debian). Please fix this!

[RainerBrell]

I wanted to buy claude pro, but as an NVDA user I also unfortunately have this problem with tracking.
Please improve the accessibility of claude for blind and visually impaired users!

[audiogamer22]

I've tried claud today and while I've not tried the coding part, the accessibility needs to be improved. In firefox if you write a prompt, the screen reader reads the reply very wierdly, it's chopped up and repeated and you can't actually stop it with control. While on microsoft edge there's no heading making navigation very very hard. This is not worth buying if you are a screen reader user.