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

[TECHS] Review of Test #168 - propose marking it as optional

From: <Becky_Gibson@notesdev.ibm.com>
Date: Mon, 14 Feb 2005 11:22:39 -0500
To: w3c-wai-gl@w3.org
Message-ID: <OF6ACEFF8D.2025B3B8-ON85256FA8.0053739B-85256FA8.005A23BC@notesdev.ibm.com>
As part of the Techniques Working group review of tests, I was assigned 
test #168 [1]:
In all forms, all radio button and checkbox groups that provide multiple 
value choices for a single field name are grouped using fieldset and 
legend elements.

In my opinion, fieldset and legend should not be required for conformance 
and this test should be marked as optional.  It does offer good advice and 
is already in our  HTML techniques document[2].  As long as labeling of 
form controls is required, the author should not be forced to group 
related components.  Also, this opens up additional issues with what 
information is required for the <legend> element. For example, is 
descriptive text required and would we need a test to verify the <legend> 
was not blank and contained an appropriate description?

Other issues:
Currently this test is associated with Guideline 1.1: Provide text 
alternatives for all non-text content. There is no particular success 
criteria associated with the test.    I believe it should be under 
Guideline 2.4 Provide mechanisms to help users find content, orient 
themselves within it, and navigate through it [3].  And be associated with 
Level 3 Success criteria #1: When content is arranged in a sequence that 
affects its meaning, that sequence can be determined programmatically [4] 
Although I realize that may be a bit of a stretch.  It also falls under 
Level 1 success criteria for this Guideline:  Structures and relationships 
within the content can be programmatically determined. 

There are also no written instructions for this test.   The Procedure, 
Expected Results, and Fail Instructions all contain, "TODO" placeholder 
text.  Here are proposed instructions:
Procedure:
1. Check all <input> elements of type radio which contain the same name 
attribute, indicating that the radios apply to a single submitted field 
value. 
Check all <input> elements of type checkbox which contain the same name 
attribute, indicating that the checkboxes apply to a single submitted 
field value.
2. The related radio or checkbox <input> controls must be surrounded with 
<fieldset> and <legend> elements.

Expected Results:
1.  All <input> elements of type radio which contain the same name 
attribute are grouped together using <fieldset> and <legend> elements.
2. 1.  All <input> elements of type checkbox which contain the same name 
attribute are grouped together using <fieldset> and <legend> elements.
3. The <legend> element contains text that describes the grouping of 
elements. (editor's note  - this may be getting too specific).

Fail Instructions:
1. Group related radio and checkbox elements that provide multiple, 
possible values for a single field name within <fieldset> and <legend> 
elements. 

I also think that the examples for this test are incorrect. The test 
description relates specifically to radio and checkbox groups but the test 
uses a grouping of text fields as an example.  I did create a more valid 
pass test file since the HTML technique is missing a radio button example, 
as well.  The file is attached. 


[1]http://www.w3.org/WAI/GL/WCAG20/tests/test168.html
[2]http://www.w3.org/TR/WCAG20-HTML-TECHS/#fieldset
[3]http://www.w3.org/TR/WCAG20/#navigation-mechanisms
[4]http://www.w3.org/TR/WCAG20/#navigation-mechanisms-one-seq



Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com

Received on Monday, 14 February 2005 16:23:12 GMT

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