E-mail List Archives
Re: WCAG
From: Geof Collis
Date: Dec 16, 2009 3:03PM
- Next message: jfoliot@stanford.edu: "Re: WCAG"
- Previous message: Jared Smith: "Re: WCAG"
- Next message in Thread: jfoliot@stanford.edu: "Re: WCAG"
- Previous message in Thread: Jared Smith: "Re: WCAG"
- View all messages in this Thread
Thanks Jared, just what I thought. I have the Landmarks there but it
didn't detect them and if I were to put headings it would throw off
my whole design
cheers
Geof
t 04:25 PM 12/16/2009, you wrote:
>On Wed, Dec 16, 2009 at 2:03 PM, Geof Collis < <EMAIL REMOVED> > wrote:
>
> > Is this correct?
>
>No. It's silly to expect or require that all things that might
>possibly be, look like, or even actually are navigation elements be
>proceeded by a heading. How many sites do you know of that have a
>"Navigation" heading immediately before the main navigation links?
>It's reasonable to assume that both sighted and non-sighted users will
>understand that a group of links near the beginning of the page that
>link to major areas of the site are probably the navigation.
>Suggesting that developers must explicitly tell the user what they are
>via a heading is a bit extreme.
>
>Now if the group of navigation items already has a visible header,
>then yes, that header should be marked up as a header at the
>appropriate level.
>
>Additionally, adding the ARIA role="navigation" allows assistive
>technology to explicitly know the section of the page that is
>navigation.
>
>Jared Smith
>WebAIM
>
- Next message: jfoliot@stanford.edu: "Re: WCAG"
- Previous message: Jared Smith: "Re: WCAG"
- Next message in Thread: jfoliot@stanford.edu: "Re: WCAG"
- Previous message in Thread: Jared Smith: "Re: WCAG"
- View all messages in this Thread