[Bug 25140] restrict summary element content?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25140

--- Comment #3 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to Simon Pieters from comment #2)
> (In reply to steve faulkner from comment #0)
> > Are there any use cases for allowing interactive descendants?
> 
> https://discussions.apple.com/servlet/JiveServlet/showImage/2-23821765-
> 332751/Screen+Shot+2013-11-17+at+1.40.08+PM.png
> http://www.crsp.com/files/images/scan_options.jpg
> http://i.msdn.microsoft.com/dynimg/IC115703.png
> http://www.lennonbus.org/images/blog/post_images/Screen_shot_2010-05-27_at_1.
> 59_.42_PM_.png
> http://www.oreillynet.com/digitalmedia/blog/images/bwaperture.jpg

thanks, its difficult to tell from the screenshots alone whether the usage
represent reasonable use cases or not. One thing I noted was in the example
http://i.msdn.microsoft.com/dynimg/IC115703.png there is a focus rectangle
around the auto updating 'summary'. I had a look at the interface in 8.1 and
found that the whole 'summary' is clickable and exposed as a button in acc
APIs.

Currently I think the control aspect of details/summary is underspecified as
there is no method to provide an accessible name (LABEL)for the 'anonymous
control' that allows operation of the widget. whereas the accessibility
implementation example provided in the HTML acc API spec [1] does provide 
clear advice.

Also from an accessibility/usability perspective having the summary element as
the actionable control provides a large activation area, as does the current
(seemingly) broken implementations. 

thus the suggestion in this bug to restrict the content allowed in summary.

Do you see a way the specification of the summary/details element can be
improved to both allow nested controls and provide a clear method to associate
a visible label, with a large enough click area to accommodate
accessibility/usability requriements?


[1]
http://rawgithub.com/w3c/html-api-map/master/index.html#accessible-feature-implementation-examples

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 28 March 2014 09:38:50 UTC