Ok Michael, Rewrite www.seowebsitepromotion.com, making it appear as is, meeting 640, 800 and 1024+, windowed of not, whilst maintaining non collapsing/overlapping columns whose alternate sheets 1px delimiting column borders do not break at certain resolutions in certain browsers -- and I'll take my hat off to you. Why bother?
That's like the 'make your site accessible to handhelds' argument. In the real world, nobody is going to access my site with a handheld because it contains no relevant data. It's meant to be viewed on a desktop. If I were offering columnar data, like flight schedules and fairs I would ensure wireless pad users could access the data (but, of course, because of the limiting screen size, I wouldn't use tables but collapsing <div>s), since they may be en-route to the airport and needed last minute departure times. But as Neerav implies, there is the law of diminishing returns, and accessibility is about making your site as accessible to as great an audience - a real, not imagined or hypothetical audience - as possible. Use the currently available tools and wait for CSS and browsers to go columnar. Mike Pepper Accessible Web Developer www.seowebsitepromotion.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Michael Donnermeyer Sent: 12 May 2004 02:19 To: [EMAIL PROTECTED] Subject: Re: [WSG] Forms, labels & headers >> using a CSS "for the sake of it approach" creating multi column >> layouts and "faffing about" I don't look at it that way...it's quite easy to get everything to work right without tables if you're willing to put the effort in. Since mid 03 I have stopped using tables for anything other than what they're supposed to contain...tabular data. That's their purpose in the world, just like ours is to pay outrageous taxes and work our butts off for low pay (isn't it?). I've had very few issues arise since...less than the layouts before, that's for sure. The worst thing that ever happened to the web was the idea of using tables for layout, although frames are a very close second. Accessibility should be the primary concern of every developer for the web. The web was intended to make sharing information/data/etc. simple and far-reaching. Why a developer would make so much more work for him/her self is beyond me when there's a valid, easy, better, standardized alternative. ~MD On May 11, 2004, at 20:49, James Ellis wrote: > 1. I have a multi-column layout... when I psuh the site to a layout > for handheld I'll turn off the floats that handle the columns. The > content will then cascade down the page. This will involve adding a > new stylesheet and linking to it via a media attr, a user agent sniff > or a hyperlink for the user. > > 2. I have a multi-column layout... when I push the site to a layout > for handheld I'll have to change the markup so that the table rows > have only one cell in them each. This will also affect the screen and > print versions of the site (so I'll have to do mutiple markup for the > same content). > > Which one is easier and better in the long run? > > faffing around with rowspans and colspans can be frustrating as well. > The difference being that one method has a future, the other doesn't. > > Cheers > James > > > Neerav wrote: > >> hear hear .. multi-columnnar sites are much easier to do with a >> single wrap around table and work cross-browser than using a CSS "for >> the sake of it approach" creating multi column layouts and "faffing >> about" s=as Mike says >> >> standards are all well and good, and where possible I have no problem >> with adhering to the letter and spirit of webs standards, but >> sometimes things like wrap around tables are indispensible. >> >> > ***************************************************** > The discussion list for http://webstandardsgroup.org/ > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
