- From: Al Gilman <asgilman@access.digex.net>
- Date: Sun, 8 Nov 1998 16:51:35 -0500 (EST)
- To: nir@nirdagan.com (Nir Dagan)
- Cc: w3c-wai-gl@w3.org
I think this version has been tacitly emphasized because of what is implemented already in browsers. Al to follow up on what Nir Dagan said: > Concerning the techniques doc. > > In 2.12.2 the example uses LABEL with > for and id attributes where it is possible to > simplify and include the INPUT as content > of LABEL and forget about the for and id stuff. > > Maybe it would be better to give both possibilities > in examples. > > In 2.12.3 it says you should use the for attribute. > I can't see why. If there is one INPUT in a LABEL, > as the HTML4.0 spec. requires explicitly, > there is no ambiguity. What's wrong with the HTML4.0 spec.? > One should use "for" in my opinion, only when it is impossible > to put the INPUT inside the LABEL (if they are in different table > cells for example). > > Also I didn't get the idea behind writing the control > and its label in the same line when "for" is not used. > I am unfamiliar with a "line" concept in HTML. > > Nir Dagan > Assistant Professor of Economics > Universidad Pompeu Fabra > Barcelona (Spain) > > http://www.nirdagan.com > mailto:nir@nirdagan.com > > "There is nothing quite so practical as a good theory." > -- A. Einstein >
Received on Sunday, 8 November 1998 16:51:44 UTC