Belated answer to this; I rarely manage to keep up with this list. I'll quote your questions, then answer them. On Thu, Jul 01, 2004 at 08:13:15AM -0400, Mike Paciello wrote: > 1. Does JFW support reading the MSAA PROPID_ACC_VALUE property? JAWS announces accValue on a case by case basis I think, but yes, it does understand and access that property. > 2. In a C# (C Sharp) Application, JAWS is not reading the contents > of the ComboBoxes like it does in C++ Applications. It reads "Zero > Items", when it should read something like "1 of 3". Why is this? I'd like to hear from you directly if you get an answer to this, because mine is a guess. The standard structure for a combo box in MSAA is this (I assume the MSAA docs from Microsoft bear this out; I'm going by what I've seen in the wild more than from my memory of that appendix describing how to implement each control type): Level 1: A Role_System_ComboBox object with three descentants. The descendants can be reached via child IDs 1, 2, and 3, or by accNavigate calls (except that it is common for accNavigate from the Open button to the list not to work when the list is closed, and thus invisible). Per usual for a control, there is actually a Window object wrapping the ComboBox object. Level 2: Three items: a Role_System_Edit object, an Open button, and a List. The list is actually a window object whose client is a list with items under that. The window tends to have the State_System_Floating bit set. I believe it is common for the edit and button objects NOT to be wrapped by a Window object. I don't know if JAWS' handling of combo boxes is based solely on the MSAA structure, but I consider it a decent guess, and thus recommend that developers follow that model carefully. > 3. In a C# ((C Charp) Application with ListBox Controls, JAWS does > not read the Accessibile Name or the Accessible Description when you > enter the control. Is that expected behavior? accDescription is not usually announced automatically by JAWS, but accName is different. I assume you mean accName for the list itself, not the items under it, for which accName is the place to put their contents. accName for the actual list object is its name. I think you're saying JAWS doesn't announce that when you tab to it. Did you perchance try making the actual window name equal to the accName value also? > Finally, we have noticed that JAWS supports the Microsoft Calendar > control (SysMonthCal32), but Window Eyes does not. Or, at least we have > yet to get it to work. Has anyone on this list noticed this behavior on > Window Eyes? And how have you dealt with it. The calendar control is > built into MS Outlook Calendar. I can't answer that one, but it's interesting that you say JAWS supports it. Once upon a time I wrote a set of scripts for that control because I found JAWS' support lacking in a few areas. That was years ago though, and I haven't had to mess with them since. > Thanks in advance for your feedback. To date, we haven't been able to > extract helpful information from any Help, Documentation, Microsoft, > MSDN, or any of the public listservs. I suggest a better list for this type of question, or at least for the ones up to but not including the final Window-Eyes question, would be the JAWSScripts list. I believe there's a link for that at www.blindprogramming.com. I keep up daily with that list, but I think today is the first day in nearly a month that I've looked at this one. The JAWSScripts list sees more programmer types I think. Someone else also suggested Program-L I think, and that's not a bad idea either. Good luck, and I'm glad you came to us to ask how to proceed. -- Doug Lee dgl@xxxxxxxx http://www.dlee.org Bartimaeus Group doug@xxxxxxxxxxxx http://www.bartsite.com No one alive is beyond hope; every second of life is a chance. (08/29/02) -- To post a message to the list, send it to jfw@xxxxxxxxxxxxx To unsubscribe from this mailing list, send a message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/jfw If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list. Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx