19:48:36 <RRSAgent> RRSAgent has joined #aapi
19:48:36 <RRSAgent> logging to http://www.w3.org/2012/03/06-aapi-irc
19:48:42 <Zakim> Zakim has joined #aapi
19:48:51 <Char> zakim, this will be AAPI
19:48:51 <Zakim> ok, Char; I see WAI_PFWG(AAPI)3:00PM scheduled to start in 12 minutes
19:48:59 <Char> rrsagent, make logs public
19:49:07 <Char> Scribe: Char
19:49:14 <Char> Meeting: AAPI
19:49:20 <Char> Chair: Cynthia Shelly
19:54:50 <Zakim> WAI_PFWG(AAPI)3:00PM has now started
19:54:56 <Zakim> + +1.781.598.aaaa
19:55:31 <Char> zakim, aaaa is Char
19:55:31 <Zakim> +Char; got it
19:57:54 <Zakim> +??P7
19:58:24 <Char> zakim, ??p7 is Jason
19:58:24 <Zakim> +Jason; got it
20:01:15 <Zakim> +[Mozilla]
20:01:26 <davidb> Zakim, Mozilla has David_Bolter
20:01:27 <Zakim> +David_Bolter; got it
20:07:26 <Char> Topic: Current behaviour of NVDA and JAWS with links as first descendent node of a push button, and using aria-pressed in addition to role=button on <summary> to signify a toggle button instead of push button
20:08:45 <Char> Jason is concerned with behavior of NVDA and JAWS, especially in detail and summary view of updated tables. We have event-handlers on the Summary element. Where a link is the first node (which is typical), when you use TAB to set focus, it expands and fires the link at the same time.
20:09:12 <Char> Also, using NVDA and using arrow keys, focus gets set on link.
20:10:04 <Char> So nested link fires when parent element gets focus. NVDA has suggested submitting a bug report, although fixing this could break something else.
20:11:31 <Char> Access to internal link is restricted in certain circumstances. Toggle button solves one problem and creates another. MSAA doesn't provide a role for toggle button (not sure about other APIs).
20:12:16 <Char> Jason is going to file same bug with JAWS, which doesn't have issue with firing nested link in FF (although it does happen with IE).
20:13:26 <Char> No problems when not using a screen reader.
20:14:40 <Char> Has to do with how focus is set in screen readers because links are fired at the same time if links are first items in the element. If we put in a non-breaking space before the link, the link doesn't trigger. (But can't use just a regular space.)
20:15:03 <jkiss> http://www.accessibleculture.org/misc-tests/link-inside-onclick2.html
20:15:11 <Char> Jason can set it up so that all elements start with a non-breaking space, which works around this issue (although it doesn't solve the actual problem).
20:15:27 <Char> Jason's link is for the test page he's been using.
20:21:46 <Char> Jason contacted Marco from Mozilla, who is quite happy to participate.
20:27:53 <Char> Jason will go ahead and add non-breaking spaces to table; could be that using arrows to navigate will cause another issue ("address button" or "heading button"), but he'll follow up on this.
20:28:08 <Char> Action: Jason will file bug reports with NVDA and JAWS.
20:28:32 <Char> Action: Jason will go ahead and add non-breaking spaces to table at beginning of each element.
20:30:06 <Zakim> -[Mozilla]
20:30:08 <Zakim> WAI_PFWG(AAPI)3:00PM has ended
20:30:09 <Zakim> Attendees were +1.781.598.aaaa, Char, Jason, David_Bolter
20:30:23 <Char> rrsagent, draft minutes
20:30:23 <RRSAgent> I have made the request to generate http://www.w3.org/2012/03/06-aapi-minutes.html Char
22:16:13 <Zakim> Zakim has left #aapi
23:31:08 <davidb> davidb has joined #aapi