Re: jaws 16 beta: death of screen reader innovation illustrated
One issue with FS is the authorization method. Sure, the client activator is cool, but really? And the locking code? That can be easily cracked? No way! Another issue with FS is that they use incredibly old technology like video display drivers which, in my opinion, suck. Window Eyes, for instance, does not require its video display driver to be attached to operate; it still works perfectly. Although video display drivers are good, they are quite old, and since they're so old, why can't screen readers simply used the already installed video display drivers to read text on the screen? NvDA and System Access can do that. Window Eyes can do that. Why can't JAWS and some of the other companies which use these drivers.
One other thing about VDDs is they slow down performance greatly. That's why JAWS is slow in massive documents in word 2010 and earlier. The VDD has to send text to JAWS manually every time new text arrives and, therefore, slows down the machine
because each line of text is being processed. NVDA works extremely quickly with word 2010, 2007, 2003, 2002, 2013, etc, and has almost no issues with it, while JAWS has lots of them. One of these is the ability to read symbols. It sometimes fails to recognize the symbol list, and just thinks its a graphic which has no navigability. The ribbon also slows things down. Again, the video intercept driver does all of this. This is not JAWS's falt directly; its the old technology that FS uses, old technology that they won't break away from.
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
