Improve WCAG support

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Improve WCAG support

mabu
Hi,

I tested orbeon forms 4.8 with a demo version of the screen reader JAWS (version 16). In general, I think the WCAG support is good but I have two suggestions to increase it.

1.) Wizard Navigation:
Currently, JAWS is not able to check that the wizard navigation tree (list of links) is for navigation purpose. If you add a ARIA landmark to the encapsulating div <div class="fr-wizard-toc" role="navigation"> JAWS is able to check it. It would also be nice if a title attribute is set on the links wizard-next/wizard-previous.

2.) Repeated Grids:
Repeated grids are in general hard to understand with JAWS. An improvement would be to specify a title attribute on the "add-new-grid-line" link. Ideally, a user is able to customize this title attribute with the formbuilder. Also for the button a title attribute (e.g. further actions) should be specified.

Martin
Reply | Threaded
Open this post in threaded view
|

Re: Improve WCAG support

Alessandro  Vernet
Administrator
Hi Martin,

1. At some point, we had done really lots of testing with JAWS, and fixed a number of problems / made a number of improvements, but we didn't get a chance to do much testing with JAWS lately. I tried adding the role="navigation" <div class="fr-wizard-toc">, and it doesn't make a difference with OS X VoiceOver. I don't have an environment with JAWS here, but are you sure this is enough to improve the situation with JAWS? If you are, I'm happy to commit the change.

2. Yes, I agree, we should have titles there. Would you be able to do those changes, test them on JAWS, and submit a pull request? If you have some bandwidth to do that, but just miss some information on how to do it, just let us know and we'll do our best to help.

Alex
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
Reply | Threaded
Open this post in threaded view
|

Re: Improve WCAG support

mabu
1. In JAWS you have the possibility to list all regions with the keystroke INSERT+CTRL+R. So, if you add role="navigation" to <div class="fr-wizard-toc"> it is in my opinion a good improvement for blind users to check that these links are for navigation purpose.
I also tested adding titles to the next/prev wizard links and it worked like a charm. I simply added the follwing xforms hints inside the trigger tags in wizard.xbl:
<xf:hint value="xxf:r('components.wizard.prev-section', 'fr-fr-resources')"/>
<xf:hint value="xxf:r('components.wizard.next-section', 'fr-fr-resources')"/>

2. Adding titles to the link/button in repeat grids works not out of the box like for the wizard links. I tried to add only static title text without success. Maybee you can take a look at it if you have time? For a first step I think simple static text is enough. Editing the title text in the formbuilder would be a nice feature for future.

Martin