Hi: Since you are in a time crunch call them on the phone to get tickets. As for diagnosing the WE problems You might try ctrl-shift-w to read the window when you get an error or try hitting it twice if that doesn't read everything. To read what is going on with WindowEyes if you are getting errors you might also be able to read the WE message using the mouse - sometimes that works, sometimes not. WindowEyes does not display messages in a particularly screen reader friendly window so trying to read them is sometimes not the easiest thing to do. Usually the ctrl-shift-w will read what is there but I forget how you can read it like one character at a time if it is confusing hearing everything all at once. If you try to run nvda or jaws to read these messages you need to run both WindowEyes and the second screenreader at the same time or you wont get the WindowEyes errors in the first place. Good luck and hope you are recovering well. 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
