E-mail List Archives

Re: Headings

for

From: Margit Link-Rodrigue
Date: Dec 21, 2009 2:33PM


Geof,

I would make Main Menu, Categories, and Search this Site <h2> headings and
apply a style class so that you can keep the look you have. This would still
allow you to keep your heading 1 where you have it now - to mark up the
start of your main content. I think this is in line with WCAG 2
recommendation, take a look at http://www.w3.org/TR/WCAG-TECHS/H42.html. I
like to have as much structural markup as possible, I think of headings a
little bit like the outline for a table of contents just like in a Word
document.

On another note, the Default Colors link in your Main Menu goes to a page
that doesn't load the stylesheet correctly. It loads as all white text on
white background for me, not sure if you are aware of that.

Margit


On Mon, Dec 21, 2009 at 3:06 PM, Geof Collis < <EMAIL REMOVED> > wrote:

> Hi Andrew
>
> I think the argument here is that my navigation are supposed to be
> headings, but I dont see it that way, navigation is navigation and
> then there is content. I dont see a need to use headings as I have
> said before, all I have is bold text to signify that it is a mainn
> navigation and categories, if I chose not to put any text then there
> would be no need to put headings at all.
>
> cheers
>
> Geof
>
>
>
> At 03:59 PM 12/21/2009, you wrote:
> >Geof,
> >Maybe you already fixed it, but when I look at the code I see one
> ><h1> and two <h2> elements, and in my book those count as headings.
> >
> >Thanks,
> >AWK
> >
> >Andrew Kirkpatrick
> >
> >Senior Product Manager, Accessibility
> >
> >Adobe Systems
> >
> > <EMAIL REMOVED>
> >
> >
> >-----Original Message-----
> >From: <EMAIL REMOVED>
> >[mailto: <EMAIL REMOVED> ] On Behalf Of Moore,Michael
> (DARS)
> >Sent: Monday, December 21, 2009 3:48 PM
> >To: WebAIM Discussion List
> >Subject: Re: [WebAIM] Headings
> >
> >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
> > >