Hi Anna and Howard, The closest thing I've had to do to the refresh screen action is having to force web pages to reload with Command-R. However, that was for one of two errors. In the first case, there used to be a bug in the underlying WebKit engine for Safari where occasionally the web page elements were not exposed to VoiceOver so you coulddn't interact. This was fixed by making the page reload. (You could read the page by selecting all and starting the Services menu text-to- speech via "Start Speaking Text" or by sending the results to TextEdit -- you just couldn't make VoiceOver interact directly with the page until you forced a reload.) This only happened with certain web pages and when you refreshed the page by forcing it to reload you could interact, etc. That bug was fixed in an earlier version of WebKit and the fix was passed onto Safari at the beginning of this year. Of course, there may still be occasions when a web page hasn't fully loaded and you'll need to force a reload -- but those are the same instances where sighted individuals would find an incompletely loaded web page.
Apart from that, the more likely possibility of a problem you might encounter is when focus behavior gets slightly flakey. This tended to happen when Apple tried to fine-tune focus behavior for more complex VoiceOver interaction models involving other Universal Access functions like sticky keys, mouse keys, or some zoom mode actions. When I did extensive testing of VoiceOver with these actions on first transitioning to Leopard I noticed more quirky focus behavior. This would show up as not being able to tab reliably in iTunes, for example. Usually I would turn VoiceOver on and off again to fix things. I don't think I've ever had to redraw the screen. HTH Cheers, Esther Howard Dupuis wrote: > > This is how it was once explained to me when I was wondering the same > thing: Because Windows screen readers are operating as an overlay and > not as an integral part of the OS, most of them use something called > an off-screen model. What you are hearing is actually information that > the screen reader took from the details being sent to the computer's > screen. Consequently, the screen and the reader can get out of synch > from time to time. Thus, the need to refresh after, to use just one > common example, something pops up on your screen and leaves things a > jumbled mess -- at least in the eyes of the screen reader -- after you > get rid of it .But since VO isn't working that way, refreshing the > screen is unnecessary. At least that's what I took from an > explanation from someone who understands computers -- both hardware > and software -- a whole heck of a lot better than I do. > > Woody Anna Dresner wrote: >> Hi, >> >> Is there a way to have VO redraw the screen as you can with Windows >> screen readers when the screen reader and screen content get out of >> sync? Or do the two not get out of sync because VO is part of the >> operating system? >> >> Thanks, >> Anna > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
