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

RE: on headings, labels, links, and image maps

From: Jamal Mazrui <Jamal.Mazrui@fcc.gov>
Date: Fri, 28 May 2010 10:29:21 -0400
Message-ID: <495842C725E7F8459B0460FC3A1060B10443D3EB@P2PXMB01S1.fccnet.win.fcc.gov>
To: <richard@userite.com>, "Andrew Kirkpatrick" <akirkpat@adobe.com>
Cc: <w3c-wai-ig@w3.org>
I agree, and think that a heading where the main content of the page
starts is more effective than a skip navigation link.  In fact, my
experience with SkipNav links has had surprisingly mixed results --
whether with a different screen reader, different version of the same
screen reader, or an apparently different HTML coding technique that
another web site uses.  It works as intended sometimes, but other times
does not skip ahead, or even worse, reloads the virtual buffer of the
screen reader, returning focus to the top.

Jamal

 


-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
Behalf Of Richard Warren
Sent: Friday, May 28, 2010 10:15 AM
To: Andrew Kirkpatrick
Cc: w3c-wai-ig@w3.org
Subject: RE: on headings, labels, links, and image maps

1) When using a screenreader I can jump up and down a well constructed
page quite easily by going to the next or previous heading. If the
headings are not nested properly I start to wonder if I have missed
something and have to go into virtual focus to read all the surrounding
text. So for me "should" is a pretty imperative should.
2) Guidelines are just that - guidelines. If you have a very good reason
not to nest headings properly, and can at the same time ensure that the
reading sequence is logical, then fair enough. But I would love to see
an example of where this has been achieved.

Richard
http:www.userite.com


On Thu, 2010-05-27 at 11:47 -0700, Andrew Kirkpatrick wrote:
> 1) Headings - yes you are correct, level A requires coded headings so 
> that blind users can get an overview of teh page and jump to sections 
> of interest by listing the headings. Level AA requires these headings 
> to be nested correctly (ie form a logical semantic structure)
> 
> I did a bit of fact-checking to answer my own question:
> Headings do not need to be nested properly to comply with WCAG 2.0.
This is desirable, but not required. If you look at the How To Meet
information for SC 2.4.10 (2.4.10 Section Headings: Section headings are
used to organize the content. (Level AAA)) you'll see the note below:
> 
> "In HTML, this would be done using the HTML heading elements (h1, h2, 
> h3, h4, h5, and h6). These allow user agents to automatically identify
section headings. Other technologies use other techniques for
identifying headers. To facilitate navigation and understanding of
overall document structure, authors should use headings that are
properly nested (e.g., h1 followed by h2, h2 followed by h2 or h3, h3 f
followed by h3 or h4, etc.)."
> 
> Note the "should" - it doesn't say "must".  That's my take on it...
> AWK
Received on Friday, 28 May 2010 14:29:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:34 GMT