On 08/31/2015 05:12 PM, Alexander Surkov wrote: > Hi, Joanie. I guess ATK didn't want to have active state just because an > item is focusable or selectable rather than deny a focsuable/selctable > items being active, otherwise I don't see a point for this; also it has > to be in conflict with aria-current. Anyway regardless what ATK has, > what is the point of having both object attribute and state for same thing?
If aria-current's value were a boolean, then the state would be sufficient -- and much more performant than the object attribute. However, aria-current has a value through which an author can indicate the context in which the element is current. This, of course, cannot be exposed via the state. But checking every last element's object attributes on the off chance it has aria-current set on it is not ideal. The state indicates it's worth getting the object attributes. --joanie _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
