- From: Léonie Watson <tink@tink.uk>
- Date: Wed, 9 Dec 2015 12:19:24 -0000
- To: "'Birkir Gunnarsson'" <birkir.gunnarsson@deque.com>, "'Bryan Garaventa'" <bryan.garaventa@ssbbartgroup.com>
- Cc: "'Matt King'" <a11ythinker@gmail.com>, "'James Craig'" <jcraig@apple.com>, "'Alexander Surkov'" <surkov.alexander@gmail.com>, <public-aria@w3.org>, "'White, Jason J'" <jjwhite@ets.org>, "'PF'" <public-pfwg@w3.org>
> From: Birkir Gunnarsson [mailto:birkir.gunnarsson@deque.com] > Sent: 07 December 2015 17:46 > The way that I saw aria-current was a quick and easy semantic equivalent of > using CSS to indicate or highlight an item in a list of items. > [...] > I have no problem not knowing the current element in a set of elements until > I move focus to (or virtual focus on) that element. > I don't have to know when I reach the common container. +1 The original use case was to indicate the current thing in a set, when that thing has focus. There may be use cases for conveying this information from the container, but I'm hard pressed to think of one. In fact the additional verbosity at the container level would probably be more of a hinderance than a help. We could make the spec text clearer about the intention of the attribute regarding where/when the information should be exposed perhaps? Léonie. -- @LeonieWatson tink.uk Carpe diem >
Received on Wednesday, 9 December 2015 12:20:25 UTC