- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Fri, 18 Oct 2013 08:39:16 -0400
- To: Léonie Watson <tink@tink.co.uk>
- Cc: "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
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:39:47 UTC