This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16503 - [AAPI]: nested links or interactive content in <summary>
Summary: [AAPI]: nested links or interactive content in <summary>
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Cynthia Shelly
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2012-03-24 03:01 UTC by Jason Kiss
Modified: 2012-05-01 20:04 UTC (History)
4 users (show)

See Also:

Attachments

Description Jason Kiss 2012-03-24 03:01:58 UTC 
"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?
Comment 1 Jason Kiss 2012-05-01 20:04:16 UTC 
Possibly of use: "Screen Readers and details/summary" http://www.accessibleculture.org/articles/2012/03/screen-readers-and-details-summary/