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. 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
On 2/12/2015 6:45 AM, Richard Schwerdtfeger wrote:
http://lists.linux-foundation.org/pipermail/accessibility-ia2/2015-September/001939.html
Alex, why would you not want the active state on non-widgets? For
example, if you have a list of links in a navigation landmark section
you do not want to mix focus with active. This is because what is
active was the last navigation item you activated.
Rich
Rich Schwerdtfeger
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: [email protected]
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
