Hello and greetings fellow LS goers!

I am the new UI designer / engineer for LS2. For the past month I have been working with Juhan and others to continually evolve LS2 UI designs and prototypes. You can see the latest (and previous) designs at design.limesurvey.org where we will be continually updating the site with the latest work.

We highly encourage everyone to frequent the updated design.limesurvey.org and send comments, questions, or hate mail ( This e-mail address is being protected from spam bots, you need JavaScript enabled to view it ). The designs start out basic and will gradually become more sophisticated over time as features and feedback are added. With everyone's eyes we can create an outstanding user experience for LS2.

Happy to be aboard
Brian

Whats your input?
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Great work so far!

One question: In which way do you treat accessibility? I think you use a lot of ajax features but what if users have disabled javascript? What's your general accessibility approach?

Thanks Mazi,

LS2 extensively uses the Dojo Javascript toolkit which has considerations for accessibility. See Dojo's strategy for more information.

A non-JS degraded interface could be supported for ultra simple (micro) surveys, but this feature is far down the list of requirements.

We feel Dojo's accessibility approach is sufficient to address the majority of accessibility issues. We can beef this up in the future if needed.

Thanks a lot for this additional information!

But as I can see you won't be able to use LS2.0 if you have JS turned off, will you?
Probably there won't be any workarounds either because LS2.0 is deeply connected to the dojo toolkit?!

Brian?

You are correct. However, this would be an exception not the rule and in the case of this exception, as I mentioned, a degraded (non-javascript) interface could be supported.

bstaats wrote:
... a degraded (non-javascript) interface could be supported.

Wouldn't this require a huge effort?

Define "huge effort". The effort involved would be determined on its intended audience / purpose.

Who is this non-javascript audience?

Can you give a reasonable example where it would be desirable to turn off javascript?

bstaats wrote:
Who is this non-javascript audience?
I hope I can make clear why a working version with java is essential.
Our company wants to use limesurvey as a tool for lecture evaluation. Therefore we will create a webservice interface for LS2.0 (I have talked to Juhan about this some weeks ago) to connect limesurvey to our highschool management software.
The problem is that German law says that public institutions (like universities) have to make their information accessable for handicapped people and because our company is owned by the German government we have very strict guidelines to make our software accessable. This includes that every interface has to be usable with javascript turned off.

Of course the normal user won't have javascript turned off but it's a requirement that we can offer alternatives for each javascript action. That's why we rely on a non-javascript interface at the client side.

I hope our problem is comprehensible. If not, just ask.

Ok, now I am officially confused.

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.

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?

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.

Please help me understand your situation if (1-3) does not address it. Thanks!