Hey Turret,

Thanks a lot for that tip, I'll definitely give that a try!

Just curious, are there perhaps other editors that work well for writing C# code and are perhaps more NVDA friendly?

Suppose I should have said this in my first post, but I really couldn't care less if the tools I'll end up using for this are the official Microsoft ones or 3rd-party solutions that might work better with NVDA, I'm really just trying to figure out what would work best in my situation.

Sure, it would be sweet if I could have everything in one package (code editor, access to API docs, compiler / debugger, GIT support), but I'd also be perfectly fine with, say, compiling or pushing to GIT from the command line.

I know this will definitely result in a steeper learning curve but hey, if it means I'll end up with a more usable experience, I wouldn't mind at all.

Thanks!

Robin

@3
I've heard of EdSharp working well for people, though haven't used it myself so can't really say.
That's the thing about native languages like C#, or Swift on Mac. It ties you to the tools given. Microsoft hardly documents the .NET CLI stuff, and Apple is even worse about it. And if the GUI breaks...

Looks like I'm the only one here that doesn't have any major issues with VS 2019. IntelliSense can be quite dodgy, sure, I know that they are working on it (at least that's what they've said), and the second problem is there's lag when your code runs into compile errors, but other than that It works fairly well for me. CTRL + Tab is your best friend to quickly jump through different windows, and I recommend disabling file previews so that your files do not automatically popup previews as you are going through them in Solution Explorer. Also, disabling line numbers is a must so that NVDA can report spaces or tab levels. I am not using NVDA addons for it.

You can also try it with Narrator. I believe that's  their primary screen reader that they test with during development.

It's not bad here, IDK why Cross is having that issue, but I still will not use it, as I said, they can, and have, just gone, "What the actual serious fuck is accessibility?" Granted they probably won't as there are blind guys working on Seeing AI / SoundScape, but still.

Hey all,

Thanks so much for the super useful tips and pointers, very greatly appreciated!

I will most definitely try applying all the suggested settings, like turning off previews and line numbers to see what happens, and give the add-on a try to see how much difference it makes.

It's most definitely a shame that there doesn't appear to be good CLI documentation for .Net Framework, as I'm sure that would make life much much easier for us.

The really cool thing about Swift is that the language, compiler and standard library are fully open-source and available on GitHub, so it's always possible to use a 3rd-party editor like TextMate to write code and then compile using the CLI.

Linux support has also come a really really long way, so you could install the Swift compiler on a distro such as Ubuntu, write your code in Emacs or any other editor, and then natively build and run your code - it's even possible to build full featured server side projects using frameworks such as Vapor which you could then either run locally, or deploy using Docker or any of the major cloud hosters.

Sorry for the super OT comment, just wanted to clarify this as I really do enjoy Swift quite a lot as well as the community-driven ecosystem that has developed around the language thanks to it actually being open and relatively intuitive to learn :-).

Robin