I believe aaron's title now is enterprise compliance or something along those lines. Someone on list looked up his linked in profile. Does enterprise compliance sound like he's working on we?
"the world has been against you from day one, tomorrow's never promised night has just begun, so sing with me we're all fucked" Walls Of Jericho Reeva On May 11, 2017 8:35 AM, "Russ Kiehne via Talk" <[email protected]> wrote: > I saw the following on another list: > > From: Joseph Lee > Sent: Wednesday, May 10, 2017 9:36 AM > To: [email protected] > Subject: Re: [BlindTech] Window Eyes to be phased out > > Hi, > > Speaking from a screen reader developer’s perspective: > > Window-Eyes and Windows 10: compatibility and support matters. Supporting > a Windows 10 release doesn’t involve just source code changes; it is a huge > commitment that requires months of effort and testing. Supporting Windows > 10 not only means incorporating UI Automation changes, but also opens up > opportunities to support universal apps, Edge and related technologies. > Although the classic desktop apps will be supported, the future is > Universal Windows Platform. Until a few years ago apps powered by this > platform were seen as mediocre in terms of accessibility, but that is > changing thanks to advocacy from users and efforts by Microsoft and other > vendors who realized that accessibility is more than compliance (it is also > a marketing opportunity). And because universal apps are UIA universes, > Window-Eyes MUST have firm UIA support and foundations to incorporate > additional materials and workarounds in the future. Why did VFO release a > JAWS 17 build a few weeks ago to fix issues in Creators Update? Because > they had to incorporate UIA changes in Creators Update (which are > numerous). Why do I experience anxiety on a weekly basis? Because I know > that new Insider Preview builds may contain issues that may impact NVDA > users. Thus I second Rob’s claim about future Windows 10 releases and > Window-Eyes. > > Microsoft Edge is a special case. Not only the user interface is > different, how it works internally is also different. Because of what > Microsoft has done, screen reader vendors have rewritten (or are rewriting > or have to rewrite) browser support modules. This is the chief reason why > VFO had to wait until Edge is stable before writing support for it in JAWS. > > In short, Windows 10 and UWP are in a constant flux. Support for Windows > 10 by a screen reader means developers must be willing to adopt to changes > at the earliest opportunity. Because Window-Eyes is in maintenance mode at > the moment (unless VFO wants to shower some love before it retires it), it > is highly unlikely that it’ll be ready in time to support what’s coming in > the fall or in early 2018. > > Cheers, > > Joseph > > -----Original Message----- From: Jim via Talk > Sent: Wednesday, May 10, 2017 1:37 PM > To: CJ &AA MAY ; Window-Eyes Discussion List > Subject: Re: Window-Eyes! > > Good Point! I seriously believe that all these folks that are > supposedly touting the end of Window-Eyes should think about that next > time they quote someone's "blog" or some other supposedly reliable > source. I have no idea on the exact number of Window-Eyes users but I > strongly suspect that it is quite high. How does it compare to the > number of JFW users-I have absolutely no idea. But there is still a > very large number of Window_Eyes users that would be left to hang out > and dry if VFO suddenly discontinued production of Window-Eyes. Keep > this in mind when you read the multiple posts about Window-Eyes demise. > Have a Good 1! de > > <KF8LT><Jim Wohlgamuth>. > > > On 09-May-17 19:40, CJ &AA MAY via Talk wrote: > >> Is this just an urban myth or a fact? Do you actually know that the number >> of Window-eyes users has fallen? >> >> What will kill Window-eyes is the fear of it being discontinued so new >> users >> will not take the risk in future of purchasing it. >> >> >> Alison >> >> burban >> >> >> >> _______________________________________________ >> Any views or opinions presented in this email are solely those of the >> author and do not necessarily represent those of Ai Squared. >> >> For membership options, visit http://lists.window-eyes.com/o >> ptions.cgi/talk-window-eyes.com/wohlggie%40gmail.com. >> For subscription options, visit http://lists.window-eyes.com/l >> istinfo.cgi/talk-window-eyes.com >> List archives can be found at http://lists.window-eyes.com/p >> rivate.cgi/talk-window-eyes.com >> > > _______________________________________________ > Any views or opinions presented in this email are solely those of the > author and do not necessarily represent those of Ai Squared. > > For membership options, visit http://lists.window-eyes.com/o > ptions.cgi/talk-window-eyes.com/russ94577%40gmail.com. > For subscription options, visit http://lists.window-eyes.com/l > istinfo.cgi/talk-window-eyes.com > List archives can be found at http://lists.window-eyes.com/p > rivate.cgi/talk-window-eyes.com > _______________________________________________ > Any views or opinions presented in this email are solely those of the > author and do not necessarily represent those of Ai Squared. > > For membership options, visit http://lists.window-eyes.com/o > ptions.cgi/talk-window-eyes.com/jadedangelpromises%40gmail.com. > For subscription options, visit http://lists.window-eyes.com/l > istinfo.cgi/talk-window-eyes.com > List archives can be found at http://lists.window-eyes.com/p > rivate.cgi/talk-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
