implementation of details/summary appears suboptimal

The details/summary elements is now implemented in webkit/chrome, there is
keyboard support in webkit but not in chrome as yet.


In webkit the summary element is the interactive component and can be
operated using the keyboard by activating the enter or spacebar keys.

Currently the summary element can have interactive element as children.
This creates a situation akin to:

<button> press 1 <a href="#poot"> press 2</a></button>

as the summary element will likely be mapped to the button role in
accessibility APIs that do not have a disclosure role [1]

This seems suboptimal and is not conforming as per the example, but is
conforming for summary

<details>
<summary>press 1 <a href="#poot"> press 2</a></summary>
</details>.

It is suggested that the allowed children of the summary element be
modified to disallow the inclusion of interactive elements.

[1] http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html#el-130
-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html