The problem with this “solution” however is that the real intention of tables was for “tabular data”.  It was not developed as a way for designers to position items on a page…although it was often being used for such.  (and still is in some cases – I’ll explain why later).

There are many reasons why you shouldn’t be using tables for layout.

1. Tables result in slow page loading times.
2. They cause accessibility issues for handicapped people – namely those using screen readers.
3. They make it MUCH harder to do redesigns.
4. They affect page rankings in search engines.
5. The code necessary to create tables is way more complicated in comparison to CSS.

Here is a great reference site for Why Tables Are Bad For Layout.

Now, having explained why tables are bad for layout, what can you do to build a site correctly?  You’ll need to learn CSS.  This may seem like a daunting task, especially if you are so used to building with tables and you like going with what you know.  However if you learn and keep up with the changing pace of CSS you will not only be doing yourself a favor but also all those who view your site/s on the web.

People are unfortunately impatient.  In most cases you have very little time to capture their attention.  If your visitors have to wait more than 15 seconds for your page to load chances are they have already clicked away from your site.  CSS allows you to create compliant web pages that load quickly and cleanly.  And if you ever want to change the look and feel site-wide, you can do so by editing one css file (versus editing every page of your site).

A good reference site for CSS is W3Schools.  If you tend to learn quicker working in a trainer led course, I offer group trainings online a few times per year.  I also offer one-on-one online training in Dreamweaver CS4, basic CSS, HTML and WordPress.  Click here for more information.

Earlier in this post I mentioned that there are still some cases where using tables is still “acceptable”.

One case of course is for tabular data.  Not sure if what you have is tabular data?  Ask yourself these questions:

• “Do the rows or columns of information share a common attribute?”
• “If I changed the order of the rows or columns, would it still make sense?”
• “If I transposed the axes of the table (made rows into columns and vice-versa) would it still make sense?”

If the answer to the above is generally “Hrm…I guess not,” then you shouldn’t be using a table. Source

The other case is when working with email based newsletters.  Unfortunately, many of the email clients in existence today are way behind the times when it comes to compliance.  Most do not yet work properly with CSS, so we are forced to use tables for layout in this case.  Some email clients support CSS more than others, but the idea behind email newsletters (aka ezines) is to reach everyone with minimal display errors.

It’s a rule of thumb if you are sending an HTML newsletter to also send along a TEXT version in the event that you are sending to someone whose email client does not support HTML email or is set not to display HTML for security reasons.

So to finalize, if you are still using tables for website layout there are plenty of reasons why you should learn to implement CSS.  You can still use your love of table layouts for creating ezines and get your fix there.