Exactly my point. A great example of this with JFW was a few
versions back, though I'm not sure if it is still included in the
latest version. There was a Jaws command to minimize all Windows and
place the focus on the desktop. Windows already provided a command
for this, so including it in Jaws was pointless.
On Apr 13, 2007, at 8:55 AM, Greg Kearney wrote:
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
