RE: More updated HTML techniques for SC 1.3.1

Thanks, Loretta.

I agree about the example of a "plain text table" (Example 1. Maybe it
shouldn't be here-- it's really a common failure rather than an example!
I included it in response to Michael's comment, but maybe we should take
it out. We don't need to create any more confusion than absolutely
necessary! <grin>

John 



"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/


 


-----Original Message-----
From: Loretta Guarino Reid [mailto:lguarino@adobe.com] 
Sent: Monday, February 13, 2006 4:27 pm
To: John M Slatin; public-wcag-teamb@w3.org
Subject: RE: More updated HTML techniques for SC 1.3.1

John, I made the changes to the technique title that you suggested, and
removed the th technique that is now redundant.

We may want to label Example 1 in
http://trace.wisc.edu/wcag_wiki/index.php?title=Using_table_markup_to_pr
esent_tabular_information as an example of a common mistake, since I, at
least, was initially confused by it.

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 Monday, 13 February 2006 22:51:25 UTC