Re: Using Heading to Replace Skip Links

Hi,

I have been using WCAG 1.0 and implement it in a lot of sites since  
1999. I'm also a screen reader user. I understand the need to mark  
sections of a page with a heading, but what is a section in a  
page? :-) Is any menu a section? Is a breadcrumb a section? To an  
index engine, like Google, seems me that the headings are also (to me,  
like user is) a noble element to be indexed. What it (the Google)  
"think" about my waste of a noble element thousands of times repeated  
in my website with the words "main menu"?!

When the WCAG 2.0 cames I read the note 2 of "Section Headings:  
Understanding SC 2.4.10" of WCAG 2.0:

"Note 2: This success criterion covers sections within writing, not  
user interface components. User Interface components are covered under  
Success Criterion 4.1.2." http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-headings.html

I underline "...within writing ...not user interface". I interpret  
this as "headings is to use in main content... and a menu, a  
breadcrumb is interface, so don't use headings on it". And more: I  
think this is a better solution to screen reader users - the user will  
have more diversity of jumps and will know that headings are on the  
main content.

Am I wrong in my interpretation more or less free?

Jorge Fernandes

++início do rodapé
 ⠨⠚⠕⠗⠛⠑ ⠨⠋⠑⠗⠝⠁⠝⠙⠑⠎ |  
jorge.f@netcabo.pt
UniversalAccess.blogspot.com

On 16 May 2012, at 16:32, Sailesh Panchang wrote:

> Typically left nav or breadcrumb nav and sometimes
> even main content, though there might be other headings on the page.
> One may insert invisible headings to aid screen reader navigation ...
> this is exploiting the screen reader's heading navigation feature.
> This will not work for sighted keyboard users.

Received on Wednesday, 16 May 2012 21:03:10 UTC