E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 4 (In chronological order)

From: JP Jamous
Date: Sun, Aug 06 2017 7:52PM
Subject: VS.NET 2017 inaccessible Installation UI
No previous message | Next message →

Has anyone on this list run into zero accessibility with the Visual Studio
.NET 2017 Community edition installation screens?



I have tried the installation on Windows 10 Pro in a virtual machine. JAWS
18 only announces the window title. Nothing else is announced on the screen
where to select the components to be installed or the next screen after
that.



I was not sure if JAWS 18 is lacking certain features to interact with this
UI. I noticed that in my virtual machine JAWS 18 OCR is not installed due to
lack of video drivers.



I would like to know if anyone faced such an issue on a real physical
machine. Either way, the UI should be keyboard accessible. Microsoft cannot
brag about accessibility and disregard this main factor in its application.



---
This email has been checked for viruses by AVG.
http://www.avg.com

From: Jim Homme
Date: Mon, Aug 07 2017 7:30AM
Subject: Re: VS.NET 2017 inaccessible Installation UI
← Previous message | Next message →

Hi JP,
You might want to ask this on program-l.

Thanks.

Jim

=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

From: JP Jamous<mailto: = EMAIL ADDRESS REMOVED = >
Sent: Sunday, August 6, 2017 9:52 PM
To: 'WebAIM Discussion List'<mailto: = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] VS.NET 2017 inaccessible Installation UI

Has anyone on this list run into zero accessibility with the Visual Studio
.NET 2017 Community edition installation screens?



I have tried the installation on Windows 10 Pro in a virtual machine. JAWS
18 only announces the window title. Nothing else is announced on the screen
where to select the components to be installed or the next screen after
that.



I was not sure if JAWS 18 is lacking certain features to interact with this
UI. I noticed that in my virtual machine JAWS 18 OCR is not installed due to
lack of video drivers.



I would like to know if anyone faced such an issue on a real physical
machine. Either way, the UI should be keyboard accessible. Microsoft cannot
brag about accessibility and disregard this main factor in its application.



---
This email has been checked for viruses by AVG.
http://www.avg.com

From: JP Jamous
Date: Tue, Aug 08 2017 5:38AM
Subject: Re: VS.NET 2017 inaccessible Installation UI
← Previous message | Next message →

Thank you Jim. I already filed a bug with Microsoft. I'll inform this list if the problem is resolved. It seemed like the UI did not have any keyboard access. Once a sighted help was applying the clicks JAWS was announcing the check boxes and buttons.

After I loaded the UI, JAWS worked fine with it. There were no issues.

From: J Isaac
Date: Tue, Aug 08 2017 9:04AM
Subject: Re: VS.NET 2017 inaccessible Installation UI
← Previous message | No next message

JP,

Just Out of curiosity, I installed VS Community on a Win 10 standalone machine. When using JAWS focus seemed to get stuck on certain buttons. I muted JAWS, and started NVDA. Tabbing seemed to resolve the navigation issue. After closing NVDA and restarting JAWS, progress and navigation seemed to announce ok.

This is a rich interface containing a lot of information. There were times, where I thought I was stuck, but the interface is slow due to the amount of elements on screen and amount of data being added to the hard drive. Nonetheless, the interface is a bit quirky, and I could see how configuration could affect the screen reader's interpretation. Throw in a VM, and the complexity and quirkiness could increase.

Hope this feedback helps.

== J