- From: Loretta Guarino Reid <lguarino@adobe.com>
- Date: Mon, 13 Feb 2006 18:34:09 -0800
- To: "John M Slatin" <john_slatin@austin.utexas.edu>
- Cc: <public-wcag-teamb@w3.org>
Are Captions required for data tables? When I read the technique, I come away with the impression that they are. I'm not quite sure how we write the test procedure for something that is optional, unless we can capture how to determine when it is needed. The summary technique talks about what the WCAG WG recommends. It should probably just make the recommendation directly. (This will probably result in passive language.) Do we need (not in layout tables) in the titles of all these techniques? It certainly belongs in the description, but I find it makes the technique title hard to read. Everything else looks ok to my untrained eye. Loretta Guarino Reid lguarino@adobe.com Adobe Systems, Acrobat Engineering > -----Original Message----- > From: public-wcag-teamb-request@w3.org [mailto:public- > wcag-teamb-request@w3.org] On Behalf Of John M Slatin > Sent: Monday, February 13, 2006 8:02 AM > To: public-wcag-teamb@w3.org > Subject: More updated HTML techniques for SC 1.3.1 > > > Hi, all. > > Over the weekend I updated the following techniques to > address > suggestions from the Working Group: > > - Using table, tr, and td elements for tabular > information[1] > - Using caption elements to identify data tables (but not > layout tables) > [2] > > > Changes are described in the Status section of each > technique. > > The tabular infomration technique [1] has now been > combined with content > from Using the th element to identify column and row > headers in data > tables (but not in layout tables) [3], as suggested by the > WG, so I > suggest deleting [3]. > > Both [1] and [2] should be retitled (suggestions in the > Status section). > > Today I'll write a technique about Using the table > element's summary > attribute to describe the organization of a data table. > Will post to the > list when it's done. > > Thanks to Loretta and Yvette for additional updates! > > John > [1]http://trace.wisc.edu/wcag_wiki/index.php?title=Using_t > able%2C_tr%2C_ > and_td_elements_for_tabular_information > [2] > http://trace.wisc.edu/wcag_wiki/index.php?title=Using_capt > ion_elements_t > o_identify_data_tables_%28but_not_layout_tables%29 > [3]http://trace.wisc.edu/wcag_wiki/index.php?title=Using_t > h_elements_to_ > identify_column_and_row_headers_in_data_tables_%28but_not_ > in_layout_tabl > es%29 > "Good design is accessible design." > John Slatin, Ph.D. > Director, Accessibility Institute > 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.utexas.edu/research/accessibility/ > > > >
Received on Tuesday, 14 February 2006 02:35:15 UTC