W3C home > Mailing lists > Public > public-html@w3.org > February 2013

Re: proposal: clarification of nav element

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 4 Feb 2013 13:34:54 +0000
Message-ID: <CA+ri+Vk2H5Jx2j9s4x0pWtH9qEmvBm2mngTd1fgimest-h9Lsg@mail.gmail.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Cc: HTMLWG WG <public-html@w3.org>
Hi Leif,

>the blog post says that to blind users, it is often better if list
>elements are not used as navigation link containers.

that is not what I was referring to, but that advice was based on one
perosons opinion, if you read through the comments you will find comments
from people such as victor tsaran, marco zehe and leonie watson that
contradict that.

regards
Steve

On 4 February 2013 13:18, Leif Halvard Silli <
xn--mlform-iua@xn--mlform-iua.no> wrote:

> Steve,
>
> the blog post says that to blind users, it is often better if list
> elements are not used as navigation link containers. If that is a real
> issue, and *that* is the message you want to send, then, explaining (in
> some other part of the spec) about <ul role="presentation">, seems just
> as relevant, since I doubt that authors are going to stop using lists
> for navigation.
>
> Speaking personally, then for a while I thought that <nav> was a list
> container (similar to <ul>, <ol> and <menu>) - I probably somehow mixed
> it up with <menu>. But I have never thought that <nav> was "list
> container container".
>
> Leif
>
> Steve Faulkner, Mon, 4 Feb 2013 13:09:54 +0000:
> > BTW
> >
> > it may be after discussion that it is decided that no changes to the spec
> > are needed as the spec is clear as it can be.
> >
> > regards
> > Steve
> >
> > On 4 February 2013 11:48, Steve Faulkner <faulkner.steve@gmail.com>
> wrote:
> >
> >> Judging from comments on a recent blog post [1] there appears to be some
> >> confusion in the developer community about nav element semantics and
> what
> >> it does as implemented.
> >>
> >> I propose that an explanatory note be added to the current definition
> text
> >> to make it clear that <nav> does not equal a list
> >> of navigation linksand that if a list of link is what is required then
> use
> >> a list.
> >>
> >> thoughts?
> >>
> >> [1] http://css-tricks.com/navigation-in-lists-to-be-or-not-to-be/
> >>
> >> --
> >> with regards
> >>
> >> Steve Faulkner
> >>
> >>
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Monday, 4 February 2013 13:36:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:37 UTC