- From: Joanmarie Diggs <jdiggs@igalia.com>
- Date: Mon, 10 Mar 2014 08:27:08 -0400
- To: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Hi all. Looking at the definitions of aria-setsize [1] and aria-posinset [2], it seems to me that the correct mapping w.r.t. ATK is not yet more object attributes. Instead, it would be to set the AtkRelation pair ATK_RELATION_NODE_CHILD_OF and ATK_RELATION_NODE_PARENT_OF as described in the ATK docs [3]. That mapping would bring ARIA widgets into alignment with native/platform toolkit widgets of the same type. Before proposing that mapping change, however, I have a question about the spec and the example therein: ========================================================= The following example shows items 5 through 8 in a set of 16. <h2 id="label_fruit"> Available Fruit </h2> <ul role="listbox" aria-labelledby="label_fruit"> <li role="option" aria-setsize="16" aria-posinset="5"> apples </li> <li role="option" aria-setsize="16" aria-posinset="6"> bananas </li> <li role="option" aria-setsize="16" aria-posinset="7"> cantaloupes </li> <li role="option" aria-setsize="16" aria-posinset="8"> dates </li> </ul> ========================================================= This example seems to suggest that web developers might not have to provide all child nodes. If that is indeed the case, then this mapping change might not work out after all. So.... Is there a use case where web developers know the set size and a subset of the children and the position of those children, but fail to know all of the children and their positions? --joanie, who wants to not have to know/care if something is ARIA or not [1] http://www.w3.org/TR/2014/PR-wai-aria-20140206/states_and_properties#aria-setsize [2] http://www.w3.org/TR/2014/PR-wai-aria-20140206/states_and_properties#aria-posinset [3] https://developer.gnome.org/atk/stable/AtkRelation.html
Received on Monday, 10 March 2014 12:31:18 UTC