RE: [#656] explicit numbering for nested lists

Good point 

I think we need to begin thinking about marking all the techniques that are
specifically for weak AT or user agents and then considering them carefully.


By weak AT I don't mean all but the very best.  I mean provisions that
should not be necessary - but are due to AT bugs or omissions. 

 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Michael Cooper
Sent: Tuesday, April 13, 2004 10:21 AM
To: WAI GL (E-mail)
Subject: [#656] explicit numbering for nested lists


Bug 656 [1] discusses an editorial note in the HTML Techniques [2]. The
question is if we need to continue to recommend that authors provide
contextual clues in nested lists for the benefit of technologies that do not
represent their structure adequately. Sailesh did some testing of Windows
technologies [3] and concludes that most but not all recent versions of
products provide adequate support.

In spite of the fact that the testing is only on Windows and support is not
universal, I propose that we deprecate this requirement. We should create a
specific technique about contextual clues for nested lists (right now this
is just in the preamble to the section on lists), mark it as deprecated, and
list user agents for which we know the technique still to be required.
Thoughts?

Michael

[1] http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=656
[2] http://www.w3.org/TR/2003/WD-WCAG20-HTML-TECHS-20031209/#lists
[3] http://lists.w3.org/Archives/Public/w3c-wai-gl/2003OctDec/0410.html

--- Signature ---

Michael Cooper
Accessibility Product Manager, Watchfire
1 Hines Rd Suite 200, Kanata, ON  K2K 3C7  Canada
Tel: +1 (613) 599-3888 x4019
Fax: +1 (613) 599-4661
Email: michaelc@watchfire.com
Web: http://www.watchfire.com/

Received on Tuesday, 13 April 2004 19:26:38 UTC