But Larry,
If you fire an activation event, it will activate that menuitem when all
the user really wanted to do is move focus to it. That seems more dangerous
than having no effect.
Andi
From: Larry Weiss <lweiss@microsoft.com>
To: Andi Snow-Weaver/Austin/IBM@IBMUS, Cynthia Shelly
<cyns@microsoft.com>, David Bolter <david.bolter@gmail.com>,
"jcraig@apple.com" <jcraig@apple.com>
Cc: "wai-xtech@w3.org" <wai-xtech@w3.org>, "w3c-wai-pf@w3.org"
<w3c-wai-pf@w3.org>
Date: 04/27/2011 12:27 PM
Subject: RE: aria-activedescendant changes to the aria-implementation
guide
As written, 4.3 specifies that some AT focus events, like focus on a
menuitem, SHOULD NOT have an effect.
To me, this SHOULD NOT be acceptable.
Note: The inability to set Platform focus to an element with the FOCUSABLE
state indicates a Platform accessibility implementation error.
From: Andi Snow-Weaver [mailto:andisnow@us.ibm.com]
Sent: Wednesday, April 27, 2011 8:04 AM
To: Cynthia Shelly; David Bolter; jcraig@apple.com; Larry Weiss
Cc: wai-xtech@w3.org; w3c-wai-pf@w3.org
Subject: Re: aria-activedescendant changes to the aria-implementation guide
Per Monday's ARIA TF call [1], I have removed bullet 5 from section 4.2 and
modified section 4.3 as discussed. Please review section 4.3 [2] and let me
know if I missed anything.
[1] http://www.w3.org/2011/04/25-pf-minutes.html#item01
[2] http://www.w3.org/WAI/PF/aria-implementation/#keyboard-focus_at
Andi
