Thread

Thanks Inparo for making the FR and bringing this to my attention.  Labels are something that we’re making pains to include.  The EE2 CP that you see in the video demo for example, is fully “labeled”.

Notice to the people who are using the input in label approach. The input is disregarded in screenreaders. So if you have a percentage of visual impaired people as your public you might reconsider your approach.

I don’t have the necessary knowledge to address that, except to say that the W3C standard states that inputs may be within label tags, Section 508 doesn’t bother to warn away from the method, and WCAG1.0 specifically mentions the practice in their speifications document

With that in mind, it’s a failure of the screen reader technology for not following standards rather than a problem with the technique. I’m willing to work around the quirks of the Explorer family of browsers because everybody uses the cursed things, but catering to a tiny segment of the market that also uses software that ignores the relevant standards seems like a sisyphean task.

Nick i understand your point of view that’s why i nuanced the response stating

if you have a percentage of visual impaired people as your public

I find it sad that the two accessibility standards don’t consider the applications that are used by disabled people. Not all people use JAWS. It’s like saying everyone should use FF or IE.

Personally i keep the input out of the label because i found out styling is easier that way. Adding a span to style the text of the label gets my lazy typing sense tingling.