W3C home > Mailing lists > Public > public-html@w3.org > March 2012

implementation of details/summary appears suboptimal

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 12 Mar 2012 11:06:00 +0000
Message-ID: <CA+ri+VkkV_4v4y3Vk979C=x1SL-=tJLq-Msz-BSUExFN0WopMw@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
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

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

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 |
HTML5: Techniques for providing useful text alternatives -
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Monday, 12 March 2012 11:06:56 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:50 UTC