Actually, the second one (move from window to window, and have vo remember where you were in the previous window already works in most cases, it depends a lot on the kind of application, and the state of voiceover at the time of the switch. I.E. if I'm in preview, and scrolling a pdf document, then I switch to text edit, read a little, (or write a little) then switch back to preview, I merely need to interact with the pdf content again, and I'm right back where I was. Same with switching back to text edit.
What particular problem were you having with this feature?As for the skipping by sentence/paragraph/whatever while in read all mode, I'm not sure that's the point of read all mode. If you wish to read *all* the content on the page, then skipping parts of text isn't exactly reading all, and therefore wouldn't really fit with what the command is suppposed to do. If you want to skip portions of reading, just use navigational keys to move around the text, there are keystrokes for moving vi word, sentence and paragraph. I've never used this method of reading, (with the exception of group mode in safari) so no real experience with how well this method works, but perhaps others could comment. And, as for the configurations based on application, this is something a lot of folks ask for when they're fresh from windows, because that's what they're used to with windows-based screen readers. And, while I admit, a feature like this one might be kind of neat, I rarely find a use for such a feature. It's easy enough to change the vo basic settings such as rate, pitch and volume on the fly using the ctrl-option-command-arrow key combinations that I really don't think it's all that necessary to have a per-application settings capability. OSX isn't like windows in that each and every application requires an entirely new set of graphic labeling files, scripts to move around the screen, and macros to read parts of the screen automatically. A lot of the functionality has been built-in to vo, and honestly, I just dont see a need for that level of configuration, though I'm sure others disagree with me, but honestly, I almost never change my vo settings while using my machine, and don't really see any need to do so. If you have the numpad commander turned on, you can assign a lot of vo functions to your keypad, and thus remove most of the need to configure things separately for different applications. Of course, each person works differently, and I'm sure there's opposing points of view on this topic, so let's ear them folks. I'm curious. Do you in general think we need application-level configurations, and if so, for which options? What would you change from app to app that would require a configuration file for each application you run? Help me out. I've been using vo for over 3 years, and I just don't see this kind of need, but I'm by far generally the exception, and not the rule, so let's discuss this one, and find out what others think.
On Jan 20, 2009, at 9:58 PM, E.J. Zufelt wrote:
Good evening,There are three significant feature enhancements that I believe are necessary in Voiceover. I have sent these requests to accessibility@xxxxxxxxx and would strongly encourage you all to send in a message as well supporting these requests. I would also love it if you could forward this message to any Voiceover users that you know who do not read this list.1. Configuration options that are configurable on a per-application basis.2. The ability to move from one window to another (for example Preview to Mail) and have VO remember where you wre in the original document when you return.3. The ability to skip the current sentence or paragraph while VO is in continual reading mode.Thanks, Everett
