Skip to main content


I know many may complain about #NVDASR and its terminal support, But hear me out: It's not as bad as Mac OS.
* On Mac OS, using QuickNav with VoiceOver and reviewing with VO +Control + left and right arrows word by word land you in different parts of the text getting reviewed.
* To select chunks of text to re-paste (such as when Git tells me an exact command to enter), I do: Command+A to select terminal contents, text edit paste it, then find the bit I need to use. (update: use VO+Command+Enter)
This entry was edited (2 months ago)

aaron reshared this.

in reply to Tamas G

of course, this is why screen readers like TDSR exist, because they solve so many of these frustrating terminal quirks. And yes, I've installed it on my work machine too, because working this way (with VoiceOver alone) is not productive. It's at github.com/tspivey/tdsr for those unaware.

Khronos reshared this.

in reply to Tamas G

Still need to figure out how I would go about running that on Windows, is especially useful for SSH.
in reply to Tamas G

I wish I could get this to work. I tried with the wsl post from somebody's blog but just kept running into errors.
in reply to Tamas G

True, however adding Terminal to a flat activity does help things a little bit. Less interacting in my experience
in reply to Tamas G

@fastfinge I will agree with this. In the latest update mac os with Voiceover and terminal has taken a serious accessibility hit.
in reply to Tamas G

FOr copy/pasting, you want VO+command+enter to start, vo+enter to finish. That's only for when what you want to copy is more than a screenful and TDSR doesn't do the job of course.

Tamas G reshared this.

in reply to Mikołaj Hołysz

@miki darn I wish this were listed on Apple's support page, but it's a good tip. (refer to support.apple.com/guide/voiceo…) - and perhaps this is in the command reference somewhere, but at least this solves the text selection issue (although not the output review / quick nav position at a different spot from when reading back through with VoiceOver Cursor.) Still a good tip for selecting if I'm lazy to fire up TDSR and am not running a build.

victor tsaran reshared this.

in reply to Tamas G

IMO "lazy to fire up TDSR" shouldn't be a thing if you're doing anything in Terminal on the Mac. I'd either recommend setting up an alias or straight up making it start up automatically.

I also have an activity set up that silences VO in the terminal automatically, if I actually need it for some reason, I can switch back with VO + x twice.

in reply to Mikołaj Hołysz

VO and most things just doesn’t cut it, honestly. If you want to be able to go beyond basic productivity, good luck. Music creation is an exception, of course, but that’s more down to Logic not being a shitpile than VO.
This entry was edited (2 months ago)
in reply to Mikołaj Hołysz

oooh yeah, I haven't explored VoiceOver activities at all yet, don't really know how those work - but mainly since I spend my work time 90% time coding things in Windows with VS code and then pasting / compiling on Mac only.
This entry was edited (2 months ago)
in reply to Mikołaj Hołysz

@miki I just find that it's a lot of interacting, and I don't get announcements with errors like I do with NVDA or can quickly jump among them with as fluidity as on Windows. Somehow I've always felt more fatigued bouncing VS code around on the mac side.
in reply to Tamas G

With VS Code, you don't want to be doing much interacting, use it like you'd use a Windows app.

It's one of those programs whose keyboard accessibility is good enough on its own that you rarely need Voice Over's help, and the Voice Over cursor slows you down more than it speeds you up in this instance.

in reply to Mikołaj Hołysz

@miki How is VO with VS code now anyways? I remember it doing some odd things, like having a hard time highlighting text because it would start echoing random bits of what you were selecting but I did not use the start/end highlight features or vo+return at the time so that might've been why
in reply to Florian

@zersiax That's gone, it was actually caused by Chromium, as most VS Code accessibility bugs on the Mac are.

Even when the bug was present, you could still use the "start selection" and "end selection" commands (I may be misremembering the names). They're mapped to hotkeys because of this exact Mac bug as far as I know.

They're still useful occasionally, particularly when you want to select and use some code navigation features and/or indentNav.

in reply to Mikołaj Hołysz

@miki Works, but the experience sort of sucks. I just run VS Code in parallels.
in reply to Mikołaj Hołysz

@miki side-note: if there was ever a way to extend Voiceover so it also does intentations using beeps rather than harsh bang sounds / counting them, it may convince me enough to give it more of a fair try - Mac for me ends up being more useful when I'm needing to see code with Braille displays, as it's super seamless to get quickly connected to one over USB.
in reply to Mikołaj Hołysz

@miki ah, so this is why so many peeps have gotten into hammerspoon (and it's automation potential it can provide) - makes sense. Wow, super useful!
in reply to Tamas G

Yes, Hammerspoon is somewhere inbetween AutoId and NVDA addons.

Essentially AutoID / AutoHotkey, but with nice APIs and a sensible programming language.