On 13 Dec 2006, at 17:54:14, Barney Carroll wrote:
Thierry Koblentz wrote:
Also, I think (I may be wrong though) the WCAG 2 (FWIW) recommends to
"display" the elements in the same sequence as they show in the
markup.
Would be interested to see if this is the case. Quickly skimmed the
guidelines but couldn't find anything.
WCAG 2.0 requires that "When the sequence of the content affects its
meaning, that sequence can be programmatically determined." [1]
"Understanding WCAG 2.0" explains what is meant by a "meaningful
sequence" [2] and links to "Techniques for WCAG 2.0" which gives an
example of incorrect use of CSS breaking this guideline, in which
positioning is used to provide the appearance of two lists when only
one list is present in the markup. [3]
Basically, what it all comes down to is that you shouldn't use CSS to
arrange content in such a way as to add meaning: the content should
be marked up in a meaningful way to start with.
Given that moving around the "chunks" of a page (navigation, header,
etc.) doesn't actually add further meaning to the content of those
chunks, those considerations don't (IMHO) apply in the case under
discussion.
HTH,
Nick.
[1] <http://www.w3.org/TR/WCAG20/guidelines.html#content-structure-
separation>
[2] <http://www.w3.org/TR/UNDERSTANDING-WCAG20/Overview.html#content-
structure-separation-sequence>
[3] <http://www.w3.org/TR/2006/WD-WCAG20-TECHS-20060427/
Overview.html#F1>
--
Nick Fitzsimons
http://www.nickfitz.co.uk/
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
