W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2002

Re: compliance and layout tables revisited

From: Charles McCathieNevile <charles@w3.org>
Date: Sat, 11 May 2002 15:43:34 -0400 (EDT)
To: Phill Jenkins <pjenkins@us.ibm.com>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0205111536120.9046-100000@tux.w3.org>
Whether we use CSS or tables is, as Phill says, not the only point, and the
one that was deemed most important to WCAG was about linearising sensibly -
WCAG checkpoint 6.1 about making sure CSS-based pages make sense without CSS
(question - is a broken CSS implementation "without style sheets"?) as well
as 5.3 making sure that table layouts work in linear format recognise this
(and a few other things).

In the medium term there is an issue with using tables for layout - it means
that serialising browsers have to be built not just to apply appropriate
styling, but also to rewrite the HTML itself.



On Sat, 11 May 2002, Phill Jenkins wrote:

  Whether we use CSS or tables for layout is *not* the point - it's that it
  linearizes correctly!  Same concept as correct or logical tab order.  As
  you read a page, you want it to be read in a logical order.

  Adding DIV's in a confusing order and putting in layout CSS is just as
  confusing as bad layout tables.    Both require the author and or tool to
  consider how the page will be rendered in a serial fashion, not just the 2
  d visual rendering in a graphical browser.

  Phill Jenkins
  IBM Research Division - Accessibility Center

Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI  fax: +33 4 92 38 78 22
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Saturday, 11 May 2002 15:43:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:19 UTC