- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Wed, 3 Aug 2016 10:50:09 -0400
- To: "Gunderson, Jon R" <jongund@illinois.edu>, Cynthia Shelly <cyns@microsoft.com>, Accessible Rich Internet Applications Working Group <public-aria@w3.org>
- Cc: "wai-xtech@w3.org" <wai-xtech@w3.org>
Hi Jon,
On 2016-08-03 9:15 AM, Gunderson, Jon R wrote:
> Joseph,
>
> Does managed states include the calculation of aria-setsize, aria-posinset and aria-level?
>
> Jon
See the section on "Group Position" in the Core-AAM, where the user
agent has some responsibility for calculating their associated AAPI
representation:
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_additional_position
But, to split a few hairs:
1. aria-setsize, aria-position, and aria-level are not states. They are
properties.
2. They are DOM attributes, not AAPI features.
3. AAPI states are dynamic in that they change over time. For example,
what is selected, what has keyboard focus, what is visible, what is
checked, and so on, change as the user interacts with the page.
Setsize, posinset, and level are fixed. There is a chance they might
change, but that's rare.
The action Cynthia is working on has to do with changing AAPI states,
and which changes the user agent manages implicitly.
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
Received on Wednesday, 3 August 2016 14:54:11 UTC