We made over 1,700 improvements and still have some work to do, but if you are using Visual Studio 2017 in a low-vision or no-vision mode, a lot has improved.
Dante has a blog post on everything we’ve done and what’s more to come, but here I’ll call out a couple of the more major things we’ve improved. The VS editor’s text adornments let developers know about features available at particular points on a line of code, such as breakpoints, lightbulbs, and error and warning “squiggles.” Customers can now discover and navigate between these adornments via the new “Show Line Annotations” command set, which you can find on the editor context menu.Debugger windows like the Call Stack, Locals, Autos, and Watch windows were inaccessible to screen readers. A crash that could occur when compiling a local function in C#.A crash in C# or VB projects when malformed metadata is encountered in the code file.A race condition when debugging C# or VB projects that could cause Visual Studio to crash when ending the debugging session.A crash that could occur in C# and VB projects when editing linked files, files in Shared Projects, or files used in projects targeting multiple runtimes.Here are some of the more notable ones that had high votes that we fixed: In addition to accessibility, we have many fixes for reliability issues to improve performance, many of which you reported through report-a-problem.
0 kommentar(er)
