The Emperor

Semantically Correct

Semantically Correct coding is different to the more widely discussed Standards Compliant coding in that HTML markup is used in the correct places to define the correct kind of content. The most obvious example, and one that I have been banging on about for a while, is Table Free Design. HTML tables are in the standards - the problem is that, without any better way of doing things in older browsers, they have been used as a layout hack rather than what they were designed for - displaying tabular data.

Essentially we use HTML for structure and CSS for presentation.

I hope to make both Gabbble (the Blog) and Wick (the Wiki) both Standards Compliant and Semantically Correct.

Some important steps that need addressing:

• Bed And BReakfast - the misuse of <B> (and <I>) and <BR> tags.


• The Problem With The Font Tag.


• Anorexic Anchors.


• Getting Rid Of PRE.


• Semantic Lists.

---

Some links to other sites which explore the issue of Semantically Correct markup:

Standards don't necessarily have anything to do with being semantically correct and the discussion continued over at Stopdesign.

WCAG 1.0: Guideline 3. Use markup and style sheets and do so properly.

Using structural markup

10 Steps to Greater Usability & Accessibility: Structural Web

CSS accessibility problems: is markup dead?

Structural mark-up

Using real headers

Don't Fake Your Markup: Accessibility Issues for CSS

Wicklinks

Welcome (in: 52 | out: 3)
Semantically Correct (in: 44 | out: 44)
Table Free Design (in: 18 | out: 19)
<B>ed And <BR>eakfast (in: 12 | out: 32)
HTML (in: 8 | out: 7)
Semantic Web (in: 8 | out: 7)
Bed (in: 8 | out: 2)
Standards Compliant (in: 7 | out: 9)
Semantic Lists (in: 5 | out: 33)
Oriental Fonts (in: 5 | out: 1)
CSS (in: 4 | out: 6)
The Problem With The Font Tag (in: 4 | out: 21)
<BR>eakfast (in: 3 | out: 2)
How the Wick Works (in: 3 | out: 2)
<A>norexic </A>nchors (in: 2 | out: 33)
Wick (in: 2 | out: 3)

Syndicate

Syndicate the content on this site:

Blog