Add command to announce the current editor line number via `aria.status`

[meganrogge]

Screen reader users use the go to line command just to hear what line number/column they're currently on.

The fix for #277538 only works when using NVDA. It does work if one arrows down.

@rperez030 and @jooyoungseo have said that a command that announces the current line and cursor position would be nice to have.

We should also add this to our editor accessibility help dialog.

[ahicks92]

I almost made a duplicate issue but funnily enough this is the first search result for "screen reader nvda announce line number" on Google here, even though VSCode is nowhere in that search. Amusing moments that save time, I suppose. With the proliferation of coding agents, this has become super, super valuable. If you want a concrete use case, I used to alt tab over to Claude Code and "in file x at line y..." and now I have to do this whole little runaround.

Arrowing down does not work here as a workaround in the go to line dialog for what that's worth. I have to go far afield to the status bar to get it.

[zuhairmahd]

I can use JAWS's Read Status command (insert numpad 3). Wouldn't mind a dedicated keyboard shortcut though, there are far more critical accessibility bugs in need of fixing, like being able to accept an edit from the accessible view. There is no workaround for that. :-(

[meganrogge]

@zuhairmahd what do you mean? can you describe your steps?

[cannona]

I can use JAWS's Read Status command (insert numpad 3). Wouldn't mind a dedicated keyboard shortcut...

Unfortunately, Insert+End in NVDA says "No status bar found," So this solution won't work for many. That said, this could probably be considered a bug in NVDA.

Edit: Looks like this is fixed and due to be released in NVDA 2026.1.

[zuhairmahd]

@zuhairmahd what do you mean? can you describe your steps?

@meganrogge as others mentioned there is a read status line command in most screen readers which typically assumes it's the bottom line. As others stated that does not work in NVDA but is being fixed. My suggestion is to aim for functionality that builds on what screen readers can do instead of trying to compensate for them. This would allow you to focus on more complex issues (like my Accept Suggestion bug lol) and ultimately have a more robust product.

[meganrogge]

Hey, thanks for that suggestion. I consult with screen reader users that have said this is a good idea @jooyoungseo and @rperez030.

Pls open a separate issue for that separate topic with steps to reproduce @zuhairmahd

[rperez030]

Edit: Looks like this is fixed and due to be released in NVDA 2026.1.

It still wouldn't work with macOS Voiceover or Linux Orca. VS Code uses a non-standard status bar. That's why screen reader developers need to come up with workarounds. Regarding your comment about accepting diffs, I believe there is a way to do it, but I'd suggest discussing that in a separate issue.

[zuhairmahd]

Hey, thanks for that suggestion. I consult with screen reader users that have said this is a good idea @jooyoungseo and @rperez030.

Pls open a separate issue for that separate topic with steps to reproduce @zuhairmahd issue -#267153. :-)?

[cannona]

It still wouldn't work with macOS Voiceover or Linux Orca. VS Code uses a non-standard status bar.

It looks like the Orca devs have also put in the effort to make this work, but it's not a great user experience because, unlike in JAWS and NVDA, the line and column aren't read first. Orca instead just reads the status line as displayed, which means you have to wait for pretty much everything else to be read on the status bar first, before it finally gets to the position info.

Also, just to be clear, as a screen reader user, I'm in favor of this feature being added as well. Even though it's technically doable in some screen readers, that does not mean that it is an optimal user experience. Position information is so often very critical to have ready access to. Anyway, I just wanted to make that clear, since I think someone could be misled by my other comments in this thread. I also don't agree with @zuhairmahd that this is a lower priority issue, and I don't think that accessibility features are necessarily a zero-sum game, where if they add this, they can't fix that.

In fact, if it would be helpful, I'd be more than happy to take a stab at a PR. But I would appreciate any suggestions on what folks feel would be a reasonable default keyboard shortcut, if any?

[meganrogge]

Thanks for offering @cannona . @anthonykim1 is excited to work on this one.