Edit comment LC-875 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-490 Next: LC-476

Comment LC-875: Comment Shortname:; Commenter: Chris Ridpath <chris.ridpath@utoronto.ca> on behalf of ATRC University of Toronto; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Part of Item:
Comment Type: substantive
Comment (including rationale for proposed change):

The technique H71 (fieldset and legend) under SC 1.3.1 is helpful but not necessary for all groups of controls. This is now at level 1 and should be moved to level 2. An example file was posted to the list (http://checker.atrc.utoronto.ca/docs/file2.html) that is very accessible and commonly used but fails the SC. Authors should not be forced to use fieldset and legend for all groups of controls.

Proposed Change:

Move H71 to level 2.; Related issues: (space separated ids); WG Notes: [TEAMC] explain that techniques are not at specific levels. Also, techniques are not required but one way to meet the success criteria. Review technique and clarify situations where the technique is most beneficial. I did add Chris' example to technique H44 about labeling form controls. The group needs to agree that his example is sufficient. I think with a small number of related radio buttons a fieldset is not required - do others agree? We could also just use the introductory text of the proposed response and not make the changes to H44 and H71. Discussed in the 03 August 2006 telecon: Action: Bruce B to create a technique for using data tables to help identify form controls in a form. Resolution: LC-875 accepted as proposed. http://www.w3.org/WAI/GL/2006/08/03-wai-wcag-minutes.html {partial-accept} DONE add the following to the description of H44: When a small group of related radio buttons includes clear instructions and distinct selections it may not be necessary to use fieldsets and legends; technique H44, Using label elements to associate text labels with form controls, may also be sufficient. DONE add the following example to H44: Example 3: A small, related group of radio buttons with a clear description and labels for each individual element. Note: To provide clear associations and instructions for a large set of related radio buttons technique H71, Providing a label for groups of radio buttons or checkboxes using the fieldset and legend elements, should be considered. <h1>Donut Selection</h1> <p>Choose the type of donut(s) you would like then select the "purchase donuts" button.</p> <form action="http://example.com/donut" method="post"> <p> <input type="checkbox" name="flavour" id="choc" value="chocolate" /> <label for="choc">Chocolate</label><br/> <input type="checkbox" name="flavour" id="cream" value="cream"/> <label for="cream">Cream Filled</label><br/> <input type="checkbox" name="flavour" id="honey" value="honey"/> <label for="honey">Honey Glazed</label> <br/><input type="submit" value="Purchase Donuts"/> </p> </form> Internal draft update 10 August.; Resolution: WCAG 2.0 techniques do not have any assigned level. Each technique provides an example of how to meet one or more success criteria and are not absolute requirements. There is often more than one technique that can be used to meet a particular success criterion. Technique H71 is one mechanism which can be used to meet SC 1.3.1, but is not the only mechanism. If appropriate technique H44, Using label elements to associate text labels with form controls can also be used with radio buttons and check boxes. In order to clarify when fieldsets are appropriate the following paragraph has been added to the description of H71: When a small group of related radio buttons includes clear instructions and distinct selections it may not be necessary to use fieldsets and legends; technique H44, Using label elements to associate text labels with form controls, may also be sufficient. In addition, your example has been added to technique H44. Example 3: A small, related group of radio buttons with a clear description and labels for each individual element. Note: To provide clear associations and instructions for a large set of related radio buttons technique H71, Providing a label for groups of radio buttons or checkboxes using the fieldset and legend elements, should be considered.; (Please make sure the resolution is adapted for public consumption)