- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Tue, 2 Aug 2016 14:36:25 -0400
- To: 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 Cynthia,
On 2016-08-02 1:22 PM, Cynthia Shelly wrote:
> I could use some input on Issue 980. In particular, does anyone know the history behind "managed states" (Rich?)
You probably already know this, but the one clue I know of is in the
Core-AAM [1]. The set of managed states are the ones that change
regardless of the presence of an aria-* state or property.
That means that these are AAPI states that are managed by the user agent
even when the author has not used ARIA. As an example (warning:
speculation ahead), when a document loads into the browser, there is a
point where it is considered loaded, and the browser fires an onloaded
event. I speculate, for example, that the user agent initially sets
STATE_BUSY while the document is loading, and then clears it when the
document is loaded (note: using ATK-AT-SPI state here).
Somewhere, for each AAPI, there is a list of states it supports. See,
for example, Mozilla's list of MSAA states [2]. Which ones are managed
by the browser irrespective of ARIA?
[1]
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#statePropertyMappingGeneralRules,
item 1.
[2]
https://developer.mozilla.org/en-US/docs/Web/Accessibility/AT-APIs/MSAA/States
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
Received on Tuesday, 2 August 2016 18:40:16 UTC