W3C home > Mailing lists > Public > public-html@w3.org > February 2011

Re: The details element

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Sun, 13 Feb 2011 15:45:36 +0000
Message-ID: <AANLkTimJUL79QPYNH354sMGSjqRARQFMf20JMs2xXQuk@mail.gmail.com>
To: Luiz Agostini <luiz@webkit.org>
Cc: public-html@w3.org, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
hi Luiz,

in order for the details/summary to be accessible to people with
disabilities it needs to be hooked up to be able to receive focus, operable
with the keyboard and have role, name and state information exposed via
accessibility APIs

below are some suggestions:

I  would suggest the summary content act as the label for the disclosure
Clicking on the summary with a mouse will open/close the details element.
The summary should be keyboard focusable and when the spacebar is pressed it
will open/close the details element.
as should a tap on a touch screen.

The summary element should be mapped to AXDisclosureTriangle[1] role in the
Mac accessibility API.
the accessible name (AXTitle) for the disclosure triangle is the text
content of the summary element.
when the details element open attribute is present, set  AXValue property to
1 on the summary element.
when the details element open attribute is absent, set  AXValue property to
0 on the summary element.

On windows where there is no disclosure triangle role map it to the

the accessible name (accName) for the button is the text content of the
summary element.
when the details element open attribute is present set  STATE_SYSTEM_EXPANDED
on the summary element.
when the details element open absent is present set  STATE_SYSTEM_COLLAPSED on
the summary element.




On 11 February 2011 19:42, Luiz Agostini <luiz@webkit.org> wrote:

> Hi,
> I am working on <details> and <summary> implementation in WebKit (see
> https://bugs.webkit.org/show_bug.cgi?id=51071<https://bugs.webkit.org/show_bug..cgi?id=51071>). It
> would be nice to receive some feedback from this list.
> Some questions that I have are:
> 1 - Should a click on the <summary> toggle the "open" attribute of the
> corresponding <details> element?
> 2 - In the example image seen in
> http://www.w3.org/TR/html5/interactive-elements.html#the-details-element there
> is a small triangle in the <summary> indicating the current value of the
> "open" attribute of the <details>. Should it be rendered by default? Are
> there attributes or CSS properties that could be used to change it or remove
> it?
> 3 - Should an event be triggered when the <details> element is opened or
> closed?
> In Bugzilla you will find a sample HTML that I am using for testing and a
> screen shot showing that sample HTML rendered by the proposed patch.
> Thank you very much in advance.
> Luiz

Received on Sunday, 13 February 2011 15:47:32 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:09 UTC