Hi Folks, You should stop all these NVDA roomers, it is starting to sound like alternative facts!
Here below is straight facts from the source, NVDA themselves about their future. There are to many people who just do not take the time to do research and go to the source, but spread false statements! Hi Roger, Thanks for your e-mail and encouragement. Firstly, let me reassure your concerns about our future. As an open source project managed by a not-for-profit organisation overseen by a board of directors, it is not possible for us to be bought out. In any case, we have a very strong and committed user base of contributors, and we, in turn, are very committed to them. Well established as the second most popular Windows screen reader, we are definitely interested in continually increasing the number of Braille displays we work with. We are working with HumanWare on the driver for their new device, but I don't have an expected completion date at this stage I'm afraid. Regarding the best way to get around the screen, we do work slightly different to Window-Eyes, however, there are several options which, once you are familiar with them, should get you around most situations: - NVDA has a power Object Navigation feature which allows moving to parts of a window which may be inaccessible via regular navigation commands. The review cursor can then often be used to read the text once a control has been reached. - The Golden Cursor add-on allows moving the mouse with the keyboard and saving positions in applications to jump back to: https://addons.nvda-project.org/addons/goldenCursor.en.html - Windows also has Mouse Keys built in which enables moving the mouse pointer via the keyboard, see: https://support.microsoft.com/en-au/help/14204/windows-7-use-mouse-keys-to-m ove-mouse-pointer for information. In the first instance, I would consider whether Object Navigation can meet the need for a particular application. See the User Guide section on Object Navigation for all the keys https://www.nvaccess.org/files/nvda/documentation/userGuide.html#ObjectNavig ation For more detailed instruction as well as step by step activities, the Basic Training for NVDA training material is a great place to start and comes in a selection of formats: http://www.nvaccess.org/shop/ Kind regards Quentin. On Mon, Aug 28, 2017 at 5:36 AM, Adaptive Information Systems Inc. <aist...@ameritech.net> wrote: August 27 2017 Hi NVDA, I am emailing you to request you support the new BrailleNote Touch from HumanWare as a Braille display. I know Greg Stilson, senior product blindness manager of HumanWare, sent the information out to all screen readers last year of needed information to make their screen readers work with the new BrailleNote Touch android device from HumanWare, but as your latest release, NVDA 2017-3, you still do not support the Touch, Why? I am a vendor of adaptive technology for the past 22 years, and a authorized dealer of HumanWare low vision and blindness products for over 17 years, in Wisconsin, United States, and like what I see in your free screen reader and install it on every computer system I sell as a main or backup screen reader, and I would like to donate but have some reservations! 1. First of all make the BrailleNote touch work as a Braille display with your screen reader now! 2. Since VFO-Freedom Scientific killed Window-eyes as of May 15, 2017, we as blind computer users have only one choice of a full screen reader and that totally sucks big time!! I do welcome your venture as you attempt to be come a full screen reader, but you do have a ways to go to equal to Window-eyes the easiest to use and learn, or Jaws. I would hope you would give us NVDA users a choice to make your screen reader simulate more like Window-eyes, especially as Window-eyes makes it so much easier to move the mouse around with the numeric keypad, unlike Jaws which has 4 different cursers for their numeric keypad and Jaws has over 400 jaws hot keys, while Window-eyes only had 200 hot keys. Also Window-eyes crushed Jaws in supporting dozens and dozens of Braille displays and synthesizers , software and hardware onesoo. Please at least give us a choice of either keyboard layout emulating Window-eyes or jaws, which you seem to emulate strongly like Jaws unfortunately! There are also roomers of VFO trying to buy your screen reader out too, like they have done with many other adaptive companies, since if they offer you a lot of money, you would take it like the others did! I am hoping the NfB or ACB will pursue legal action against VFO for violating the Sherman anti trust law here in the U.S. for having a monopoly! We as vision impaired computers users should have a choice, not limit us to one screen reader, the sighted community would never put up with one choice of a product or service! Thank you for your efforts to create a fully functional screen reader! Regards, Roger A. Behm, President Adaptive Information Systems Inc. We Make Technology Accessible to the vision Impaired and Reading Disabled Roger A. Behm, President 1611 Clover Lane Janesville WI 53545-1388 Fax: 608-758-7898 Voice: 608-758-0933 Email: aist...@ameritech.net Web Page: www.adaptiveinformation.org -- Quentin Christensen Training and Support Manager Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/ Ph +61 7 3149 3306 www.nvaccess.org Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess \ Adaptive Information Systems Inc. We Make Technology Accessible to the vision Impaired and Reading Disabled Roger A. Behm, President 1611 Clover Lane Janesville WI 53545-1388 Fax: 608-758-7898 Voice: 608-758-0933 Email: aist...@ameritech.net Web Page: www.adaptiveinformation.org -----Original Message----- From: Talk [mailto:talk-bounces+aistech=ameritech....@lists.window-eyes.com] On Behalf Of Singing Sparrow via Talk Sent: Monday, September 11, 2017 6:05 AM To: Window-Eyes Discussion List Cc: Singing Sparrow Subject: Re: window-eyes open source? To Be honest with you nvda has a place for people wherejaws will not be able to fill. NVDA does things better thenJaws will ever do. On 9/10/2017 10:50 PM, Dennis Long via Talk wrote: > It is far from being as good as jaws! > > -----Original Message----- > From: Talk [mailto:talk-bounces+dennisl1982=gmail....@lists.window-eyes.com] > On Behalf Of Loy via Talk > Sent: Sunday, September 10, 2017 6:55 PM > To: Window-Eyes Discussion List > Cc: Loy > Subject: Re: window-eyes open source? > > NVDA is not far from being as good as JAWS and I can see it happening that > people will download the free program instead of paying hundreds of dollars > for a very similar program. > ----- Original Message ----- > From: Josh Kennedy via Talk > To: Window-Eyes Discussion List > Cc: Josh Kennedy > Sent: Sunday, September 10, 2017 4:23 PM > Subject: Re: window-eyes open source? > > > Why couldn't it happen? > > > > On 9/10/2017 3:47 PM, Dennis Long via Talk wrote: > > I don't see that happening. > > > > -----Original Message----- > > From: Talk > [mailto:talk-bounces+dennisl1982=gmail....@lists.window-eyes.com] On Behalf > Of Josh Kennedy via Talk > > Sent: Sunday, September 10, 2017 1:08 PM > > To: David; Window-Eyes Discussion List > > Cc: Josh Kennedy > > Subject: Re: window-eyes open source? > > > > I wonder what VFO would do if NVDA starting eating into their business > profits? If free open source NVDA would become way more popular than jaws > and would still be open source? > > > > > > > > > > On 9/10/2017 2:54 AM, David wrote: > >> Matter of fact, this question was raised a couple of days after the > >> anouncement of the discontinued development of WinEyes. I will get > >> back to what Doug said back then. First of all, let's take a quick look > at facts. > >> > >> Had it been as easy as WinEyes would have been a stand-alone software, > >> with all its coding done 'in-house', things would have been pretty > easy. > >> And had it been that Doug and Dan had been the only ones to develop > >> the software, they could have decided whatever they wanted. > >> > >> Things are not that easy! > >> First of all, what doug pointed out, was that to get the better > >> functionality of WinEyes, they had to reach certain agreements with - > >> for instance Adobe - to get access to third-party software, kind of > >> behind the scene. If they open-sourced the code, now these techniques > >> might be disclosed to the public, threatening the products of the > >> third-party manufacturer. In turn, this of course would lead to > >> people, not working on assistive technology at all, to get hold of the > >> key for the backdoor of - say Adobe's reader - and use it for unwanted > >> activity, or even malware development. > >> > >> Secondly, WinEyes had a feature of offering you loads of apps. Many of > >> them are open-sourced, but WinEyes holds a chance for the app > >> developer to cryptize his code, for protecting against peekers. This > >> was a benefit, for instance when the app has to access a server, and > >> maybe even use some login credencials, to perform the activity. > >> Without me knowing for sure, we could think of an app like > >> WeatherOrNot, which has to access a server, retrieve weather details, > and process them for you. > >> Now if the developer has reached a given agreement with the > >> weather-server provider, that his app will gain free access, under the > >> condition of not disclosing the login credencials, we are in trouble > >> in open-sourcing WinEyes. By doing so, we would disclose the > >> cryptizing code, opening up for people to break the cryptized code of > >> the app, get to the credencials, and then misuse it. > >> > >> Part of the agreement GW made with their app developers, by providing > >> the cryptizing feature, was to keep the app code an enclosed program. > >> They might get into legal issues, should they disclose the cryptizer, > >> thereby lay bare the very code of the app developer, who in turn might > >> sue GW for breaking the agreement. This is kind of backed up, by a > >> message Doug posted several years back, when someone claimed they had > >> broken the cryptizer. > >> > >> Furthermore, it has been confirmed from Aaron, that some of the apps > >> directly from GW, like AppGet, do hold credencials for accessing the > >> servers of GW. It is unlikely that they want to have these credencials > >> open-sourced. In particular so, if you remember the attack someone > >> gave them a few years back, when the code of the GWToolkit was hacked, > >> and gave many a WinEyes user quite a shock the morning they turned on > >> their computer, and got a threatening message on their screen. > >> > >> Mind you, GW got into a cooperation with Microsoft, when they > >> introduced the WEForOffice program. Even here, they told that this > >> agreement would put them in specially close relationship with the > >> ingeneers of Microsoft. Who knows what closures might be involved > >> there, and which would be broken, had WE got open-sourced. > >> > >> Now let's move back to the answer Doug gave back in the spring this > >> year. The above is a bit of an elaboration of what he said. You will > >> find his answer in the archives, but in very short terms: > >> NOPE! WinEyes code CANNNOT go open-source; If for no other > >> reasons, due to the infringement of third-party agreements involved. > >> > >> All of this, actually leads me to once again raising the very question: > >> Does VFO even have access to the WinEyes code? > >> VFO might have bought AISquared, thereby also the former GWMicro. But > >> they might not have bought the copyright of the source-code. And > >> perhaps that was never intended either. Seems all they wanted, was to > >> rid the market of any competition, period. Who knows, maybe Doug > >> simply hit the Delete-key, the last thing before he handed in the key > >> for the Office front-door? > >> > >> And to assume that VFO's tech personel would bother to plow the > >> thousands of lines of coding for WinEyes, in hope of hitting the > >> technique used to perform a simple task, is out of range. It would > >> take hours, days or even weeks, to figure why things have been done > >> the way they were. Or, to find the part of a signed contract, that > >> possibly could be renewed in VFO's favor. Far more cost-effective, and > >> resource sufficient, to simply look at the behavior of the WinEyes > >> product, and sit down developing the same bahavior from scratch. Even > >> calling Adobe, Microsoft, AVG, Avast and so forth, asking for a brand > >> new contract. A contract VFO already has in place. So my big guess is, > >> VFO DO NOT NEED the code of the WinEyes screen reader, and never did. > >> They needed the market, and that is what they've currently got. > >> > >> > >> On 9/10/2017 3:01 AM, Josh Kennedy via Talk wrote: > >> > hi > >> > > >> > Is there any possibility since window eyes is no longer supported > >> to get the window-eyes source code make it open source and put it up > >> on the github website? then other developers could keep developing > window eyes. > >> > > >> > > >> > >> > > -- > > sent with mozilla thunderbird > > > > _______________________________________________ > > 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/dennisl1982%40 > gmail.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 > > > > _______________________________________________ > > 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/joshuakennedy2 > 01%40comcast.net. > > 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 > > -- > sent with mozilla thunderbird > > _______________________________________________ > 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/loyrg2845%40gm > ail.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 > _______________________________________________ > 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/dennisl1982%40 > gmail.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 > > _______________________________________________ > 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/sunshine%40abe .midco.net. > 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 > _______________________________________________ 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/aistech%40amer itech.net. 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 _______________________________________________ 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
