At 3:37 PM -0800 1/11/08, roxanne sutton wrote:
>I am looking for information regarding the usage of H1-H6 tags. I
>have followed general guidelines of Eric Meyer and Jeffrey Zeldman. I
>am trying to keep this site as standard as possible: 
>http://www.roxstyle.com/transfer/blssi/InBaseline_Phase_2/v2-optimized/template-2.html
>Today in a meeting with an SEO person, it was suggested that H1 be
>used for the top headline- not the logo (i can live with that), also
>that the image be in the markup and not using the background image
>technique (i can understand the SEO reasons behind this), but then it
>was suggested to only use h2 and drop all h3-h6 and use the strong
>tag instead. This seems to me, that we loose a lot of hierarchy and
>hooks for css, so i'm wondering what other standards people are doing.

Header markup is very important for screen reader users because it 
allows them to navigate easily through content-rich pages. As per our 
accessibility best practices at the University of Illinois, h1 should 
be reserved as a title description of the page and also duplicated in 
the document title. h2 and down should be used to structure the page, 
much like you did with your template-2.html. It's also a good idea to 
precede unordered/ordered lists with a header tag, again to help 
screen reader users navigate.

I'm with you, I'd be reluctant to let go of h3-h6 (although I rarely 
use h5-h6).

Peace,

-Tim
-- 
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
        Tim Offenstein  ***  Campus Accessibility Liaison  ***  (217) 244-2700
             CITES Departmental Services  ***  www.uiuc.edu/goto/offenstein
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to