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

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

From: Daniel Weck <daniel.weck@gmail.com>
Date: Tue, 10 Nov 2015 18:28:58 +0000
Message-ID: <CA+FkZ9EpOHX85zNLMT70RL0OuZuADnxgDmA_TBarXZ1bYgGitA@mail.gmail.com>
To: "White, Jason J" <jjwhite@ets.org>
Cc: 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>
Jason:
> I’ve also raised concerns about the possible use of links to external descriptions in EPUB, as it limits the offline use of books, thus placing readers with disabilities at a disadvantage with respect to their peers. An EPUB book should be a self-contained package that can be copied onto a device and read without requiring access to external resources in order to be accessible to the user.

Just to clarify: I am certainly not suggesting that long/extended
descriptions should be located outside of an EPUB publication. The
vision (as demonstrated by our prototype implementations, DAISY
production tool + Readium reading system) is that the description HTML
files are external to the primary reading flow (ancillary to the main
HTML spine item), but that they are indeed very much part of the
e-book container (and listed as internal resources in the package
manifest). As the original publication needs to be altered in order to
incorporate references to long/extended descriptions, it makes sense
to also bundle the new resources.

Conversely, an alternative model is offered by annotations, whereby
descriptions "link into" untouched original publications, resulting in
separate physical entities.

/Daniel

/Daniel


On Tue, Nov 10, 2015 at 5:07 PM, White, Jason J <jjwhite@ets.org> wrote:
>
>> On Nov 10, 2015, at 11:45, Daniel Weck <daniel.weck@gmail.com> wrote:
>>
>> Hello Janina (et. al)
>> Somewhere in this discussion (<wink>), I raised some concerns about
>> the use of iframes (inline markup) to embed external (possibly-long)
>> descriptions. The use of various mailing lists / target audiences
>> seems to cause confusion here (dpub-ig, dpub-aria, aria, etc.), so
>> please allow me to link directly to the two most relevant messages:
>
> One could use figure/figcaption elements, where figcaption contains a link to an external description. The link (anchor element) could be hidden from users who don’t explicitly request extended descriptions using the media query taht several contributors to this discussion have proposed.
>
> This is a good illustration of the fact that no single solution meets all requirements or should be considered appropriate for all use cases.
>
> I’ve raised privacy concerns about linking to external descriptions. In addition, there are circumstances in which network access is restricted or unavailable (testing scenarios are often good examples here, due to security considerations). Ideally, everything, including descriptions, needs to be loaded at once in such cases. I’ve also raised concerns about the possible use of links to external descriptions in EPUB, as it limits the offline use of books, thus placing readers with disabilities at a disadvantage with respect to their peers. An EPUB book should be a self-contained package that can be copied onto a device and read without requiring access to external resources in order to be accessible to the user. In essence, I am not in agreement with the requirements articulated by the digital publishing community in connection with extended descriptions, although I think those requirements can be met without significant changes to Web technology.
>
>
> ________________________________
>
> 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:29:49 UTC

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