- From: Chris Ridpath <chris.ridpath@utoronto.ca>
- Date: Thu, 22 Sep 2005 09:22:06 -0400
- To: "Terrence Wood" <tdw@funkive.com>, "WAI Interest Group" <w3c-wai-ig@w3.org>
Hi Terrence, The WCAG test suite has a couple of tests that apply to layout tables. These have not been accepted by the group but there is some support for them: Test 114 - All layout tables have an empty summary or no summary. http://www.w3.org/WAI/GL/WCAG20/tests/test114.html Test 115 - All layout tables do not contain caption elements. http://www.w3.org/WAI/GL/WCAG20/tests/test115.html Test 137 - All layout tables do not contain TH elements. http://www.w3.org/WAI/GL/WCAG20/tests/test137.html Try to avoid using layout tables. Use CSS instead. Cheers, Chris ----- Original Message ----- From: "Terrence Wood" <tdw@funkive.com> To: "WAI Interest Group" <w3c-wai-ig@w3.org> Sent: Wednesday, September 21, 2005 7:58 PM Subject: Complex Tables and the TH element > > Greetings, > > I am developing processes for converting complex financial documents to > valid, accessible HTML. > > Traditionally, I have marked up tables where the first column is marked up > as a TH and set scope="row" for accessibility (and semantic meaning). > > However, some of the documents I am working with are 5 column Statements > of Financial Position where the first two columns are estimated numbers, > followed by a column containing the row labels, and finishing with two > columns of actual numbers. > > A quick perusal of the HTML 4.0 recommendation does not preclude me from > marking up the cells in column 3 as TH with scope="row". I am wondering if > anyone else has marked up documents in this manner, or can elighten me if > this is an abuse of HTML 4.0, or is aware that this presents a significant > barrier to assistive technologies? > > kind regards > Terrence Wood. > >
Received on Thursday, 22 September 2005 13:23:10 UTC