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

RE: 4.13.1 Bread crumb navigation - use of right angle brackets

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Sun, 27 Jan 2013 20:53:10 +0100
To: tink@tink.co.uk
Cc: 'Gez Lemon' <g.lemon@webprofession.com>, public-html@w3.org, steve.faulkner@gmail.com, 'Silvia Pfeiffer' <silviapfeiffer1@gmail.com>
Message-ID: <20130127205310311067.0fb705d0@xn--mlform-iua.no>
LĂ©onie Watson, Sun, 27 Jan 2013 16:14:25 -0000:
> " Realistically, the > is just decoration, so should be provided with CSS."
> Agreed. I'd even suggest that there is little to compel anyone to use 
> the > character at all, except perhaps for convention. It's a style 
> choice at this point of course.

I checked that VoiceOver doesn't pronounce e.g. this CSS.
  <style>nav a:after{content:">"}</style>
But have you checked that other screenreaders don't?

> "The examples provided should meet WCAG, so I suggest the following 
> (using an unordered list, but an ordered list would be fine in this
> context):
> <nav aria-label="You are here">
> <ul>
>   <li><a href="/">Main</a></li>
>   <li><a href="/products/">Products</a></li>
>   <li><a href="/products/dishwashers/">Dishwashers</a></li>
>   <li>Second hand</li>
> </ul>
> </nav>"
> Think this is a good example. 

1) Does it not meet the WCAG to do an <a> without @href, like the
   current example? <li><a>Second hand</a></li>
2) The current example is paragraph with links inside. To use a
   list means that one must turn each list into a paragraph - 
   visually, by the use of <style>nav li{display:inline}</style>.
   Thus, how about letting each list end with a <hr>, and use 
   that as the link separator? Here is a demo:

   It can even possible to use generated CSS inside the hr
   hr:before {content:">"}
leif halvard silli
Received on Sunday, 27 January 2013 19:53:40 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:30 UTC