W3C home > Mailing lists > Public > public-aria@w3.org > January 2016

RE: code samples for extended description

From: Siegman, Tzviya - Hoboken <tsiegman@wiley.com>
Date: Wed, 13 Jan 2016 13:55:53 +0000
To: Daniel Weck <daniel.weck@gmail.com>, Jason White <jjwhite@ets.org>
CC: "Liam R. E. Quin" <liam@w3.org>, "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>, ARIA Working Group <public-aria@w3.org>
Message-ID: <25eea00fb40745c888a840cb897ddd2a@AUS-WNMBP-004.wiley.com>
Further to Daniel’s questions, we have talked about a theoretical media query and user settings to show/hide extended descriptions, but we have not actually talked about whether this is an attribute of ARIA, HTML, or CSS. Is this something the user can toggle? Is this built into the browser chrome?

Whether the additional text would annoy or disrupt people, of course, depends on context. But, if the text gets in designers’ way (or is perceived to), no one will use this solution, so I don’t think it’s a good starting point.


Tzviya Siegman
Digital Book Standards & Capabilities Lead

From: Daniel Weck [mailto:daniel.weck@gmail.com]
Sent: Wednesday, January 13, 2016 12:38 AM
To: Jason White
Cc: Liam R. E. Quin; DPUB mailing list (public-digipub-ig@w3.org); Siegman, Tzviya - Hoboken; ARIA Working Group
Subject: Re: code samples for extended description

Hello Jason, in the suggested usage of a Media Query, would a CSS selector be used to match all available extended descriptions in the document? If so, then it would make sense to enable content discovery via a well-defined "type" or "role" for the details element (see my previous comment regarding text in the summary element). Daniel
On 13 Jan 2016 2:17 a.m., "White, Jason J" <jjwhite@ets.org<mailto:jjwhite@ets.org>> wrote:

> On Jan 12, 2016, at 18:35, Liam R. E. Quin <liam@w3.org<mailto:liam@w3.org>> wrote:
> On Tue, 2016-01-12 at 21:16 +0000, White, Jason J wrote:
>>> On Jan 12, 2016, at 14:57, Siegman, Tzviya - Hoboken <tsiegman@wile
>>> y.com<http://y.com>> wrote:
>>> One of the issues that we have not fully resolved is that,
>>> especially when using <details> and <summary>, there is nothing to
>>> indicate to users that the content is a description.
> [...]
>> This can be solved today by providing suitable text in the SUMMARY
>> element, as your examples demonstrate. I wouldn’t be opposed to a new
>> ArIA property, but I suspect the need for it is overestimated.
> I worry first that it's hard enough to get people to add image
> descriptions; do you think people would actually put appropriate text?

Yes, I think the people who make the effort to use the ALT attribute, then to include a detailed description, are exactly the authors who are most likely to place appropriate text in the SUMMARY element.

> In addition, how will people who see the images feel about the text?

This depends on whether the media query becomes available, as has been proposed, for authors to hide the SUMMARY/DETAILS elements from people who do not elect to view extended descriptions.

Finding out to what extent people are in fact annoyed by such additional text would be worthy of an empirical investigation.


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Wednesday, 13 January 2016 13:56:52 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:18 UTC