Re: Using aria-selected on focusable elements

Hi Leonie,

I think the issue is that aria-selected is used in controls such that on
some platforms it becomes part of the selection model for a widget. I think
you are looking for something more global in nature.

It almost seems like you want something beyond "widget scope". Would this
also apply to breadcrumbs? We did not do a breadcrumb role in ARIA as we
thought it could be handled by existing widgets.

If you had this type of role how would you see a user interacting with it
differently from selection?

Note: If we do this it may require platform accessibility API changes on
each platform. This will also impact ATs.

Rich


Rich Schwerdtfeger



From:	Léonie Watson <tink@tink.co.uk>
To:	<public-pfwg@w3.org>,
Date:	10/18/2013 07:24 AM
Subject:	Using aria-selected on focusable elements



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.