There are a couple of things here.
First, what do you mean by console mode?
There is a console in OSX, but I doubt it's what you're intending, it's more for logs and things which wouldn't apply in windows. If you mean the command line, then terminal is what you're after. Be advised that terminal does not speak automatically, and extensive vo navigation is necessary to use it. However, once you get used to it, it's quite usable.

Second.
There is no voice over for jaws users, because it would be a meaningless document. There really isn't anything from jaws you can apply to voice over, because of their completely different approaches to screen review. That's similar to asking where's the using jaws for windows guide for folks switching from artic vision's dos screen reader. Not much point to it, since they're completely different environments, programs, and access methods. Any comparison would be minimal at best, and wholely confusing at worst.
There's really no help for it.
To use voice over, you really have to approach it from a starting from scratch point of view, since there's no direct comparison to be made. This is the first thing I always tell windows users. Forget what you know about screen readers, and jump in head first. It's a trial by fire sure, but when you're done, you'll be considerably better able to handle the mac than you will if you approach it with a windows mindset. That won't do any good, and will really only hold you down, and prevent you from getting the full functionality of vo. I can't stress this enough, and it's something that isn't even mentioned in any documentation I've seen. It needs to be stated, loud and clear, and repeated often during the training of vo users. Don't try comparing it to windows, because it won't help, and will only cause confusion. That's why Gab's comments about jaws experts. Your knowledge of jaws won't help in this context. A windows eyes or hal expert would have the same problems, so it's not a slam on jaws by any means.

Reply via email to