Hi: Yup, WE does not usually read that dialog, just locks up. I just ran through some web pages that lock up allot with WindowEyes using JAWS. After navigating through a few of them JAWS reported that Internet Explorer was not responding and had the buttons to close the program. WindowEyes will just lock up and you have to use narrator or another screen reader to close, even to be aware of, that dialog. I have seen WindowEyes lock up like this in other programs as well although not as often and it is likely that if a program has a problem WindowEyes will lock up instead of continuing to work unlike other screen readers. Someone had had a problem like this with some game and found it was that WindowEyes had some kind of threading problem where it locks up if a program locks up and he had to set some priority for either the game or WindowEyes to get around this if I remember. I don't know how to set the WindowEyes threading priority nor the Internet threading priority to test this whether this might at least get the dialog to read - any ideas? Rick USA
_______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com