E-mail List Archives
Re: VS.NET 2017 inaccessible Installation UI
From: JP Jamous
Date: Aug 8, 2017 5:38AM
- Next message: Sarah Ferguson: "Re: Trying to find middle ground with a developer"
- Previous message: Ben Regis: "Re: Trying to find middle ground with a developer"
- Next message in Thread: J Isaac: "Re: VS.NET 2017 inaccessible Installation UI"
- Previous message in Thread: Jim Homme: "Re: VS.NET 2017 inaccessible Installation UI"
- View all messages in this Thread
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.
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jim Homme
Sent: Monday, August 7, 2017 8:31 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] VS.NET 2017 inaccessible Installation UI
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 REMOVED>
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O
From: JP Jamous<mailto: <EMAIL REMOVED> >
Sent: Sunday, August 6, 2017 9:52 PM
To: 'WebAIM Discussion List'<mailto: <EMAIL 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
- Next message: Sarah Ferguson: "Re: Trying to find middle ground with a developer"
- Previous message: Ben Regis: "Re: Trying to find middle ground with a developer"
- Next message in Thread: J Isaac: "Re: VS.NET 2017 inaccessible Installation UI"
- Previous message in Thread: Jim Homme: "Re: VS.NET 2017 inaccessible Installation UI"
- View all messages in this Thread