WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Seeking selected link in Carousel examples

for

From: Birkir R. Gunnarsson
Date: Sep 9, 2014 5:09PM

This is a long-discussed problem actually.
You would have to map any link (or other underlying focusable element)
as a tab before you can use aria-selected.
See for instance:
http://www.romaingervois.fr/implementations/en/carousel.html

You could map them as buttons and then use aria-pressed="true" on the
selected one, but that really would be presenting the user with
something very different from what you are displaying.

You could use role="presentation" on the currently active one. It
would still remain focusable but would not be announced as a
link/button/tab (whatever the basetype is that you use), so that way
it would be different from the rest. This might be ok if you visibly
mae the active dot/link look like it is not a link or if you made it
look disabled you could use aria-disabled for the equivalent
programmatic distinction.
Then there is always adding off-screen hidden text of course to the active link.

We do need an aria attribute that indicates active or selected that
can be used on any focusable, even possibly on non-focusable element
in a set of elements.
Maybe in the next version of the ARIA spec, who knows.
Cheers
-B


On 9/9/14, Gunderson, Jon R < <EMAIL REMOVED> > wrote:
> The w3c aria working group is aware of this issue and is anticipating on
> having an aria property in aria 1.1 specification to solve this problem
>
> Jon Gunderson
> Sent from my iPhone
>
>> On Sep 9, 2014, at 12:49 AM, "Bryan Garaventa"
>> < <EMAIL REMOVED> > wrote:
>>
>> Can you send through the markup for one of the actionable dots?
>>
>>