WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Headings

for

From: Geof Collis
Date: Dec 21, 2009 2:15PM

Hi Mike

They are not there to look like headings for the sighted. If you
follow the skip links it will read out that it is a main menu and categories.

As for the main heading, I dont believe a navigation is a main
heading, the main heading is the start of the main content and if I
start moving the menus further down the page then it will have to
come after all the content and cause problems for other users and I
dont believe in slapping navigation into my content just to get the
headings nested correctly.

cheers

Geof




At 03:48 PM 12/21/2009, you wrote:
>My own personal warped opinion is that if it visibly looks like a
>heading then it should be coded as a heading. Why would you want
>headings for sighted users that are not available for screen reader
>users? As far as the heading order goes, you can control that
>through the code order with CSS and/or make the main heading an h1
>and the other headings lower heading. If I want to get to the main
>heading using a screen reader I can just whack the key for that
>heading level - the "1" key in JAWS.
>
>Mike Moore
>(512) 424-4159
>
>
>-----Original Message-----
>From: <EMAIL REMOVED>
>[mailto: <EMAIL REMOVED> ] On Behalf Of Geof Collis
>Sent: Monday, December 21, 2009 1:03 PM
>To: WebAIM Discussion List
>Subject: Re: [WebAIM] Headings
>
>But I want the first heading to be the main content, I have skip
>links, they are marked up as lists and I use role landmarks, is that
>not enough?
>
>At 01:55 PM 12/21/2009, you wrote:
> > > They are, but is it an WCAG issue if they aren't coded as headings?
> >
> >Looking at the sufficient techniques for WCAG 2.0 4.1.2
> >(http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html),
> >I would think that they should be marked up as headings.
> >
> >Tim
> >