WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Headings

for

From: Moore,Michael (DARS)
Date: Dec 21, 2009 1:48PM

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
>