Orbeon accessibility

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

Orbeon accessibility

eric.ficheux
Hi,

We have chosen to implement forms with Orbeon, but we have a strong
accessibility constraint and must provide an accessible version of our forms.

I'm thinking of 2 options:
1/ Write an alternative version of the form with pure XHTML (no Xforms, no
javascript) and use the page flow controller and the XPL processors to process
the request.
2/ Modify the orbeon engine to make it accept form submissions with javascript
disabled on the browser.

Solution 1 would be OK, but I find it unsatisfying because It doesn't make use
of XForms and we would have to develop a second form for every form we want to
put online.
Solution 2 could be an option if the workload remains reasonable (less than 10
days for a good J2EE developer).

So here's my question: how big an effort would it be to make orbeon run with
javascript disabled on the browser?

Regards,
Eric Ficheux


--
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
Reply | Threaded
Open this post in threaded view
|

Re: Orbeon accessibility

Erik Bruchez
Administrator
Eric,

You are in luck, because we will be working on #2 in the summer :-)

-Erik

On Jun 4, 2008, at 3:38 PM, [hidden email] wrote:

> Hi,
>
> We have chosen to implement forms with Orbeon, but we have a strong
> accessibility constraint and must provide an accessible version of  
> our forms.
>
> I'm thinking of 2 options:
> 1/ Write an alternative version of the form with pure XHTML (no  
> Xforms, no
> javascript) and use the page flow controller and the XPL processors  
> to process
> the request.
> 2/ Modify the orbeon engine to make it accept form submissions with  
> javascript
> disabled on the browser.
>
> Solution 1 would be OK, but I find it unsatisfying because It  
> doesn't make use
> of XForms and we would have to develop a second form for every form  
> we want to
> put online.
> Solution 2 could be an option if the workload remains reasonable  
> (less than 10
> days for a good J2EE developer).
>
> So here's my question: how big an effort would it be to make orbeon  
> run with
> javascript disabled on the browser?
>
> Regards,
> Eric Ficheux
>
> --
> 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 for the Enterprise Done the Right Way
http://www.orbeon.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