W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2005

RE: Navigational features

From: Becky Gibson <Becky_Gibson@notesdev.ibm.com>
Date: Mon, 12 Dec 2005 08:45:45 -0500
To: "WCAG " <w3c-wai-gl@w3.org>
Message-ID: <OF0961E48F.C8C91028-ON852570D5.004B6A20-852570D5.004B9A0D@notesdev.ibm.com>

<John wrote>
I agree with Loretta's and Gregg's suggestion that we list Jim's example
under Common Failures. In fact, it could be listed under both 2.4.1 and
1.3.1, I think.
</John>

Here is a common failure example.  I tried to use technology neutral 
language for the common failure description, then followed with an 
HTML/CSS specific example. 

Common Failure: Using mechanisms to visually mark the structure of a 
document rather than using the structure of the language. 
For example, creating a CSS class that makes heading text large, blue and 
bold:
.myheading {
        font-size:x-large;
        font-weight:bold;
        font-family:Times, serif;
        color:blue;
}
Then using that class to visually mark headings:
<div class="myheading">Section 1</div>
<p>data for section 1.....</p>
<div class="myheading">Section 2</div>
<p>data for section 2....</p>
......
rather than styling the header element:
<h2 class="myheading">Section 1</h2>
<p>data for section 1....</p>
<h2 class="myheading">Section 2</h2>
<p>data for section 2....</p>
......

-becky


Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com
Received on Monday, 12 December 2005 13:46:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:41 GMT