W3C home > Mailing lists > Public > wai-xtech@w3.org > November 2011

Re: Bug 14320 as discussed in Re: [aapi] UAI TF Meeting Minutes, November 8, 2011

From: david bolter <david.bolter@gmail.com>
Date: Mon, 14 Nov 2011 15:02:03 -0500
Message-ID: <CAEO7jQAn4D3pEDk48Jhng6SyEGZTSjP3ppHXHjnN7b+swF3QNw@mail.gmail.com>
To: Joseph Scheuhammer <clown@alum.mit.edu>
Cc: Cynthia Shelly <cyns@microsoft.com>, Andi Snow-Weaver <andisnow@us.ibm.com>, David Bolter <dbolter@mozilla.com>, Larry Weiss <lweiss@microsoft.com>, Matthew King <mattking@us.ibm.com>, Stefan Schnabel <stefan.schnabel@sap.com>, "Surkov, Alexander" <surkov.alexander@gmail.com>, "wai-xtech@w3.org" <wai-xtech@w3.org>
Hi Joseph,

I was talking about the browser firing a desktop accessibility event. E.g.


On Mon, Nov 14, 2011 at 9:54 AM, Joseph Scheuhammer <clown@alum.mit.edu>wrote:

> Hi David,
> Regarding your explanation of why aria-activedescendant exitss, there is
> one thing that I need further explanation for.
> At a certain point, some ancestor element has DOM focus, (=
> document.activeElement), but one of its children appears visually focussed.
>  You wrote (my emphasis):
>  For screen readers the browser accessibility engine can use the semantics
>> of aria-activedescedant to indicate what appears focused (*by firing a
>> focus event for the active child*).
> What kind of focus event is fired for the active child?  Is it a DOM focus
> event?  A desktop focus event?  An a11y API focus event?  Or some
> combination of the above?
> Also, what is firing this event?  Is it the browser?
> Thanks.
> --
> ;;;;joseph
> 'I had some dreams, they were clowns in my coffee. Clowns in my coffee.'
>                     - C. Simon (misheard lyric) -
Received on Monday, 14 November 2011 20:02:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:44 UTC