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

Yep, and I'm suggesting no "activation" event ever, for focus changes.

Cheers,
David

On Thu, Apr 28, 2011 at 2:48 PM, Joseph Scheuhammer <clown@alum.mit.edu>wrote:

> David,
>
> > If a user tries to programmatically set focus to a checkbox they don't
> > want to actually check/uncheck it do they?  (Not sure if you were
> > implying that)
>
> No, they don't want to check /uncheck simply by focussing.  To be clear,
> I wasn't implying that.  I was wondering if one could leverage what the
> spec suggests in this particular context (the aria-activedescendant issue).
>
> BTW, since checking/unchecking is undesirable in this case, I think that
> is what is behind the restriction in the UAIG text, where it talks about
> focus and aria-activedescendant (my emphasis) [1]:
> > User agents SHOULD NOT fire an activation event on elements with the
> > role button, *checkbox*, ...
>
> [1] http://www.w3.org/WAI/PF/aria-implementation/#keyboard-focus_at
>
> --
> ;;;;joseph
>
> 'I had some dreams, they were clowns in my coffee. Clowns in my coffee.'
>                     - C. Simon (misheard lyric) -
>
>