That's right. I also reported this problem and hav been told that it'll be
looked at.
When I saw it hadn't, I decided to take action and modified the visual
studio nvda addon to fix this. I still think there's a lag when arroing
through the suggestions, but it works for me.
If anyone needs the addon, let me know.
-----Original Message-----
From: Ian Reed
Sent: Friday, June 7, 2019 4:13 AM
To: program-l@xxxxxxxxxxxxx ; Dante Gagne (Redacted sender danteg for DMARC)
Subject: [program-l] Re: vs 2017/2019 c# intellisense suggestions is not
read by nvda anymore
Sorry if I've missed an update, but last I heard, (and tested)
intellisense in Windows 10 with VS 2017 or VS 2019 and NVDA was reading
the entire line before it would read the selected intellisense item.
This makes it pretty close to unusable.
Then of course there was this email thread I am responding to that says
it stopped working entirely.
Now I just saw an new email asking about the preferred way to present
Intellicode items.
Just wondering, has the issue with NVDA reading the entire line before
each intellisense item in VS 2019 been fixed?
What about the issue with intellisense not reading whatsoever in VS 2017
and 2019?
Worrying about how intellicode is presented seems premature if either of
these issues have not yet been resolved.
Also, last I checked, in Windows 7, VS 2017 intellisense doesn't speak
at all in NVDA.
I'm sure nobody even checks the accessibility of new versions of VS in
Windows 7 anymore, based on the below email, it is apparently hard
enough just to keep accessibility working in the latest version of the
OS, but just thought you should know.
I've been programming full time in C# since 2004 (only lost my vision in
late 2010), and I still use VS 2010 on Windows 7, because last time I
tried to upgrade to VS 2017, intellisense didn't work at all.
Also, NVDA does not read anything from the VS 2010 texte editor in
Windows 10. Not sure why the exact same version of VS is entirely
inaccessible in Windows 10, but works fine in Windows 7.
I get that I am using an old VS, so can't expect anyone to check why an
old VS works fine in Windows 7 but not Windows 10, but how am I supposed
to upgrade to VS 2019 if intellisense is still broken?
And I certainly can't rely on new versions of Visual Studio working in
Windows 7, as is apparent with VS 2017 intellisense breaking permantly
in Windows 7 with a VS update.
Upgrading is difficult, since staying on Windows 7 and upgrading VS
gives me broken intellisense, and upgrading to Windows 10 but staying on
VS 2010 gives me a broken text editor.
Upgrading both at once is more challenging, but perhaps I would be up
for it if VS 2019 on Windows 10 actually held the promise of working
intellisense in NVDA.
It seems weird, but I feel much safer in Windows 7 and VS 2010, where
Windows 10 updates cannot break my intellisense, and VS 2010 no longer
receives any updates.
I probably sound like an old man, using older products, but mostly I
just like basic features such as intellisense to consistently work, not
break randomly with an update to either the OS or the IDE.
I don't even need a lot of features to work consistently, as evidenced
by my continued use of older products, which most would say had plenty
of their own accessibility issues.
I really do appreciate that there are people at Microsoft who care about
accessibility, especially in the VS division.
So thank you Dante, and Allison, for trying.
Good luck to you, and let me know if you think you get to a point where
intellisense actually reads properly in NVDA, and will continue to do so
going forward.
Then I think I'd love to upgrade to VS 2019, take advantage of some
newer C# language features, and actually care about how intellicode
items are presented.
~ Ian Reed
On 5/2/2019 10:16 AM, Dante Gagne (Redacted sender danteg for DMARC) wrote:
The regression is related to a Windows update to .NET Framework 4.8. Here's the details:
For VS 2017, we have a fix in the works that should release in the next week or two.
For VS 2019, there is an update coming either next week or the week after if you need to stay on Update 0 (GA), or you can update to VS2019 Update 1 which should be available next week and that should fix the issue.
You can either use the latest Update 1 Preview which is available now.
I'm really sorry about the hassle, and thankfully, our fixes should be out next week... which is unfortunate for folks who are using it THIS week.
--Dante
-----Original Message-----
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf Of gozaltech
Sent: Wednesday, May 1, 2019 6:44 PM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] vs 2017/2019 c# intellisense suggestions is not read by nvda anymore
hello all.
from yesterday, for some reason nvda stopped reading intellisense suggestions of net editor in vs 2017/2019.
i've tried to reinstall them, but nothing improved.
do you have any advices how to return intellisense accessibility back?
thanks.
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
