Hello Anne and others, Let me first say that if Kevin's issues are resolved no longer seems the general subject of this thread. This is why I jumped in in the first place. Let me first disagree with you on one point Anne. Formatting documents may not be necessary for quick 'n dirty edocument writing, but then neither is iWork. We have our built-in friend TextEdit for that. Often though, at schools, wehn writing letters, essays, assignments, papers, books, readme files, websites, articles, blog posts, ...... it is no bad idea to do some formatting on your text. Headings are certainly important because a lot of screenreaders provide hotkeys to quickly jump from heading to heading. Putting headings in your documents therefore cuts back on a lot of unnecessary reading. Same goes for lists, they may not be very important for us visually impaired people, but they certainly are for people who can see the screen and any eventual print-outs of what you are writing. And this is coming from someone who hates having to adhere to sighted people.
So saying formatting is only for the very professional is just not true. Also, if you come from a Windows world, naturally you are first going to try what works and what doesn't from a windows perspective. This is of course not the way to go, but you do it anyway. Its a basic human response to first try what they are familiar with , even if it is just in your mind. So my initial response would be that there has to be a hotkey to format headings , like shift+ctrl+1 in Windows. If or when i later find out this is in fact not so and that there's quite a bit of work to be done to make one heading appear and i have to make ten, my initial response would be to say ' Fine, i'll do it in Windows because it goes ten times faster'. But to come back on my original point. If his issues are resolved doesn't seem to be important anymore. All i see is people criticizing people who criticize voiceOver, which is imho not right. Look if people are using the mac for their jobs or school and bugs pop up that hamper them in their productivity, I can very much imagine them not cheering and jumping for joy about it. Podcasts like voiceOver On are there to point out these bugs, inform people having the same problems of possible workarounds if they are known, or asking if they are not . They are not in any way to be viewed as some sort of magical law that states that voiceOver is bad. So, if something is demonstrated in one of these podcasts, and the bug is clearly shown for what it is, it makes absolutely no sense at all to blatantly yell ' USER ERROR!' without explaining yourself. Anne did a very good job at this, providing solutions that she is comfortable with. I commend her for that. And I can imagine people being bothered by seeing the same questions over and over. But do everyone a favor and do not respond with useless info if that is the case. You will cut back on list traffic and also on a lot of frustration from the initial poster's perspective. If iWork works well, just say so. Say what is wrong in the assumptions of a post like Kevin's initial one, point out solutions but don't go all ' VoiceOver is holy' because that just doesn't help anyone. Sorry for the long rant but I just see this happen more and more often and I really see no point to it. Florian -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
