This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"summary" Need to provide advice on what should happen with interactive content, e.g., links, nested in <summary> with role="button". Should nested links, for example, be passed to the a11y API as accessible objects (as IE9 and FF11 do), or should they be flattened to text and unavailable in the tree (as Safari does)? Nested interactive content is permitted as per the spec for <summary>, but is contrary to what is expected in a typical <button>. What effect should role="button" have in this case?
Possibly of use: "Screen Readers and details/summary" http://www.accessibleculture.org/articles/2012/03/screen-readers-and-details-summary/