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

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

From: Cynthia Shelly <cyns@microsoft.com>
Date: Fri, 13 Nov 2015 19:55:30 +0000
To: "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, "White, Jason J" <jjwhite@ets.org>, Shane McCarron <shane@aptest.com>
CC: Charles LaPierre <charlesl@benetech.org>, "Gunderson, Jon R" <jongund@illinois.edu>, Steve Faulkner <faulkner.steve@gmail.com>, "Chaals McCathie Nevile" <chaals@yandex-team.ru>, Janina Sajka <janina@rednote.net>, W3C WAI Protocols & Formats <public-pfwg@w3.org>, "public-digipub-ig@w3.org" <public-digipub-ig@w3.org>
Message-ID: <SN1PR0301MB1535A629355235692CE834B1C6110@SN1PR0301MB1535.namprd03.prod.outlook.com>
I understand that there are many potential uses. I'm trying to tease out whether these are "Blocking a major project right now" uses or "Would be nice to leverage at some point" uses.  That can help us understand how to stage it and iterate, which is a development strategy more in line with the processes of browser-makers.

Would it, for example, be enough to say "use longdesc for images" for now, gather some data on how well that works, before designing something that covers all the other cases?

-----Original Message-----
From: Siegman, Tzviya - Hoboken [mailto:tsiegman@wiley.com] 
Sent: Friday, November 13, 2015 10:29 AM
To: White, Jason J <jjwhite@ets.org>; Shane McCarron <shane@aptest.com>
Cc: Charles LaPierre <charlesl@benetech.org>; Gunderson, Jon R <jongund@illinois.edu>; Steve Faulkner <faulkner.steve@gmail.com>; Chaals McCathie Nevile <chaals@yandex-team.ru>; Janina Sajka <janina@rednote.net>; W3C WAI Protocols & Formats <public-pfwg@w3.org>; public-digipub-ig@w3.org
Subject: RE: Proposal: remove aria-describedat from the ARIA 1.1 specification

DPUB discusses many uses for non-image content that require descriptions, including video, tables, text that is organized in an image-like pattern (picture a poem by e.e. cummings). Please note that these are not elements that are exclusive to the publishing industry. We just have loud voices and a very demanding audience with a very organized activists in the school systems. 



Tzviya Siegman
Digital Book Standards & Capabilities Lead Wiley
201-748-6884
tsiegman@wiley.com 


-----Original Message-----
From: White, Jason J [mailto:jjwhite@ets.org]
Sent: Friday, November 13, 2015 1:21 PM
To: Shane McCarron
Cc: Charles LaPierre; Gunderson, Jon R; Steve Faulkner; Chaals McCathie Nevile; Janina Sajka; W3C WAI Protocols & Formats; public-digipub-ig@w3.org
Subject: Re: Proposal: remove aria-describedat from the ARIA 1.1 specification


> On Nov 13, 2015, at 11:38, Shane McCarron <shane@aptest.com> wrote:
>
> This is actually a super important point.  In the ARIA call yesterday we were asking if this was only related to images.  If it is not... then I don't know that anything we have been discussing is really general purpose except the summary / details relationship that we are discussing right now.
The Web Components that can be created and used to provide descriptions and other alternatives are very general. They can be applied to tables, images or whatever elements one chooses.

The design that Mark Hakkinen arrived at is similar to that of the AUDIO and VIDEO elements in HTML 5 in that the Web Component provides a “controls” attribute taht determines whether or not it creates its own user interface. That UI can be styled so that it’s visually distinctive and made accessible to screen reader users.



________________________________

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 Friday, 13 November 2015 19:56:01 UTC

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