W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > April 2007

WCAG 2.0- HTML technique - table summary- wrong classification

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Tue, 10 Apr 2007 17:16:07 -0400
To: <public-comments-wcag20@w3.org>
Cc: <caldwell@trace.wisc.edu>, "'Bailey, Bruce'" <Bruce.Bailey@ed.gov>, <evlach@SPAMFREE.aegean.gr>
Message-ID: <461bfe32.69dd5a92.5dbf.462f@mx.google.com>

Please refer to HTML technique #H73 at
http://www.w3.org/TR/2006/WD-WCAG20-TECHS-20060427/Overview.html#H73
And the WCAG 2.0 Test Samples (sc1.3.1_l1_018) at
http://www.w3.org/2006/tsdtf/TestSampleStatusList
.

Issue: 
i. The table summary is an aid to understanding table content (G3.1 make
content readable and understandable, Principle #3) and is not related to
structure versus presentation (G1.3). Table summary helps understanding in
the same way as expansion of acronyms/ abbreviation helps understanding
content.
ii. The summary attribute is not required for all data tables. 
- The summary is  generally necessary for complex tables and may be a vital
aid for quick comprehension of such tables.  
- The summary is useful for simple tables with many columns. It can also be
used to convey the purpose of the table when the caption is not used. 
iv. In other cases it may be a nuisance . 
The explanation following the H73 technique is apt

Recommendation:
i. H73 should be a technique against G3.1 and not G1.3
ii. For complex tables the summary  should be  at level 1
iii. For the other two uses it may be  at Level 3 or Level 2.
Thanks,
Sailesh Panchang
Senior Accessibility Engineer
Deque Systems Inc. (www.deque.com)
11130 Sunrise Valley Drive, Suite #140,
Reston VA 20191
Phone: 703-225-0380 (ext 105)
E-mail: sailesh.panchang@deque.com
Received on Tuesday, 10 April 2007 21:14:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:07 UTC