The W3C HTML recommendations for tables … Hope you are very comfortable with HTML tables and you are efficient in designing page layouts using HTML Tables. There's a real risk of developers creating heavily nested tables, as was the case in the past. When you create an image, say in Photoshop or GIMP, it has a set width. In some situations tables are easier for layout; such as three columns or forms (albeit there are some great suggestions here for doing a pure css form layout so don't ignore those either.) When you are using tables to control page layout, there are some problems you need to be aware of. Assistive technologies use this information to provide context to users. Its layout is very similar to excel sheet so it may need no introduction. As you hover with your mouse above the fields you will see the current table dimmensions highlighted. Accessible tables need HTML markup that indicates header cells and data cells and defines their relationship. Tables are used to create databases. Don't use tables to create HTML layouts! It should also encourage people to go deeper and learn more about you. Nowhere do I advocate html tables for layout or suggest that css tables and html tables are the same thing. Let’s take a look at a basic example of HTML table style: Imagine looking at a row (horizontal) to see a single person and relevant information about them. Categories: Coding emails, Design One of the biggest challenges in designing an HTML email is ensuring that it displays consistently for all users, across all email clients. Before I begin, I want to first acknowledge the risks associated with using tables for a website's layout.