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

Re: Change Proposal for Issue 194

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 14 Feb 2012 18:15:24 -0800
Message-Id: <3D0F9651-BDB9-4F0B-B06A-E83BEC406C59@jumis.com>
Cc: David Singer <singer@apple.com>, Janina Sajka <janina@rednote.net>, Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, John Foliot <john@foliot.ca>, "public-html@w3.org" <public-html@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Seconded.

Transcriptions are about capturing the content in text; an gosh could we use that for img too.

I could easily reuse alt, longdesc an transcript on the same image and have three very different blocks.

-Charles

On Feb 14, 2012, at 4:34 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote:

> Well, this is why I wanted the attribute to be called @transcription
> rather than @transcript, because it should contain everything a user
> needs to read in order to get the same "experience" that a user gets
> who watches the film. So to me transcript = captions + descriptions
> (roughly).
> 
> Silvia.
> 
> On Wed, Feb 15, 2012 at 11:24 AM, David Singer <singer@apple.com> wrote:
>> Does seem that a *description* of a video and a *transcript* are quite distinct.
>> 
>> In this video, a transcript might end:
>> 
>> 
>> heedi hoo! heedie hoo!
>> 
>> Do-NUT!
>> 
>> a description might be moreā€¦informative.
>> 
>> 
>> David Singer
>> Multimedia and Software Standards, Apple Inc.
>> 
>> 
> 
Received on Wednesday, 15 February 2012 02:15:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:30 UTC