W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2005

RE: Tests 186, 187, 188, 189,

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Wed, 10 Aug 2005 11:21:56 -0500
Message-ID: <6EED8F7006A883459D4818686BCE3B3B01B05DE2@MAIL01.austin.utexas.edu>
To: "Roberto Scano - IWA/HWG" <rscano@iwa-italy.org>, "Yvette Hoitink" <y.p.hoitink@heritas.nl>, "WCAG WG mailing list" <w3c-wai-gl@w3.org>

Roberto wrote:

<blockquote>
I don't understand your reply.

Here is an example:

	<fieldset>
           <legend>Sex</legend>
		<label for="sessoM">Male</label>
		    <input type="radio" size="20"
			    id="sessoM" name="sex" /> <br />
              <label for="sessoF">Female</label>
		<input type="radio" size="20"
			    id="sessoF" name="sex" />
	</fieldset>

What's wrong?
</blockquote>

Hi, Roberto. I don't think there's anything wrong with this example. But
I don't think it associates multiple label elements with the same form
control.

You have two <input> elements of type="radio"; each has a unique ID, and
each has a <label> element associated with its ID.  The <input> elements
are nested inside a <fieldset>, whose <legend> governs the pair of
<input> elements.  This is correct code, but there's a unique label for
each input.
So there's nothing wrong with your example, but it's not relevant to the
test.

John

"Good design is accessible design."

Dr. John M. Slatin, Director 
Accessibility Institute
University of Texas at Austin 
FAC 248C 
1 University Station G9600 
Austin, TX 78712 
ph 512-495-4288, fax 512-495-4524 
email jslatin@mail.utexas.edu 
Web http://www.utexas.edu/research/accessibility 



-----Original Message-----
From: Roberto Scano - IWA/HWG [mailto:rscano@iwa-italy.org] 
Sent: Wednesday, August 10, 2005 11:15 AM
To: John M Slatin; 'Yvette Hoitink'; 'WCAG WG mailing list'
Subject: RE: Tests 186, 187, 188, 189,


Hi John,
I don't understand your reply.

Here is an example:

	<fieldset>
           <legend>Sex</legend>
		<label for="sessoM">Male</label>
		    <input type="radio" size="20"
			    id="sessoM" name="sex" /> <br />
              <label for="sessoF">Female</label>
		<input type="radio" size="20"
			    id="sessoF" name="sex" />
	</fieldset>

What's wrong?


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of John M Slatin
Sent: Wednesday, August 10, 2005 6:06 PM
To: Roberto Scano - IWA/HWG; Yvette Hoitink; WCAG WG mailing list
Subject: RE: Tests 186, 187, 188, 189,



Roberto wrote:

<blockquote>
E006554318

</blockquote>

The HTML spec allows for multiple labels to be associated with one form
control.  But I don't know of any screen reader that supports this. That
makes it a user agent issue, perhaps, rather than a guidelines issue.
So maybe we should accept the test.

Tests are not normative, so it will be possible to update the test files
as user agents, etc., evolve.

John

"Good design is accessible design."

Dr. John M. Slatin, Director 
Accessibility Institute
University of Texas at Austin 
FAC 248C 
1 University Station G9600 
Austin, TX 78712 
ph 512-495-4288, fax 512-495-4524 
email jslatin@mail.utexas.edu 
Web http://www.utexas.edu/research/accessibility 



-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Roberto Scano - IWA/HWG
Sent: Wednesday, August 10, 2005 10:57 AM
To: 'Yvette Hoitink'; 'WCAG WG mailing list'
Subject: RE: Tests 186, 187, 188, 189,





-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Yvette Hoitink
Sent: Wednesday, August 10, 2005 5:40 PM
To: 'WCAG WG mailing list'
Subject: RE: Tests 186, 187, 188, 189,



David MacDonald recommended to accept HTML test 187:
INPUT element must have only one associated LABEL. [1] 
 
Are there any accessibility problems with having two labels associated
with the same input element? To me it would that problems only occur if
the wrong label is associated, but that's true if only 1 label is
associated as well. Multiple labels are permitted by the HTML spec and
used wisely it can actually benefit accessibility. Based on this, I
would like to reject this test.

Roberto Scano:
There is a problem for label esplicit association. The "for" attribute
refer to the ID and HTML spec don't authorize to use more than one ID
per page.

Yvette:
A real-world example: a content management system we built allowed the
user to choose between two images. We used radiobuttons placed below the
images to make the selection. One radiobutton had a text to it that read
something like 'use old photograph', the other 'use new photograph'. 
We chose to use both the image (where the alt text described the image)
and the text as labels. This way, the user could either click the image
or the text below it to make a selection, providing a larger click
target for people with limited motor functions. Also, it made sure that
both the alt-text of the image and the meaning of the radio button (to
use that
image) were associated with the radio button.

Roberto Scano:
Put the input inside a fieldset.
Received on Wednesday, 10 August 2005 16:22:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:39 GMT