>, VoiceOver provide only the tools needed to do those tasks that need >modification it expect that the user will still learn the standard MAcOS > >commands for doing a task were these commands exist.
I think Jaws also takes this philosophy too when it is practical. Closing a window - alt+f4 -- works in every app I've tried whether Jaws is running or not You can generally do it via a menu command too, but that's generally app specific. Web browsing - if I'm on a web page which is a 3-column newspaper like layout (nav across the top and down the left side, main page content in the middle, and more navigation down the right side), how would this be without some sort of "modification". Imagine using this kind of site with the Jaws cursor (essentially the mouse cursor). This is basically what VoiceOver gives you right now in a browser, and in fact what Jaws gave you before version 4 or so. To me, this kind of site would be very difficult to use via direct interaction, and if you add dynamic features such as dhtml menus, throw in a data table, and a tree control just for fun, you'll really start pulling your hair out trying to be productive with it. Try it - there are plenty of busy web sites out there, and probably several screen reader/browser combinations to try it on. Comments please. I very well could be missing something here. Its sometimes hard to teach an old dog new tricks... -- Rich ----- Original Message ----- From: "Greg Kearney" <[EMAIL PROTECTED]> To: "General discussions on all topics relating to the use of Mac OS X by theblind" <[EMAIL PROTECTED]> Sent: Friday, April 13, 2007 11:55 AM Subject: Re: Hi The difference between JAWS and VoiceOver is that JAWS attempts to take over the whole function of the OS. YOu do everything in JAWS. JAWS users coming to VoiceOver always wnat to knwo what the VO command to do this or that is. They become frustrated when they are told there isn't a VO command to do something, why? because the MacOS provide a command to do that task and so there is no need for VoiceOver to provide one too. Take for example the task of closing a window. VoiceOver does not have close window command, it does not need one because the MacOS already has the command-w command to do that. So JAWS users are always looking for the VoiceOver commands when much of the routine functions are no VoiceOver commands but MacOS command that exist with or without VoiceOver. This is a fundamental design approach. JAWS takes over the whole computer experience, VoiceOver provide only the tools needed to do those tasks that need modification it expect that the user will still learn the standard MAcOS commands for doing a task were these commands exist. Greg
