[Documentation status: preliminary] Availability This is an Orbeon Forms PE feature.Introduction The noscript mode is a special mode of the XForms engine which produces pure HTML pages without any JavaScript. This has the following benefits:
Because of the declarative aspects of XForms, a same page description written in XHTML and XForms can produce an Ajax output or a noscript output, thus saving on development time. Limitations of the noscript mode
Enabling the noscript modeYou enable the noscript mode:
The choice whether users get the noscript or script-enabled version of your form is done ahead of time, before the HTML is sent to the browser. At this point, Orbeon Forms does not support sending a page to the browser which uses JavaScript if available, and degrades to the noscript mode if JavaScript isn't available. Typically, you'll want to present users for the script-enabled version of the form first, adding a link at the top that could read "Accessible version" and that points to the noscript version of the form. If you're using Form Builder / Form Runner, this will be done automatically for you. The benefit of this approach is that you're giving users the choice of which version to use. In some cases, users might have a JavaScript enabled browser, but prefer the noscript version because it will work better with their screen reader. The drawback is that in the rare cases where users happen to use a browser that really doesn't support any JavaScript, they will have to do an additional click on "Accessible version" before they can get a version of the form they can use. It is also possible to disable noscript support using the oxf.xforms.noscript-support property. See the Noscript mode properties.Writing XForms supporting the noscript mode Use property('xxforms:noscript') in XPath: return true or false depending on whether you are in noscript mode or not.[TODO] Form Runner support[TODO]NotesTODO:
|