16503 2012-03-24 03:01:58 +0000 [AAPI]: nested links or interactive content in <summary> 2012-05-01 20:04:16 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified All All NEW a11y P2 normal --- 1 jason cyns hans.hillen mike public-html-admin public-html-wg-issue-tracking sideshowbarker+html-a11y-api oldest_to_newest 66010 0 jason 2012-03-24 03:01:58 +0000 "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? 67223 1 jason 2012-05-01 20:04:16 +0000 Possibly of use: "Screen Readers and details/summary" http://www.accessibleculture.org/articles/2012/03/screen-readers-and-details-summary/