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

Re: [media] progress on video transcript discussion

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 7 Jun 2012 23:55:11 +1000
Message-ID: <CAHp8n2=pTN8wQX8ddH3vfEiOuWL7drd5n6edO1i5=f2RMSkPAA@mail.gmail.com>
To: John Foliot <john@foliot.ca>
Cc: David MacDonald <david100@sympatico.ca>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Thu, Jun 7, 2012 at 7:37 AM, John Foliot <john@foliot.ca> wrote:
> David MacDonald wrote:
>> Good discussion....
>> Sylvia's suggested code snip for the use case of embedded video:
>> <video src="video.mpg" aria-label="video with transcript below"
>> transcript="@this_page#transcript"></video>
>> I think this would confuse a blind user... double message..."transcript
>> below", and transcript linked from video element... but there is no
>> transcript below... just the linked transcript from within the video
>> element
>> ... maybe the linked version should drop the aria label, or change to
>> say
>> "video available" or something...
> My larger issue is focused on reaching for ARIA every time an accessibility
> question comes up. I am a huge fan of ARIA, and rejoice in how much support
> we increasingly see from AT tools for ARIA. I am thrilled to see it being
> used more and more every day in mainstream development, but we must all
> remember that it is designed for (and currently only works with) AT tools,
> which only cover a small percentage of people with disabilities.

I am proposing ARIA as a solution where only people with disabilities
need it. Where everyone needs a solution (and there is indeed such a
use case), I have proposed a different attribute - you might want to
re-read my proposal (sorry it got so long, but reasons need to be

Web developers in search of a solution for users with disabilities
will turn to ARIA now - that's an achievement to celebrate and a
trodden cowpath that works. I am just following it for the part of the
transcript problem that relates only to users with disabilities.

As for the programmatic linkage that you are after: my proposal
actually includes this with @transcript being a URL and not an IDREF
any longer for the reasons explained. Since it is now very clearly a
link, it is indeed possible for developers to experiment with buttons
or other interaction mechanisms on the video player if they want to.
So, I think it meets the requirement that you're posing.

Received on Thursday, 7 June 2012 13:55:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:28 UTC