We don't consider accessibility a number's game: accessibility has to be included no matter what. The question is when and how within the whole set of relevant accessibility scenarios. I'm not expecting anyone in the product team to argue against adding an option to activate audio in server SKUs during installs, but I'm expecting them to be interested in what should come first: should we focus on more accessible automation first, or should accessible WinPE take precedence? And yes, we should work on both, but in which order? Everything has a roadmap and a list of priorities. We do not stack rank accessibility features against all the issues and priorities because that would lead to the slippery slope you point out. But I believe it makes sense to prioritize accessibility features and issues among themselves. Does that make sense? Gianugo -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kelly Prescott Sent: Friday, December 23, 2016 6:35 AM To: 'Blind sysadmins list' <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update Katherine, I agree with you. We start down a slippery slope when we say that access doesn't need to be included because it only will be used by a few. I hear this all the time from people... "You are the only blind person we know so it is not worth the trouble/expense/time...." Just my $0.02. Kp -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Friday, December 23, 2016 8:02 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update Then there needs to be a way for us to toggle the audio service enabled at OOBE ... because in my opinion, not having it enabled, or at least available to enable via a keystroke, really defeats the purpose of having the talking PE experience to begin with. Yes ... you've probably figured how opinionated and passionate about this I am ... LOL ... thanks for checking this out, though! -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart via Blind-sysadmins Sent: Friday, December 23, 2016 12:01 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Cc: Ryan Shugart <ryshugar@microsoft.com> Subject: Re: [Blind-sysadmins] Windows 10 creators update Hi Katherine: I just wanted to update you on your question, I did reach out to some of the Narrator team and asked about server SKUs. The short answer is yes, the releases of Windows Server 2016 based on the creater's update of Windows 10 will have the talking Windows PE based install. I still believe that as soon as you boot into the actual Windows Server OS for the out of box experience, the Windows Audio service will be disabled and you won't have speech for that part of setup. I did raise this feedback so we'll see how far it goes, but to be honest in an enterprise environment, most companies have automated ways to set their servers up. Many servers don't even have sound cards, although I do understand that could be worked around easily with a USB headset, so that argument doesn't go too far. Most of the people I know either used an automated setup to install Windows Server, or they'd be using something like ILO on HP servers to install the server remotely anyway. I'm not saying the fee dback and issue isn't important as it is, just saying that its not common to do an interactive setup of Windows Server at the server console. Ryan -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Saturday, December 17, 2016 2:32 PM To: 'blind-sysadmins@lists.hodgsonfamily.org' <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Windows 10 creators update Hi all, Can anyone speak on whether the supposed integration of Narrator with the installation/setup/PE process will also extend to server operating systems? Nothing about said integration was mentioned in the blog post, though you would think that something could be done about it ... if one side of an interface is accessible, then all sides of it ought to be. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.hodgs onfamily.org%2Flistinfo%2Fblind-sysadmins&data=02%7C01%7Cryshugar%40microsof t.com%7C7af675a1fae444128c3608d426bbd74d%7C72f988bf86f141af91ab2d7cd011db47% 7C1%7C0%7C636176035589573968&sdata=gaRsK9BLoN9ilJFEqFm%2BxWmlcNsaBne1uyFy%2F exXtcE%3D&reserved=0 _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.hodgsonfamily.org%2Flistinfo%2Fblind-sysadmins&data=02%7C01%7Cgianugo.rabellino%40microsoft.com%7C94276fe181dd4ec3777a08d42b410184%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636181005584226631&sdata=4N50Znfp88XmZDDoH36bC9%2FZXmA%2FNkgve4wsy2x2Xas%3D&reserved=0 _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.hodgsonfamily.org%2Flistinfo%2Fblind-sysadmins&data=02%7C01%7Cgianugo.rabellino%40microsoft.com%7C94276fe181dd4ec3777a08d42b410184%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636181005584226631&sdata=4N50Znfp88XmZDDoH36bC9%2FZXmA%2FNkgve4wsy2x2Xas%3D&reserved=0 _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.hodgsonfamily.org%2Flistinfo%2Fblind-sysadmins&data=02%7C01%7Cgianugo.rabellino%40microsoft.com%7C94276fe181dd4ec3777a08d42b410184%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636181005584226631&sdata=4N50Znfp88XmZDDoH36bC9%2FZXmA%2FNkgve4wsy2x2Xas%3D&reserved=0