- From: <bugzilla@jessica.w3.org>
- Date: Fri, 13 Jan 2012 05:24:09 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12964
John Foliot <jfoliot@stanford.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |TrackerRequest
--- Comment #7 from John Foliot <jfoliot@stanford.edu> 2012-01-13 05:24:09 UTC ---
(In reply to comment #5)
>
> Status: Did Not Understand Request
Add a @transcript attribute to the <video> and <audio> elements with a URL as
the value.
> Rationale: We need implementation experience before we can add this to the
> spec. Without it, I see no reason why this would not suffer the same fate as
> similar solutions before it (like longdesc, summary, cite, etc).
The Editor's bias against specific accessibility accommodations such as
@longdesc and @summary is not a reason to fail to address this requirement.
We have evidence that video producers will be creating and subsequently
providing transcripts (essentially non-time-stamped captions or subtitles) and
so accurate content will be produced at the time of content creation. Best
Practices and possibly legislation(s) will require content authors to provide
these transcripts to end-users, and a means to directly and programmaticly link
the transcript to the video element (without the absolute requirement for
on-screen text) is well founded.
On 2012-01-06 Anne van Kesteren stated "A standard sets a goal."
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13531#c8, and so the need for
implementation experience should not be a reason to reject this
user-requirement.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 13 January 2012 05:28:15 UTC