I'm trying to use expression web 4. Window Eyes 7.2 wouldn't read much of anything with regard to the setup and installation screens. Actually neither would NVDA, but NVDA would read the "accept" "next" "I agree" buttons. After just going ahead and installing it. NVDA does read the pull down menus: File, edit, view, etc, but Window Eyes does not. When I hit alt, We announces "context opening" or something like that. It doesn't even read file, edit, view, etc. Then as I arrow up and/or down, it reads Open if on the file menu. But it acts like it's stuck on that first menu item; however as I continue to arrow down, I know I am crossing other menu items because NVDA does read them, but WE only says the first item when I hit the speak summary hotkey. As I arrow down, WE is silent, but if I hit the speak summary hotkey, WE only constantly reads the first item I crossed by me using the speak summary hotkey to check to see which item I am on. If I hit alt and am on the file menu, if I arrow up, WE will tell me I'm on the exit menu item, but again, it remains stuck on that item no matter if I arrow up or down.
If I'm so blessed to be able to hit alt and then right arrow with lightening fast speed twice over to view, WE will always say I'm on the view menu. In that case, it won't even report the first item under the view menu after I hit the down arrow key. It may read the first thing under the edit menu as I arrow to the right. But again it only recognizes that one item arrowing down. I don't even have time to arrow through the menus. Window Eyes doesn't seem to give me time to arrow over to the view, format, and insert menus, but NVDA does, and NVDA recognizes all of them. NVDA says "collapseable" on some of the menu items. I just wanted to give the scripters and expert WE users as much info as I could. Expression Web 4 uses the .net 4 extended framework. I know it must not use standard menus, so is there a script out there that makes these menus accessible? I used the msaa detective script and found out that they do popup though. That's an interesting script. What can I do? I don't know NVDA well enough, and I would really rather use WE anyway. If much of MS Office is accessible, why wouldn't this program be.? As a nonscripter yet, how would I break down the steps necessary to create a script like whether or not a program is going through msaa or is communicating by some other means? I know these are a lot of questions, so I really appreciate the feedback and the time taken to answer these questions. Much thanks as always, Andre If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
