Using tables for layout is also flat out against the recommended accessibility guidelines of the W3C and WCAG.

Tables are designed to be used for DATA. Not layout.

While a table can be checked, and checked, and checked to verify it's visual display on various browsers - the last thing you want is for some users out of left field with a disability that uses a screen reader, and the reader follows your tables in an order you didnt expect.

CSS for layouts - Not Tables.

DIV is the way to go, tables are out and should have never really been "in".

hello

better you go for dream weaver it may help you to design template
enjoy it.........................



<MOD NOTE: Signatures must be setup in your profile and not manually added to your messages.>

Disagree. While dreamweaver is a fine tool, standards are standards, which is what a good webpage is all about. Dreamweaver does not necessarily enforce standards, for example it is perfectly happy for you to use tables for site layouts, when div tags should be used. It CAN however guide you with standards... Which I am all for.

Furthermore, there are lots of fine web authoring tools out there, that are not necessarily wysiwyg. Take coda, for exmple.

What a developer should do is be mindful of the w3c standards, and THEN use a tool such a dreamweaver to implement them. For a beginning web developer, I have absolutely no problems with them doing that

Definitely make the switch to Divs. It might seem overwhelming at first, but it is much better once you learn. I learned at http://www.w3schools.com/css/default.asp

It will be easier to style the page now and change it in the future. It will be more compatible across browsers and load faster, and when your page loads faster, Google is happier.

Yes, customers does not bother with the code you do but it matters when you require to give your customer a project with good SEO promised.

Divs should be used. Tables are for tabular data, information you would normally display in a table. Not for actual page layout