E-mail List Archives
Re: Heading order/nesting - was RE: H1 header in iframe
From: Susan Grossman
Date: Aug 26, 2010 8:30AM
- Next message: Langum, Michael J: "The affect of "scope" attributes in
tags" - Previous message: Jared Smith: "Re: Heading order/nesting - was RE: H1 header in iframe"
- Next message in Thread: Jared Smith: "Re: Heading order/nesting - was RE: H1 header in iframe"
- Previous message in Thread: Jared Smith: "Re: Heading order/nesting - was RE: H1 header in iframe"
- View all messages in this Thread
> ...Interestingly, the new w3.org site uses two <h1>s on content page -
one for the logo and one for the document heading.
I was taught that you never use more than one H1 on a page, and have
followed this, without question on all sites.
And since I was taught there can't be an H2 without an H1, I use the H1 for
usually what's a combo Domain Level/ Site Level (Name of Company /
Application Name) In most corporate contracts, they combine domain/site so
I don't have to worry about breaking it up into headings.
Now you have me questioning my understanding of Web Semantics (different
from traditional Word Doc).
So is there an H1 rule or not? Is anything cut and dry?
Susan
On Thu, Aug 26, 2010 at 7:22 AM, Jared Smith < <EMAIL REMOVED> > wrote:
> On Thu, Aug 26, 2010 at 7:19 AM, Langum, Michael J wrote:
>
> > What is your best thinking about these headings BEFORE the <h1
> id="PageTitle">Page Title</h1>?
>
> Some will say that because you are not supposed to skip heading levels
> that this is somehow inappropriate. I've yet to see anything in
> accessibility or coding standards that indicates you can't do this.
> The WebAIM site and many others have a similar structure with no
> apparent issues. This allows direct access to the main content. In
> most screen readers, just hit the 1 key and you're at the main
> content. The logo/site name should probably be the <h1> on the home
> page
>
> Interestingly, the new w3.org site uses two <h1>s on content page -
> one for the logo and one for the document heading. If users generally
> expect one <h1> to be at the beginning of the main content, there's a
> possibility this could result in some confusion.
>
> Jared Smith
>
- Next message: Langum, Michael J: "The affect of "scope" attributes in
tags" - Previous message: Jared Smith: "Re: Heading order/nesting - was RE: H1 header in iframe"
- Next message in Thread: Jared Smith: "Re: Heading order/nesting - was RE: H1 header in iframe"
- Previous message in Thread: Jared Smith: "Re: Heading order/nesting - was RE: H1 header in iframe"
- View all messages in this Thread