Posted by HankRatz on Jan 29, 2010; 12:16am
URL: https://discuss.orbeon.com/Accessibility-Using-Orbeon-Forms-for-menus-and-keystroke-navigation-tp1401410.html


The University of California has asked us to make our websites more
accessible to people with motor and sight disabilities.  Keystroke navigation,
screen readers, voice recognition navigation, etc.

The interactive features of XForms and Orbeon at first seem to require more
mouse activities.  In general, there is some opposition between "ajax"
applications and accessibility because audible readers were designed to
have the page refreshed.

(On the other hand, a reader built into XForms could dramatically
simplify paginated table access, all kinds of things. The event and
data model lend themselves to readers that otherwise only have the
page load event.)

I'm welcome any feedback, references or experiences you have had attempting
to make you XForms applications more accessible.

Thank you,
Hank


Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042







--
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