- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Tue, 10 Jun 2003 13:35:25 -0500
- To: "Ben Caldwell" <caldwell@trace.wisc.edu>, <w3c-wai-gl@w3.org>
Ben, the proposal does sound reasonable. But I notice that the proposed text for definition headings puts the numbers first (1.1.2 etc.) whereas the others put the words first (Success criteria for ...). I'd suggest putting the letters first, both for consistency's sake and because it makes navigation faster. For example, people who use JAWS or Home Page Reader can navigate the headings list alphabetically: hit "D" and you jump to the next item in the list that begins with that letter. If the numerals come first, it'll take longer, since there's 1.1.1, 1.1.2, etc., plus the possibility of even deepr nesting. John John Slatin, Ph.D. Director, Institute for Technology & Learning University of Texas at Austin FAC 248C 1 University Station G9600 Austin, TX 78712 ph 512-495-4288, f 512-495-4524 email jslatin@mail.utexas.edu web http://www.ital.utexas.edu -----Original Message----- From: Ben Caldwell [mailto:caldwell@trace.wisc.edu] Sent: Tuesday, June 10, 2003 1:25 pm To: w3c-wai-gl@w3.org Subject: RE: [12] Use of headings Gregg asked: > Sounds good. You mean like adding the number of the respective guideline > / > checkpoint to the repetitive heading to make the headings unique? Yes. Checkpoint 1.1 would include checkpoint numbers in headings as follows: Required Success Criteria for Checkpoint 1.1 Best Practice for Checkpoint 1.1 1.1 Definitions (Informative) 1.1 Benefits (Informative) 1.1 Examples (Informative) I've modified the XSL for our draft to insert these numbers automatically and will include it in the next draft. Does this sound like a reasonable proposed resolution to Issue #12 [1]? -Ben [1] http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=12
Received on Tuesday, 10 June 2003 14:35:26 UTC