W3C home > Mailing lists > Public > public-digipub-ig@w3.org > November 2015

Re: Proposal: remove aria-describedat from the ARIA 1.1 specification

From: White, Jason J <jjwhite@ets.org>
Date: Tue, 10 Nov 2015 18:10:21 +0000
To: Ivan Herman <ivan@w3.org>
CC: Daniel Weck <daniel.weck@gmail.com>, Janina Sajka <janina@rednote.net>, Richard Schwerdtfeger <schwer@us.ibm.com>, Avneesh Singh <avneesh.sg@gmail.com>, Charles LaPierre <charlesl@benetech.org>, Juan Corona <juanc@evidentpoint.com>, George Kerscher <kerscher@montana.com>, "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>, "PF (public-pfwg@w3.org)" <public-pfwg@w3.org>, Ric Wright <rkwright@geofx.com>, "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, Zheng Xu <zxu@kobo.com>
Message-ID: <EB6FA8C7-4268-4C6B-8650-A97C30FEC25D@ets.org>

> On Nov 10, 2015, at 12:33, Ivan Herman <ivan@w3.org> wrote:
>
> Just a minor remark: I think your remark on EPUB is not justified. The term 'external' is, in this sense, misleading: it is perfectly possible to include the target of a desribed-at (or longdesc) in the EPUB and make the book self contained for offline reading.

Yes, it’s possible to do this, but it isn’t the scenario that I’ve heard emphasized in digital publishing discussions, which have tended to focus on retrieval of descriptions (possibly provided by third parties) over a network.

Placing descriptions in separate files within packaged publications would yield a slight performance improvement in the processing of the document, and conserve a modest amount of memory. If the descriptions are included by default in the package together with the primary content, then the privacy concerns don’t apply, unless the reading system is hosted on a server that the user has reason not to trust with information about what her or his needs are.

In any case, I think all that the W3C needs to do is to supply (1) the media query that reflects the user’s “extended description” requirement, and (2) possibly an ARIA role for designating descriptions. Existing HTML elements, including details/summary, figure/figcaption, and other solutions identified in the work of this group can address all of the various use cases of which I am aware. I also support Rich in encouraging implementation of details/summary.


________________________________

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 Tuesday, 10 November 2015 18:10:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 25 April 2017 10:44:35 UTC