From: "Philipp Lenssen" <phil@mrinfo.de>
Newsgroups: comp.infosystems.www.authoring.html
Subject: Re: Tables in Site Design
Date: Mon, 27 Aug 2001 12:02:07 +0200
Message-ID: <9md5ml$fdh$3@swifty.westend.com>
Newsgroups: comp.infosystems.www.authoring.html
Subject: Re: Tables in Site Design
Date: Mon, 27 Aug 2001 12:02:07 +0200
Message-ID: <9md5ml$fdh$3@swifty.westend.com>
"Jake Roberts" <otijim@NOSPAMME.yahoo.com> wrote in message news:3b86b7af.176956299@news.byu.edu... > Can someone point me to some info on using tables in advanced site > design. I don't mean a silly basic table tutorials that explains > COLSPAN. > I'm looking for something that can help me with Netscape/IE > crossbrowser problems. >.. If you want to save yourself time in development, don't use table layout at all. If you're interested in crossbrowser compatibility, don't use it. If you like to keep your pages simple, fast to transmit and fast to render, don't use table layout. As a bonus, you get a site more accessible to browsing situations you can't test or didn't even think of. (Ever imagined your page as WAP WML by the Google-on-the-fly conversion from HTML?) From the W3C Web Accessibility Guideline ( http://www.w3.org/TR/WCAG10/#gl-structure-presentation ): "Misusing markup for a presentation effect (e.g., using a table for layout or a header to change the font size) makes it difficult for users with specialized software to understand the organization of the page or to navigate through it. Furthermore, using presentation markup rather than structural markup to convey structure (e.g., constructing what looks like a table of data with an HTML PRE element) makes it difficult to render a page intelligibly to other devices (refer to the description of difference between content, structure, and presentation)." -- Philipp Lenssen M+R infosysteme http://www.mplusr.de