W3C home > Mailing lists > Public > public-pfwg@w3.org > October 2013

RE: Using aria-selected on focusable elements

From: Léonie Watson <tink@tink.co.uk>
Date: Fri, 18 Oct 2013 13:57:58 +0100
To: "'Alexander Surkov'" <surkov.alexander@gmail.com>
Cc: "'W3C WAI Protocols & Formats'" <public-pfwg@w3.org>
Message-ID: <000301cecc01$ac7315a0$055940e0$@tink.co.uk>
Alexander Surkov wrote:
"Can I have some real life examples of it please?"

To differentiate the link leading to the current page in the main navigation
of a website:

<ul>
   <li><a href="home.html">Home</a></li>
   <li><a href="about.html" aria-current="true">About</a></li>
   <li><a href="contact.html">Contact</a></li>
</ul>

Similarly to indicate the currently selected step in a process indication
bar:

<ol>
   <li><a href="1.html">Provide your name</a></li>
   <li><a href="2.html">Provide your address</a></li>
   <li><a href="3.html" aria-current="true">Provide your phone
number</a></li>
</ol>

A visual indication is easy to provide in these circumstances, but
programmatic indication is more cumbersome. In the above situations, a
screen reader might read the link text followed by "current".

>From a UX perspective "selected" after the link text would probably be
better, but as previously noted that would lead to more confusion than it
was worth.

Léonie.

-----Original Message-----
From: Alexander Surkov [mailto:surkov.alexander@gmail.com] 
Sent: 18 October 2013 13:39
To: Léonie Watson
Cc: W3C WAI Protocols & Formats
Subject: Re: Using aria-selected on focusable elements

Hi. I agree it's clearer when one attribute is not used for different
proposes. If new use case has a different AT API mapping than aria-selected
on selectable widget items then it should be a big confusion because items
maybe focusable too. But I should admit I don't understand the proposed use
case. Can I have some real life examples of it please?
Thank you.
Alexander.

On Fri, Oct 18, 2013 at 8:23 AM, Léonie Watson <tink@tink.co.uk> wrote:
> Hello,
>
>
>
> Resurfacing an idea from Steve Faulkner [1], and consequently put into 
> the PF tracker against ARIA 1.1 [2].
>
>
>
> The original suggestion was for aria-selected to be permitted on any 
> focusable element. The use case being to indicate things like the 
> currently selected page, or the current step in a process.
>
>
>
> James Craig noted (in the tracker) that although the use case is 
> sound, aria-selected may not be an appropriate solution.
>
>
>
> I wonder therefore whether a new attribute, perhaps aria-current, 
> could be introduced to solve this use case?
>
>
>
> Léonie.
>
>
>
> [1] http://lists.w3.org/Archives/Public/wai-xtech/2012Jul/0006.html
>
> [2] https://www.w3.org/WAI/PF/Group/track/issues/587
>
>
>
> Carpe diem.
>
>
Received on Friday, 18 October 2013 12:58:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:44:56 UTC