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

[Bug 5758] insufficient accessibility fallback for <audio> or <video>

From: <bugzilla@wiggum.w3.org>
Date: Sun, 07 Feb 2010 01:36:16 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Ndw4O-0004gn-MH@wiggum.w3.org>

--- Comment #14 from Silvia Pfeiffer <silviapfeiffer1@gmail.com>  2010-02-07 01:36:15 ---
The discussions on this bug have touched multiple topics related to media and

I'd like to propose this bug to focus on the support of synchronised
accessibility data (captions, subtitles, audio description, sign language) -
both embedded in stream and external.

In particular, this bug is not about "fallbacks" (and possibly the word
"fallback" should be replaced with "support" in the title).

As for all the other topics that this bug has touched upon, here is what I took
* choice of a baseline code - not something we can make any progress on through
a bug
* video fallback in UAs where video is not supported - already possible
* non-synchronised text alternatives - already possible through putting text or
a link next to the video (and possibly using aria-describedBy to link it to the
* access to captions/subtitles available in media files that a UA does not
support (e.g. MPEG with subtitles in Firefox) - is simply not technically
* @alt attribute - has been discussed in WHATWG, see thread at
basically, the following attributes already provide what is required: @title,
@aria-label, @aria-describedby

Hope this answers some questions and lets us move to the core accessibility
issues for media elements that are still open and that Ian proposed a process
for how to address.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 7 February 2010 01:36:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:10 UTC