- From: Andi Snow-Weaver <andisnow@us.ibm.com>
- Date: Thu, 28 Apr 2011 10:02:03 -0500
- To: Larry Weiss <lweiss@microsoft.com>
- Cc: Cynthia Shelly <cyns@microsoft.com>, David Bolter <david.bolter@gmail.com>, "jcraig@apple.com" <jcraig@apple.com>, "w3c-wai-pf@w3.org" <w3c-wai-pf@w3.org>, "wai-xtech@w3.org" <wai-xtech@w3.org>
- Message-ID: <OF85322FD2.BA8100B2-ON86257880.00526FFB-86257880.005295E6@us.ibm.com>
In today's UAI TF call, we were talking about this topic.
David said that Firefox fires focus events. I don't recall this being
discussed as an option at our meeting two weeks ago, do you? Seems like
this might be the right thing to do since the AT is actually requesting a
focus change.
Andi
From: Larry Weiss <lweiss@microsoft.com>
To: Andi Snow-Weaver/Austin/IBM@IBMUS
Cc: Cynthia Shelly <cyns@microsoft.com>, David Bolter
<david.bolter@gmail.com>, "jcraig@apple.com"
<jcraig@apple.com>, "w3c-wai-pf@w3.org" <w3c-wai-pf@w3.org>,
"wai-xtech@w3.org" <wai-xtech@w3.org>
Date: 04/28/2011 09:11 AM
Subject: RE: aria-activedescendant changes to the aria-implementation
guide
I agree that an activation event would be the wrong response to an AT
generated focus event. But it is acceptable for those elements where
activate has the same effect as a focus change.
No response for the remaining elements is just as wrong.
Larry.
From: Andi Snow-Weaver
Sent: Thursday, April 28, 2011 6:40 AM
To: Larry Weiss
Cc: Cynthia Shelly; David Bolter; jcraig@apple.com; w3c-wai-pf@w3.org;
wai-xtech@w3.org
Subject: RE: aria-activedescendant changes to the aria-implementation guide
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
Inactive hide details for Larry Weiss ---04/27/2011 12:27:57 PM---As
written, 4.3<http://www.w3.org/WAI/PF/aria-implementation/Larry Weiss
---04/27/2011 12:27:57 PM---As written, 4.3<
http://www.w3.org/WAI/PF/aria-implementation/#keyboard-focus_at> specifies
that some
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
Attachments
- image/gif attachment: graycol.gif
Received on Thursday, 28 April 2011 15:02:50 UTC