- From: Bryan Garaventa <bryan.garaventa@whatsock.com>
- Date: Wed, 8 Jan 2014 11:11:15 -0800
- To: <wai-xtech@w3.org>
Hi, I understand this will be discussed later this month when we're at the ftf meeting, but I just wished to throw this out there in advance. Also, I may not have been clear yesterday about the use case I was thinking of during the call. I can see the attraction of making a role, such as role=button on a Div or Span, cause the browser to activate the click event when activated from the keyboard in the same manner as a Button element. At the same time, for years, the passive aspect of ARIA has caused countless implementations and libraries to implement both a key event and a click handler to ensure accessibility for both keyboard and sighted mouse users with cross browser and cross AT compatibility when applying interactivity to natively static elements. So if the addition of role=button suddenly caused the click event on a Div or Span to be fired as well when activated from the keyboard, presumably it would fire both the key event and the click, which would cause a conflict for redundant event handlers. For example, for ARIA Toggles, the firing of one would cancel out the other, since the key event would toggle on and at the same time the firing of the click would instantly toggle off, breaking all such implementations that currently exist everywhere. If ARIA were made active instead of passive, Presumably the same considerations would have to be made for all other interactive roles as well, such as menuitem, option, radio, checkbox, tab, etc? Just some food for thought prior to the meeting. ----- Original Message ----- From: "Joseph Scheuhammer" <clown@alum.mit.edu> To: <wai-xtech@w3.org> Sent: Wednesday, January 08, 2014 8:06 AM Subject: Minutes: [aapi] UAI TF Meeting Tue Jan 7 2013 > Link: http://www.w3.org/2014/01/07-aapi-minutes.html > > Plain text version follows: > > [1]W3C > > [1] http://www.w3.org/ > > Protocols and Formats Working Group Teleconference > 07 Jan 2014 > > [2]Agenda > > [2] http://lists.w3.org/Archives/Public/wai-xtech/2014Jan/0002.html > > See also: [3]IRC log > > [3] http://www.w3.org/2014/01/07-aapi-irc > > Attendees > > Present > Joseph_Scheuhammer, David_Bolter, Bryan_Garaventa, cyns, > Cynthia_Shelly, Michael_Cooper > > Regrets > Chair > Joseph_Scheuhammer > > Scribe > MichaelC > > Contents > > * [4]Topics > 1. [5]UAIG 1.1 issues/actions (all): > https://www.w3.org/WAI/PF/Group/track/products/23 > 2. [6]action-847 > * [7]Summary of Action Items > __________________________________________________________ > > UAIG 1.1 issues/actions (all): > [8]https://www.w3.org/WAI/PF/Group/track/products/23 > > [8] https://www.w3.org/WAI/PF/Group/track/products/23 > > <clown> [9]https://www.w3.org/WAI/PF/Group/track/products/23 > > [9] https://www.w3.org/WAI/PF/Group/track/products/23 > > action-847 > > <clown> action-847? > > <trackbot> action-847 -- Michael Cooper to Create script to > hide columns at user choice in UAIG tables to yield less wide > tables -- due 2011-06-21 -- OPEN > > <trackbot> > [10]https://www.w3.org/WAI/PF/Group/track/actions/847 > > [10] https://www.w3.org/WAI/PF/Group/track/actions/847 > > <clown> > [11]http://rawgithub.com/w3c/html-api-map/master/index.html > > [11] http://rawgithub.com/w3c/html-api-map/master/index.html > > Or this, in W3C space: [12]http://www.w3.org/TR/html-aapi/ > > [12] http://www.w3.org/TR/html-aapi/ > > <clown> > [13]http://rawgithub.com/w3c/html-api-map/master/index.html#htm > l-element-to-accessibility-api-role-mapping-matrix > > [13] > http://rawgithub.com/w3c/html-api-map/master/index.html#html-element-to-accessibility-api-role-mapping-matrix > > Steal code from above, but do in 1.1 > > <clown> action-1102? > > <trackbot> action-1102 -- David Bolter to [ARIA 1.1] Get > someone to look at the SHOULD statements in the Role Mapping > table. Can these be changed from "SHOULD be exposed" to "expose > as" -- due 2012-07-25 -- OPEN > > <trackbot> > [14]https://www.w3.org/WAI/PF/Group/track/actions/1102 > > [14] https://www.w3.org/WAI/PF/Group/track/actions/1102 > > <clown> > [15]http://www.w3.org/TR/wai-aria-implementation/#mapping_role_ > table > > [15] http://www.w3.org/TR/wai-aria-implementation/#mapping_role_table > > <clown> Do in 1.1 > > <trackbot> action-1104 -- Cynthia Shelly to Define what the > accessibility API mapping is for UIA on aria-describedby in > section 5.5.1 table when the element does not exist in the > accessibility tree such as when css: display:none applies -- > due 2013-09-17 -- OPEN > > <trackbot> > [16]https://www.w3.org/WAI/PF/Group/track/actions/1104 > > [16] https://www.w3.org/WAI/PF/Group/track/actions/1104 > > <clown> Cyns will look > > <trackbot> action-1263 -- Joseph Scheuhammer to AXARIABusy is > probably going to change to something less ARIA-specific, like > AXBusy or AXElementBusy -- due 2013-12-02 -- OPEN > > <trackbot> > [17]https://www.w3.org/WAI/PF/Group/track/actions/1263 > > [17] https://www.w3.org/WAI/PF/Group/track/actions/1263 > > depends on outcome of forking discussion > > will wait for after FtF > > <clown> action-1284? > > <trackbot> action-1284 -- Cynthia Shelly to Start the > conversation re keeping issue-616 feature in the spec on list, > realizing it may go lc at risk. we need to determine what to do > by next tuesday. -- due 2013-10-29 -- OPEN > > <trackbot> > [18]https://www.w3.org/WAI/PF/Group/track/actions/1284 > > [18] https://www.w3.org/WAI/PF/Group/track/actions/1284 > > <clown> issue-616? > > <trackbot> issue-616 -- ISSUE: Review potentially at-risk > statement "When the user triggers an element with a defined > activation behavior in a manner other than clicking it, such as > by pressing Enter, simulate a click on the element." -- closed > > <trackbot> [19]https://www.w3.org/WAI/PF/Group/track/issues/616 > > [19] https://www.w3.org/WAI/PF/Group/track/issues/616 > > <clown> [20]http://www.w3.org/TR/wai-aria-implementation > > [20] http://www.w3.org/TR/wai-aria-implementation > > <clown> > [21]http://www.w3.org/TR/wai-aria-implementation/#sotd_atrisk > > [21] http://www.w3.org/TR/wai-aria-implementation/#sotd_atrisk > > relates to items at risk in current cr > > question of taking those up again in 1.1 > > make sure we remember to > > timeframe for 1.1: [22]http://www.w3.org/WAI/PF/project/ > > [22] http://www.w3.org/WAI/PF/project/ > > close action-1284 > > <trackbot> Closed action-1284. > > when we activate the risk conditions, weŽll create actions to > revive the features in the 1.1 version > > <clown> > [23]https://dvcs.w3.org/hg/pfwg/raw-file/default/ARIA-UAIG/1.0/ > tests/test-files/test31.html > > [23] > https://dvcs.w3.org/hg/pfwg/raw-file/default/ARIA-UAIG/1.0/tests/test-files/test31.html > > <clown> > [24]http://www.w3.org/TR/wai-aria-implementation/#mapping_event > s_menus > > [24] > http://www.w3.org/TR/wai-aria-implementation/#mapping_events_menus > > text alternative computation item may not meet the risk > condition > > so we can remove the at risk ednote > > <clown> > [25]http://www.w3.org/TR/wai-aria-implementation/#mapping_event > s_menus > > [25] > http://www.w3.org/TR/wai-aria-implementation/#mapping_events_menus > > menus weŽll change to non normative if risk met > > but make normative again in 1.1 > > Summary of Action Items > > [End of minutes] > __________________________________________________________ > > > Minutes formatted by David Booth's [26]scribe.perl version > 1.138 ([27]CVS log) > $Date: 2014-01-08 15:51:22 $ > __________________________________________________________ > > [26] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm > [27] http://dev.w3.org/cvsweb/2002/scribe/ > > > -- > ;;;;joseph. > > > 'A: After all, it isn't rocket science.' > 'K: Right. It's merely computer science.' > - J. D. Klaun - > >
Received on Wednesday, 8 January 2014 19:11:35 UTC