- From: White, Jason J <jjwhite@ets.org>
- Date: Fri, 13 Nov 2015 18:21:04 +0000
- To: 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>
> 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 18:21:36 UTC