Visual Studio for Mac With Voiceover

macOS & Mac Apps

I recently decided to investigate the accessibility of Visual Studio for Mac. All signs point to the application being at least somewhat accessible, but I haven't been able to find any specific pointers. In particular, I'm trying to figure out how to actually interact with the text editor, as everything I try results in the program locking up. Does anyone have experience using this program with VO and can give me any pointers? I'm using the free version, Visual Studio Community, if it matters. Thanks in advance!



Submitted by Joseph Westhouse on Friday, July 27, 2018

Thanks, but that's one of the first things I looked at—before downloading the program, in fact. Basically all that doc says is that you can use basic VO navigation in the program, and can tab between controls. But that doesn't solve my particular issue. Again, I can navigate to the text editor using VO commands just fine, but when I try any method I can think of for interacting with the text (interacting with the editor, VO + space on the editor, etc.) it causes the program to freeze.

Submitted by Mani on Friday, July 27, 2018

Hello Joseph,
I faced the same issues when I tried it some months ago. Now I am wondering if it is worth investing in a cheap Windows laptop just to be able to run MS Office and Visual Studio. Is that a good idea?

Submitted by Joseph Westhouse on Friday, July 27, 2018

If you specifically want to run VS, and if we can't figure out a way to do it on the Mac, a more cost-efficient option would be to run Windows through Bootcamp on your Mac. That's assuming it's accessible on Windows. Personally, I wouldn't buy a separate machine unless I didn't have room on my hard drive for the needed space in a Windows partition. I certainly wouldn't buy a separate m; machine without first confirming that Visual Studio can be used with a screen reader on Windows.

Submitted by Joseph Westhouse on Wednesday, August 1, 2018

No other wisdom from the crowd? This is discouraging. It seems so strange that the text field doesn't act like a text field, and I'm convinced there must be something obvious I'm missing. Ah well. Guess I'll be sticking with VisualStudio on Windows...