bstaats wrote:
Ok, now I am officially confused.
Me too
1. A web service interface is not a end user graphical interface. A web service interface is like RPC or SOA. Thus, javascript [on/off] has no relevance.
The webservice has absolutely nothing to do with this javascript issue. I just wanted to point out that our company wants to contribute the webservice we are developing.
2. If you are talking about an end user browser-based graphical interface, then are you talking about turning Java off or Javascript off in the browser?
I'm talking about the limesurvey client side e.g. the user who fills out a survey and might be handicapped and therefoe uses technical helpers like screenreaders or other stuff that might not be javascript compatible. Java doesn't matter.
3. Projects that are funded by the US government are also mandated to be accessible and proper use javascript (javascript turned on) does not disrupt this mandate. Especially given our use of Dojo, which has a fairly comprehensive strategy for accessibility.
I have read about the dojo teams' effort to consider accessibility issues. I hope I can persuade my boss that the way javascript is used is acceptable for our company.

Nevertheless can you estimate the effort necessary to create a non-javascript client interface (excluding the admin panel). I think it won't be easy because the dojo toolkit is deeply connected to the whole system?!

Thanks for your enlighting insights into limesurvey development.

The use of Dojo for all things UI does not imply the UI will not work if Dojo (or javascript) is removed. For example: If you have a textbox for collecting a date it is still a HTML textbox, Dojo is designed such that if this textbox is marked in a particular way Dojo will replace the textbox with it's date picker textbox.

So the answer to the question of 'will everything still work if javascript is disabled' is yes if everything is designed to degrade correctly. One big challenge here will be saving of results. We currently plan to leverage xhr to do auto saving so responses are recorded periodically (we do not wait for the page to be submitted). If javascript is disabled we will still need a strategy to save the users results on page submit. This is where we need to pay attention to how we degrade the UI when javascript is turned off.

Thanks for this additional information.

macasek wrote:
So the answer to the question of 'will everything still work if javascript is disabled' is yes if everything is designed to degrade correctly. One big challenge here will be saving of results. We currently plan to leverage xhr to do auto saving so responses are recorded periodically (we do not wait for the page to be submitted). If javascript is disabled we will still need a strategy to save the users results on page submit. This is where we need to pay attention to how we degrade the UI when javascript is turned off.
Hi Michael/Brian,
can you add a few sentences about the progress regarding the marked topics?!

The Roadmap maintains weekly updates on LS2 progress in addition to features slated for the near future (e.g. non-javascript support)