Orbeon Forms community mailing list

Accessibility - Using Orbeon Forms for menus and keystroke navigation

Classic

List

Threaded

2 messages Options

HankRatz

Accessibility - Using Orbeon Forms for menus and keystroke navigation

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

Alessandro Vernet

Re: Accessibility - Using Orbeon Forms for menus and keystroke navigation

Administrator

Hi Hank,

We constantly do improvements to make markup Orbeon Forms generates
more accessible, for instance making sure that labels have a "for"
attribute point to the corresponding input field. If you have to
satisfy some drastic constraints, you can also provide a link to a
version of the page rendered in noscript mode, so most people won't be
impacted and those with a screen reader can have a plain-HTML page
that doesn't use any scripting. You'll also find a some more
information on:

http://www.orbeon.com/orbeon/doc/home-faq#xforms-accessibility

Alex

On Thu, Jan 28, 2010 at 4:16 PM, Hank Ratzesberger
<[hidden email]> wrote:

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

--
Orbeon Forms - Web forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
My Twitter: http://twitter.com/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