W3C home > Mailing lists > Public > public-html-a11y@w3.org > April 2012

Re: video and long text descriptions / transcripts

From: David Singer <singer@apple.com>
Date: Fri, 06 Apr 2012 10:24:44 -0700
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <6E0F5975-0469-4247-B627-BD597DBE96B7@apple.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Silvia

I think we have a fundamental difference of approach here.

My observation: we have a number of places where all users (and their UAs) would benefit from knowing of a relationship between two elements, notably a media element and non-timed alternatives.  So my taste is to find a simple, general, mechanism that can express that, and then we just need to (incrementally) decide on the set of relationships we need to express.  My current feeling is that we need "transcript" and "long description", as they are distinct.  Maybe, down the road, the web will getg flooded with opera aficionados and we'll need "plot summary" as well, for example. I think this leads to a flexible, layered, design, and permits expression of nuance (that a long description and a transcript are different, for example).

Your taste, as I understand it, is to be much more specific, but unless the specific solution is actually more simple than the general one (and in this case, I don't see that) I am not sure I see what other advantages there are...


> 
> Who for? Who would make use of this information? Which one would the
> screen reader use?
> 

Whichever it, or the user, likes.  Go ahead, be inventive.  With luck, the regular UAs will expose the link(s) well enough that the need for specialist accessibility UAs would decrease.


David Singer
Multimedia and Software Standards, Apple Inc.
Received on Friday, 6 April 2012 17:25:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:58 GMT