Skip to content

A podcast for those who design, develop and run websites.

Boagworld is the personal website of Paul (the Wurzel) Boag who lives in the heart of rural Dorset. He produces a weekly podcast along with Marcus (pop star) Lillington on all things relating to building and running websites.

Latest shows

138. Freeform
In this week's show the entire boagworld production team answer listener questions.
137. Adobe
In this week's show, Aral Balkan joins us to discuss the release of Adobe CS4 and we discuss how not to get blacklisted by google.
136. Stagnation
In this week's show we talk about overcoming stagnation and Ed Merritt shares a technique to achieve fixed footers without the use of javaScript.
135. Libraries
In this week's show we talk with John Resig on javaScript libraries and address the question what is more important when we release an app: speed or quality?
134. Chrome
In this weeks show we give you advice on choosing the right hosting company, Teifion and John send us a review of dConstruct and of course we discuss the release of Google Chrome, can it topple IE?

or view all shows

Have your say

Leave a message for the show...

Buy my book: The website owners manual. A book for all those involved in designing, developing or running websites on a daily basis.

Accessibility and table layout don't mix

Published on: June 30, 2005 by Paul Boag

Here is my controversial point for the day. A point I am not sure if I agree with or not: It is impossible to conform to anything but the most basic level of accessibility if you are using tables to control layout.

As anybody who reads this blog regularly already knows, there are two basic approaches to building a web site:

  1. The traditionally used, table based design approach
  2. The officially approved, web standards methodology

Tables based design

Tables based design uses tables to slice up a design into grids and then reassemble it like a jigsaw. Unfortunately, the vast majority of web designers still use this method to construct web pages even though it is unnecessary and highly inefficient.

Web standards

The web standards approach involves separating content from design. Content is held in your (X)HTML page while the layout and presentation is held in a file called a cascading style sheet (CSS).

Short guide to accessibility

Especially here, in the UK the W3C guidelines on web site accessibility (WAI) are the defining standard in web accessibility. These guidelines are broken into three levels:

  1. Priority One - All sites must conform to this level
  2. Priority Two - All sites should conform to this level
  3. Priority Three - All site can conform to this level

The controversial bit

Checkpoint 3.3, which is a priority two issue states:

Use style sheets to control layout and presentation.

In short, this is saying that you cannot use tables to control layout. This checkpoint may well demonstrate that the W3C does not live in the real world where many web designers only know how to design using tables, but nevertheless there seems to be no getting around what the checkpoint says.

I would be interested in other people's interpretation of this guideline. Am I missing something here?

Comments

Comments are for the discussion of this post. If you have other questions / comments then post them to the forum or send me an email

  • Post by ed on September 10, 2005 12:47 AM

    "Use style sheets to control layout and presentation" - that does not say "Use style sheets to control layout and presentation, and do not use any other method for layout too." - though I wouldn't use tables any more anyway.

  • Post by Paul Boag on September 11, 2005 9:08 AM

    Yeah, I am not convinced that I am totally convinced by this either but its an interesting idea :)

Leave a comment

Additional Information

Supporting boagworld

Boagworld only exists thanks to the kind support of the following people. Check them out.

Speaking and writing

Powered by Feed Informer