- From: Michiel Bijl <michiel@agosto.nl>
- Date: Thu, 28 Jul 2016 04:04:09 +0100
- To: Jason Kiss <jason@accessibleculture.org>
- Cc: Birkir Gunnarsson <birkir.gunnarsson@deque.com>, Matt King <mck@fb.com>, ARIA Working Group <public-aria@w3.org>
That is good advice Jason. Would it be enough to link to the navigation role/nav element warning about this? It makes sense to me to make it navigation as that's its purpose. I'd argue that a breadcrumb is more important than cruft in a fat footer. That said, if not a nav, what then? —Michiel > On 28 Jul 2016, at 03:15, Jason Kiss <jason@accessibleculture.org> wrote: > > Is it always appropriate for breadcrumbs to be a navigation landmark? > Might it not depend on the site/page and the other navigational > sections it contains? I'd say it's a judgment call for the author > whether the breadcrumbs represent a section of "major navigation > blocks". Yes, that is a note from the definition of <nav>, but given > that <nav> maps to a navigation landmark, there's a certain > equivalence. It's how I decide whether or not a navigation block > deserves the <nav> element: Is it so major a navigation block that it > deserves to be a landmark? I think that landmarks tend to get overused > and thus lose their effectiveness: how useful is a landmark in a sea > of landmarks? > > I often recommend against breadcrumbs being a navigation landmark if > there are a number of other navigational landmarks, e.g. main menu, > section menu, fat footer menu with more than the typical links to > copyright, privacy, etc., and especially if these exist among a whole > bunch of other landmarks. > > Maybe it's worth noting something along these lines in the authoring practice? > > Jason > >> On Thu, Jul 28, 2016 at 12:10 PM, Michiel Bijl <michiel@agosto.nl> wrote: >> Oh right, well, the agenda for the week after that works too :) >> >> The markup you suggest is what is in the code example. As for a separate >> landmark region, you mean a new role of breadcrumb? >> >> —Michiel >> >> On 28 Jul 2016, at 00:27, Birkir Gunnarsson <birkir.gunnarsson@deque.com> >> wrote: >> >> Hi >> >> We are not having a meeting until the 8th, right? >> I would like to suggest that the breadcrumb be exposed as an ordered list >> inside a labeled navigation landmark. >> <div role=”navigation” aria-label=”breadcrumb”> >> <ol> >> <li><a href=”/”>Main page</a></li> >> <li><a href=”/categorypage”>Category page</a></li> >> <li><a href=”/categorypage/subpage” aria-current=”page”>Current >> subpage</a></li> >> </ol> >> </div> >> >> I think a separate landmark region is appropriate for this, of course it is >> just one man’s opinion. >> >> >> From: Michiel Bijl [mailto:michiel@agosto.nl] >> Sent: Wednesday, July 27, 2016 6:48 PM >> To: Matt King <mck@fb.com> >> Cc: ARIA Working Group <public-aria@w3.org> >> Subject: APG: Breadcrumb design pattern >> >> Hi Matt, >> >> During today's London Accessibility Meetup I've pushed the breadcrumb design >> pattern to the Editor's Draft after a short review with the crowd. Can we >> add this to next week's agenda please? It includes a short description and >> code example all ready to go. >> >> —Michiel >
Received on Thursday, 28 July 2016 03:04:41 UTC