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

[Bug 12794] <video> Add a non-normative note on how to provide text alternatives for media elements

From: <bugzilla@jessica.w3.org>
Date: Fri, 13 Jan 2012 04:57:36 +0000
To: public-html-a11y@w3.org
Message-Id: <E1RlZCq-0006oX-7U@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12794

John Foliot <jfoliot@stanford.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |

--- Comment #9 from John Foliot <jfoliot@stanford.edu> 2012-01-13 04:57:34 UTC ---
(In reply to comment #8)
> But that doesn't help in cases where the video is not supposed
> to have other markup about it around it, such as when it's "embedded" in
> another page through an iframe. This is why I suggested moving the extra
> content into the video element as fallback content. If that fallback content
> was available to accessibility APIs, then it would be the nicest way to have
> accessibility content that can be copied around with the video.

The requirement is as Silvia notes: authors require a means of adding both
short and longer textual alternatives to media markup (<video> and <audio>
elements) directly in the markup even when design considerations remove the
ability to provide that text as visible on-screen text. 

Simon's comment (https://www.w3.org/Bugs/Public/show_bug.cgi?id=12794#c1) is
correct in that adding this content as the fall back content will not be a
viable solution, due to the fact that when <video> is supported the fallback
content is not supposed to be exposed to users. The current specification
states:
     "Note: In particular, this content is not intended to address
accessibility concerns. To make video content accessible to the blind, deaf,
and those with other physical or cognitive disabilities, authors are expected
to provide alternative media streams and/or to embed accessibility aids (such
as caption or subtitle tracks, audio description tracks, or sign-language
overlays) into their media streams."
http://www.w3.org/TR/html5/video.html#video

It is possible that aria-label could address the need for the short textual
description of the video asset (but not the @poster asset), however the
requirement for supporting a longer textual description has not been resolved.
Related to Bug 12228 https://www.w3.org/Bugs/Public/show_bug.cgi?id=12228

Once this means is determined, author guidance on how to achieve this is
required as non-normative text in the specification
(http://www.w3.org/TR/html5/video.html#best-practices-for-authors-using-media-elements).


(In reply to comment #7)
> 
> (I don't see why anyone would care what the poster is.)

We have had numerous requests from non-sighted users via numerous email
exchanges discussing this requirement. It is too bad that the Editor still does
not understand this need, but it has previously been well articulated, and the
requirement has not been addressed to date. 
Possibly related to Issue 142 (Status: Formal Objection)
http://www.w3.org/html/wg/tracker/issues/142

-- 
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 04:57:41 GMT

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