Hi.
We're having some trouble getting the JAWS screen reader to read the xforms:textarea control as a table header. When JAWS is traversing the whole table, the text in the edit box is read correctly, but when trying to read the headers associated with a data cell (by pressing Ctrl+Alt+5), the textarea is completely ignored by JAWS. It's not clear what leads to the difference. We have already tried adding a title attribute and a hidden output with the same data we want read. These solutions both work for the specific problem case, but since the textarea will still be read during table-wide traversal, it means the data will end up being read twice in that case. Is there a known workaround for this type of issue? Thanks. Here is some markup to describe the situation:
|
Administrator
|
Hi Fredrick,
I ran this example here, and you'll find attached what I hear from JAWS. This sounds OK to me. Are you getting something different? Or expecting something different? Alex On Tue, Dec 27, 2011 at 7:38 AM, Fredrik Lidstrom <[hidden email]> wrote: > Hi. > > We're having some trouble getting the JAWS screen reader to read the > xforms:textarea control as a table header. When JAWS is traversing the whole > table, the text in the edit box is read correctly, but when trying to read > the headers associated with a data cell (by pressing Ctrl+Alt+5), the > textarea is completely ignored by JAWS. It's not clear what leads to the > difference. > > We have already tried adding a title attribute and a hidden output with the > same data we want read. These solutions both work for the specific problem > case, but since the textarea will still be read during table-wide traversal, > it means the data will end up being read twice in that case. > > Is there a known workaround for this type of issue? > > Thanks. > > Here is some markup to describe the situation: > <table> > <tr> > <th /> > <th scope="col">Test Text</th> > </tr> > <tr> > <th scope="row"> > <xforms:textarea id="test-area" > ref="instance('test-instance')/data/textarea" /> > </th> > <td> > <xforms:input id="test-input" ref="instance('test-instance')/data/input" > /> > </td> > </tr> > </table> > > -- > View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Accessibility-issue-reading-textarea-in-table-header-tp4237369p4237369.html > Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com. > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws jaws-reading.mov (191K) Download Attachment
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Thanks for the reply.
It looks like in your example you just let JAWS read over the whole table. There is no issue with that behavior. The problem comes when you focus on a cell and push the hotkey to read the associated headers for the cell. In that case, we could not get the contents of the textarea to be read. That said, it's probably not worth continuing this discussion. We eventually gave up and decided to change our requirement to avoid using dynamic table headers. Also, it could be an issue with JAWS rather than Orbeon. |
Administrator
|
Hi Fredrik,
On Wed, Jan 18, 2012 at 10:17 AM, Fredrik Lidstrom <[hidden email]> wrote: > It looks like in your example you just let JAWS read over the whole table. > There is no issue with that behavior. The problem comes when you focus on a > cell and push the hotkey to read the associated headers for the cell. In > that case, we could not get the contents of the textarea to be read. > > That said, it's probably not worth continuing this discussion. We eventually > gave up and decided to change our requirement to avoid using dynamic table > headers. Also, it could be an issue with JAWS rather than Orbeon. Got it; thank you for the update. Alex -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Free forum by Nabble | Edit this page |