W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2012

Re: heading level order

From: Johnson, Shawn [USA] <johnson_shawn@bah.com>
Date: Tue, 29 May 2012 12:53:21 +0000
To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <CBEA3DDA.C87B%johnson_shawn@bah.com>
Thanks for everyone's responses so far.  I work with Ian and this has been
a long running discussion on our project.

I'm going to follow-on here.  If you are building a "site" with many
"pages", isn't it typical that you have a shared CSS file for the entire
site?  In that shared.css, wouldn't you typically define global styles for
Heading elements?  I ask this way, because this is the way I have always
seen.  Some "pages" may have an H1, H2, H3, while others may have only 3
H3 tags and no H1 tag.  We want to enable the most accessible site we can,
however we also want to figure a way that doesn't create a lot of extra
work for every "page".  Maybe the heading role is the answer?

If we go with roles, do we do that instead of using header tags?  Does
this pose an issue for older readers?

-=Shawn Johnson

On 5/25/12 3:52 PM, "David Best" <davebest@ca.ibm.com> wrote:

>Ian, it is recommended that you use a structured Header hierarchy of
>Headers. If a screen reader navigates by Headers, and skips from a h2 to a
>h4, they might assume they are missing information that the screen reader
>is not picking up, but web sites rarely follow this principle. You can
>Header levels, but you might prefer to use CSS to style your Header
>structure. Also, you can use the W3C/WAI ARIA code to make text look like
>Headers to screen readers. See the WAI/ARIA "5.3.3. Document Structure"
>the Heading Role.
><div role=heading aria-level=2>Section Content Sample</div>
>Cheers, David
>From:	"Stewart, Ian [USA]" <Stewart_Ian@bah.com>
>To:	"w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
>Date:	05/25/2012 03:17 PM
>Subject:	heading level order
>My name?s Ian Stewart, I?m a GWT/Drupal developer and new to
>but I?ve done extensive research lately in order to make one of my
>as accessible as possible.
>Right now, I?m confronted with an interesting issue regarding heading
>levels.  Heading levels, from my point of view, have always been primarily
>a visual style cue.  Often an <h4> works better for CSS inheritance
>than an <h3>, for no reason other than visual style.
>Recently, our accessibility tester approached me with an interesting
>She suggested that the reader is expecting heading levels to make sense as
>if the page is a linearized document, with each depth representing a
>consistent level of detail.  What do you all make of this statement?  Does
>jumping from an <h2> to an <h4> on a page for stylistic reasons truly
>lessen the intuitiveness of the page for a screen reader?  Is subclassing
>an <h3> to fit my style needs worth having <h2>s always followed by <h3>s?
>Thanks for your thoughts, I found it an interesting question.
Received on Tuesday, 29 May 2012 12:54:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:44 UTC