assistive reading technogies don't read the content pane

[chrisjoseph]

While using the keyboard for navigation in HTML5 output, assistive reading technologies like JAWS/ZoomText are not able to read content from the content pane. They do go to the hyperlinks in the content pane by pressing the TAB key, but don't really redy the content.Has anyone faced such issues before. Were you able to rectify it? Note that using the mouse, this works perfectly well, but not using keyboard. Steps followed

Press TAB multiple times to go to the required TOC entry (reading works)
Press ENTER.
The topic opens in the content pane, but does not read.

Any suggestions would be appreciated. Thanks

[Psider]

Which output type and skin are you using? I don't use assistive technologies, but perhaps it's having problems with frames/iframes? (for example, Tripane uses iframes)

[chrisjoseph]

1) The output type is HTML5 and the Skin is Tripane. Is Tripane known to have issues with Frames/iFrames? are there any solutions that we can implement? This is what we ideally want to use as we have 3 output types - for desktop, tablets and mobiles. and Tripane has the best look and feel for our Desktop help.

2) We also have the option of using HTML 5 and Top Navigation/Side Navigation screen. When doing so we have noticed that some assistive technologies like JAWS reads the content pane well, but some of them like ZoomText don't. Our requirement is that it works on both these reading technologies well. We have kept this as a backup plan because we don't really like the way Top/Side navigation behaves with Desktop help (it pushes the content page to the left when TOC opens. This is due tobreakpoints being applied).

Will look into Frames/iFrames for Tripane, but if you do know of any solution, do let us know. Thanks.