W3C home > Mailing lists > Public > public-html@w3.org > September 2008

RE: Accessibility of <audio> and <video>

From: Justin James <j_james@mindspring.com>
Date: Tue, 2 Sep 2008 08:57:01 -0400
To: "'Lachlan Hunt'" <lachlan.hunt@lachy.id.au>, "'Matthew Raymond'" <mattraymond@earthlink.net>
Cc: <public-html@w3.org>
Message-ID: <0e8601c90cfb$644c81f0$2ce585d0$@com>

> -----Original Message-----
> From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
> Behalf Of Lachlan Hunt
> Sent: Tuesday, September 02, 2008 8:08 AM
> To: Matthew Raymond
> Cc: public-html@w3.org
> Subject: Re: Accessibility of <audio> and <video>
> Matthew Raymond wrote:
> > Lachlan Hunt wrote:
> >>> It is when looking at the fallback, that we should be offered the
> choice
> >>> between how we want the video served: as slides, transcript or the
> very
> >>> video.
> >> Right, and I'm ok with providing all of that in a way that is
> available
> >> to everyone, and providing it or a link to it from within the
> >> surrounding content seems most appropriate for that.
> >
> >    Perhaps we can provide some attribute values for |rel| along these
> lines:
> >
> >  * "transcript"
> >  * "slideshow"
> >  * "download"
> We already have rel="alternate", although it's currently only defined
> to
> mean an alternative for the whole document, and there have been
> previous
> suggestions for rel="longdesc".  However, if the problem is helping
> users of assistive technology identify which links are to alternative
> content, then it still needs to be demonstrated that:

This is what I proposed as well... I also added the possibility of putting a @longdesc in the element too. I think it is a good way of handling it. Use an attribute for moderate amounts of text, and an URL for large amounts of text (or frequently referenced text).

> 1. Something like that is actually necessary for solving the problem,
>     rather than just providing suitable link text that describes its
>     purpose, and

I agree, we need the accessibility people to weigh in on this and see if it is worth pursuing.

> 2. That it would successfully solve the problem.

Ditto my above remark. :)

Received on Tuesday, 2 September 2008 12:57:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:23 GMT