Hi Manish, I wish I had a Silverlight fruit basket to post, but no one has developed one yet, as far as I know. If that is something you could do, I think it would be a valuable contribution to the community. As you may know, the criteria for a fruit basket program is available on http://FruitBasketDemos.org and you can post a solution there as well. Cheers, Jamal On 3/19/2011 7:04 AM, Manish Agrawal wrote: > I’ve recently worked on several Silverlight projects and did get basic > support from jaws. Textblocks are all read properly in the virtual > buffer – combo boxes and list boxes are all useless. Jamal posted a > Silverlight example on the web…I don’t seem to remember but I guess you > could look in the list archives. The apps I was working on were all > internal to various organizations. > > As for this app, I don’t have the option of changing the textblocks. > > -Manish > > *From:*program-l-bounce@xxxxxxxxxxxxx > [mailto:program-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Travis Roth > *Sent:* Saturday, March 19, 2011 1:04 AM > *To:* program-l@xxxxxxxxxxxxx; jawsscripts@xxxxxxxxxxxxx > *Subject:* [program-l] Re: UIA - WPF and textblocks > > Hi Manish, > > You have gotten Silverlight to work with JAWS? I have never seen this > work, is there a working example on the web? > > As for the textblocks, my advice though not entirely elegant, is to use > a textbox that allows the control to be in the tab order. > > Static text has always been problematic in applications, but in the past > you could use the JAWS cursor to roam around the screen. But with > MSAA/UIAutomation JAWS does not seem to build an off screen model, so > the JAWS cursor is not useful. So JAWS reads where the tab order goes. > > I suppose if this is not an option, a JAWS script could be tried to have > it access the textblock at the object level and speak it out on demand. > I don’t’ like screen reader specific fixes (e.g., scripting) unless > there is no other way as it is that much more to maintain and also ties > the user to one screen reader. But you sometimes do not have a choice. > > *From:*program-l-bounce@xxxxxxxxxxxxx > [mailto:program-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Manish Agrawal > *Sent:* Friday, March 18, 2011 11:14 AM > *To:* program-l@xxxxxxxxxxxxx; jawsscripts@xxxxxxxxxxxxx > *Subject:* [program-l] UIA - WPF and textblocks > > Hi, > > At work, I am working on creating a WPF application , which is almost > completely inaccessible (as expected) out of the box. > > There are several textBlocks on the screen that present useful > information to the user but are not a part of the tab order and never > get focus. > > Jaws does a fairly good job with these in Silverlight where it loads > everything in a virtual buffer. However, with a WPF app, jaws doesn’t > pick up anything at all. > > Also, UIA exposes a whole lot of information with grids but none of the > screen readers seem to give me even very basic support for content in > tables, let alone full table support. > > Combo boxes are announced as “combo boxes” and that is the end of it. I > cannot figure out any way of reading the contents and current selection > inside a combo box. > > With NVDA, I am able to get to most of the textblocks and grid cells > using object navigation. Object navigation is however, hardly a good way > of accessing an application as a user and gives very little sense of the > layout of the content on the screen. > > I also tried the demo version of the new window eyes 7.5 (it has UIA > support now) and got results comparable to NVDA but because of lack of > WE’s capability or my lack of practice with that product (not to mention > the very irritating 30 minute limit before re-boot), I couldn’t make > much progress. > > Has anyone done any work on these problems and made any more progress – > specially with jaws or any other screen reader? > __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts