SelectionItem Pattern events when used on roles gridcell,  option, row, tab

Per the current text events MUST be fired for the following which currently do not have UIA events defined:

aria-disabled
aria-pressed
aria-invalid
aria-readonly
aria-required

Andi to remove bulleted lists and make sure information is either absorbed into the events table or described elsewhere.

At the UAI TF meeting today, we decided to take out the bulleted list above the
table as long as the information is covered either in the table or elsewhere in
the document.

The only things that don't seem to be covered are:

aria-hidden: this will affect the visibility state when the object is in the
accessibility tree
<als> I know this is tied up with the aria-hidden issues but we don't talk
about exposing any states for aria-hidden in the state/property mapping table.
Should we have something more there for cases where the object is in the
accessibility tree? </als>

aria-multiselectable changes: user agents SHOULD cause the destruction and
recreation of a new accessible object for the element, because it is a major
change where the interfaces exposed via accessibility APIs change as well.
<als> aria-multiselectable processing will be covered in the section on
Selection Events. See Bug 13258 </als>

David,

Look up the events that are fired with aria-hidden changes and review the table of events in 5.8.1 to make sure it's correct for the IA2 and ATK columns:

http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_state-change

Record any changes needed in this bug and reassign to Andi.

For changes to aria-hidden, FF currently fires:

On Windows:
IA2_EVENT_OBJECT_ATTRIBUTE_CHANGED

On Linux:
Nothing :(

I need to figure out what's up there.

In any event, I had push-back on firing SHOW/HIDE. My gut reaction is to say the object attribute changed event is important. I'm having trouble finding the event in atk...

Are all of the other IA2 and ATK events correct?

Figure out "notify state change" verbiage.

OK for ATK create verbiage that follows this pattern:

fire "object:state-changed:foo" where foo is the state. For example:

Fire "object:state-changed:checked".