Hi Jamie,
Thanks for making that clearer. Comments inline.
On 2015-12-01 7:42 PM, James Teh wrote:
The active state in the IA2 spec says:
This state can be used to indicate the current active item in a
container, even
if the container itself is not currently active. In other words
this would indicate
the item that will get focus if you tab to the container.
So, it basically maps to aria-activedescendant.
Put another way, the item has focus when the container is active. That's
not what aria-current means. The current item may or may not have
focus, and can remain current even when another item in the container
has focus. IA2's active state has a different meaning than ATK's,
apparently.
One question: the quote above says the item has the active state when
it's container is non-active. Then when the container becomes active,
the item then has a focused state. Does it keep the active state after
it has gained focus? I know, the question is likely irrelevant to the
current discussion, but I am curious about details.
That technically conflicts somewhat with the idea of aria-current.
The question is whether ATs currently use this solely for its
currently documented purpose. (FWIW, NVDA doesn't use it at all yet.)
If they do, this needs to be discussed with other AT vendors or a new
state needs ot be used.
Jamie
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
