Re: aria-activedescendant changes to the aria-implementation guide

Hi Joseph,

Thanks for your comments.

>> ... because WAI-ARIA 1.0 does not provide a mechanism to notify an
>> application that the DOM has changed.

> This wording it makes it sound like WAI-ARIA 1.0 is at fault.  It
> isn't.  The reality is that there is no mechanism to notify a webapp
> that the DOM has changed.  That deficiency is not specific to ARIA.

I changed this to your suggested wording "because there is no reliable
mechanism...."

I'll talk to the UAI TF today about coming up with a definition for
"activation event".

I added checkbox to the SHOULD NOT list.

And to your last comment

> there are two kinds of button -- push buttons and toggle
> buttons.  Toggle buttons have role='button' *and*
> aria-pressed='true/false'.  The section currently says that user agents
> should not fire an activation event for buttons, but the reader might
> think that's for push buttons only.  It might be useful to mention that
> the same holds for toggle buttons.  (I assume it does because toggle
> buttons are similar to checkboxes and radio buttons, and radio buttons
> are listed in the SHOULD NOT section).

I don't think the clarification is necessary. The spec says "elements with
the role button...". Since toggle buttons do have role="button", this seems
very clear to me that the rule applies to toggle buttons.

Andi