So, <label> should use the for='id' attribute for associating labels with elements, rather than trying to surround the elements.

<label for="thename">Some information</label><input name="thename" />

id is a very good optimisation:
<label for="thename" id="label-thename">Some information</label><input name="thename" id="thename" />

But label mee "Some information", <label for="thename"><input name="thename" /></label> is NOT a solution.

I don't have THE solution, i think:

• <label class="hide">Answer here : </label><input class="text" type="text" /> is the easiest way in quanda.
• ARIA way : http://www.w3.org/TR/wai-aria/states_and_properties#aria-labelledby can be too a good solution. ( see dev note : http://bugs.limesurvey.org/view.php?id=5781)

Given that WAI-ARIA just got W3C candidate recommendation status last month, I think it is a bad idea to try to support it right now. Also, we'd need to continue to use <label> to provide backwards support for older browsers.

WAI-ARIA is good to think about for optional HTML 5 support in the future.

Do we have anyone who can provide feedback from a Section 508 compliance perspective (that's the USA set of rules), or comparable international ones? I'm not well versed in that area.

Currently, <label> is nice because you can click on the text and toggle the value of the associated control. So, if you have a checkbox or radio button, you can click on the text rather than exactly hitting the input control.

However, <label> does nothing for sighted users for array-style questions. So, do we really need it there?

Also, for <textarea> and <input type='text'>, clicking on the text does shift focus to the input box, but it doesn't toggle the value. Is such a shift of focus an accessibility goal? If not, then I see no harm in removing those <label> tags.

All input need a label for accessibility.

Label mean : "What is the input for ?"
Without label you give no-information for accessibility and RGAA/Section508 etc ... are breaked. ( and label without content have the same issue).
(RGAA = Section 508).

You can try http://www.cynthiasays.com/ , but you can use too http://lynx.isc.org/ . Best is to have some information from user.

I have a link to answer of a survey by a concurrent system: no javascript => no answer . I think LimeSurvey have to be accessibility best compatible.

Denis
PS: aria-label and aria-labelledby aren't for IE6/IE7 user. It's for FANG/reader system user.

Hello,

I ask at a accessibility mailing list, and the answer is :
Using aria way is actually a good solution, JAWS (the web reader most using) use a lot af aria since version 9 for windows. FireFox/Opera/Chrome/Safari use aria for a long time. And IE8 use some aria element. A quote from 2008:
<blockquote>Screen readers that already support this feature are NVDA, JAWS 9.0, and Window-Eyes 5.5 or higher. JAWS 8 does not support this attribute yet. Also, ORCA does not seem to pick this attribute up yet, at least my testing showed that Orca did not indicate the required state to me when tabbing through that form.</blockquote> http://www.marcozehe.de/2008/02/29/easy-aria-tip-1-using-aria-required/

I think too of

• aria-required for mandatory,
• aria-live for em_validation tip
• aria-hidden for conditionnal question

And maybe some optimisation for accessibility without touching of visibility without screen reader.

Denis

PS: had to work on table too ... Arf .... table accessibility first.

@TMSWhite: That's exactly the reason why I requested in 04948 that this would be an optional feature which can be switched on/off in the question attributes (and defaults to true).

@magiclko: Can you please fix this up so there is a question attributes 'High accessibility' which defaults to true and if switched off leaves out the labels.
Thank you.

After reading Shnoulles comment again I am tending to support the suggestion to use the invisible label instead (if that's really visible to the screen reader).
Does a label hidden by a class really still show to blind people?

Hello:

positon:absolute,top=-9999px,left:-9999px : reading ( actual hide css in all included template, maybe some correction ( left:auto ) but it's a solution.
text-indent: -999999px : reading
display:none : not reading
visibility:hideen : no reading

I don't know for opacity:0, but i think reading.
Can have a look at webaim.org/techniques/css/invisiblecontent/ ( I know a lot of french semi-official site for accessibility, but not english site, sorry)

But there another good alternative i think:

• Optional : At question-text / inline but hidden label / actual way ( no label but an alt for input ) : inline but hidden by default

We can use this optionnal attribute at some question to have some specific accessibility issue on another question ( fieldset on radio list for example)..

for hide in user template : if i had time for http://bugs.limesurvey.org/view.php?id=5807 for 2.0, it can be very good. But included template have this class for a long time ago.

1.92 released