See also: IRC log
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.
Also, using NVDA and using arrow keys, focus gets set on link.
So nested link fires when parent element gets focus. NVDA has suggested submitting a bug report, although fixing this could break something else.
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).
Jason is going to file the same bug with JAWS, which doesn't have issue with firing nested link in FF (although it does happen with IE).
No problems when not using a screen reader.
This 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 we can't use just a regular space.)
Jason's test page is http://www.accessibleculture.org/misc-tests/link-inside-onclick2.html
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).
Jason contacted Marco from Mozilla, who is quite happy to participate.
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.
<scribe> ACTION: Jason will file bug reports with NVDA and JAWS. [recorded in http://www.w3.org/2012/03/06-aapi-minutes.html#action01]
<scribe> ACTION: Jason will go ahead and add non-breaking spaces to table at beginning of each element. [recorded in http://www.w3.org/2012/03/06-aapi-minutes.html#action02]