W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: Recursive Links in menu bars [SEC=UNOFFICIAL]

From: Ian Yang <ian@invigoreight.com>
Date: Mon, 17 Sep 2012 12:58:17 +0800
Message-ID: <CABr1FseCC2siOyNbHWOTaSmRBq_aB11_ULSG50uBMHy0M+hTbA@mail.gmail.com>
To: w3c-wai-ig@w3.org
Imho, the use of <strong> is semantically correct because it makes the
markup meaningful. <strong> satisfies the need of strongly emphasis the
current item; while <span> doesn't really have a specific meaning so it
fails to make the markup meaningful.

Ian Yang

On Mon, Sep 17, 2012 at 8:20 AM, ANDERSEN, Leon <
Leon.Andersen@fahcsia.gov.au> wrote:

> I prefer your first option, assuming that the 'current page' information
> is hidden off screen via CSS, as I'm not convinced whether the use of
> <strong> is correct semantically speaking. Plus, if a bold effect on the
> link is the aim then this is easily achievable with CSS. If it's for the
> benefit of screen reader users, from what I understand even though it is
> intended the speech output has some audible emphasis on the word, they
> don't. Also with regard to adding a 'title' to convey the message, this
> again from my understanding will not be read by screen readers and is not
> available to keyboard only users. And while aria-selected="true" exists I
> don't think it is appropriate for use in this type of situation.
> So considering all of the above, and if the link can't be removed, maybe
> this could work:
> <ul id="nav">
> <li><a href="#">page 1</a></li>
> <li class="current"><a href="#" title="current page"><span
> class="sr">Current page: </span>Page 2</a></li> ...
> </ul>
> One downside of this is screen readers that do announce 'title' will get
> the message twice.
> Leon
Received on Monday, 17 September 2012 04:58:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:45 UTC