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

Re: code samples for extended description

From: White, Jason J <jjwhite@ets.org>
Date: Wed, 13 Jan 2016 12:45:08 +0000
To: Daniel Weck <daniel.weck@gmail.com>
CC: "Liam R. E. Quin" <liam@w3.org>, "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>, "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, ARIA Working Group <public-aria@w3.org>
Message-ID: <3A30DC12-C459-4836-99D5-E1416C3A296A@ets.org>

> On Jan 13, 2016, at 00:37, Daniel Weck <daniel.weck@gmail.com> wrote:
>
> 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

My understanding of the proposal is that the media query would evaluate to true if the user prefers to be alerted to the availability of extended descriptions and other alternatives available in the content. Thus, the query reflects a preference/configuration setting. All that is needed is CSS that conditionally hides (e.g., display: none) the content unless the media query returns true.


________________________________

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 12:45:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:22 UTC