PF/ARIA/BestPractices/API MSAA

From W3C Wiki
< PF‎ | ARIA‎ | BestPractices

Starter resources: http://developer.mozilla.org/en/docs/ARIA_to_API_mapping, http://www.w3.org/WAI/PF/Group/adaptable/#statemapping

States and Properties module User Agent mapping via MSAA
disabled MSAA:STATE_SYSTEM_UNAVAILABLE
checked MSAA: STATE_SYSTEM_CHECKED
expanded *If the hidden property is set to true : MSAA:STATE_SYSTEM_COLLAPSED. *If the hidden property is set to false: MSAA:STATE_SYSTEM_EXPANDE
haspopup *This state should be mapped to true on Windows systems when an event handler has a role of pop-up menu. MSAA: haspopup
invalid MSAA: no mapping - In the case of MSAA the user agent should provide a specialized API to return its value. Alternatively, if the user agent provides a specialized API for [XForms] it may provide invalid(), outOfRange(), or empty() (returns true when required but not available). This information is computed from the instance data associated with the form element.
multiselectable MSAA:STATE_SYSTEM_EXTSELECTABLE
pressed MSAA: STATE_SYSTEM_PRESSED is true when checked.
readonly MSAA:STATE_SYSTEM_READONLY
required MSAA: There is no mapping. User agent must make available through the [DOM] or a specialized API.Note: While optional could be combined with required this is kept to be consistent with CSS3 pseudo classes and [XForms].
selected MSAA:STATE_SYSTEM_SELECTED
unknown MSAA:mixed
value MSAA: should return the value for getValue().