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

[Bug 17463] 'sign' and 'captions' as attributes

From: <bugzilla@jessica.w3.org>
Date: Tue, 12 Jun 2012 12:58:42 +0000
To: public-html-a11y@w3.org
Message-Id: <E1SeQgE-0007XY-RF@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17463

--- Comment #4 from Devarshi Pant <devarshipant@gmail.com> 2012-06-12 12:58:42 UTC ---
> I would like to refocus this bug on this problem if it's ok, seen as the
> information that you are after is already available through text tracks and
> synchronized media resources.

Yes, it is ok with me. 

(In reply to comment #3)
> (In reply to comment #2)
> > This is what I have in mind: Users who interrogate pages using commands like
> > the links list (say, on YouTube), will get something like, 'Video Name XYZ 1,
> > Signing available, Captions not available, Transcript available'; 'Video Name
> > XYZ 2, Signing Not available, Captions not available, Transcript not available'
> > etc.
> > I would like to know if such attributes can be exposed for video. Could AT
> > vendors use these values?
> We already have markup for captions, video descriptions, synchronized video
> like sign language video, and synchronized audio like audio descriptions. We
> are currently solving the transcript use case (see bug 12964). All of these
> will be machine discoverable, so a screen reader does indeed have all
> functionality available from HTML for making the announcements that you are
> asking for.
> > Coming to your proposed use case, yes, making the video tabfocusable would
> > work, but isn't that already happening? Wouldn’t it help when assistive
> > technology could announce / convey information regarding these attributes
> > (discussed above) when the video has keyboard focus?
> It is possible to focus on the video element with AT, i.e. your screenreader
> may choose to focus on video and audio elements. However, my last test has
> shown that neither VoiceOver nor ChromeVox provide focus on audio and video
> elements. And neither does the browser in their default tabfocus. I had to put
> explicit @tabindex attributes onto the media elements to allow them to receive
> focus.
> As the video is specified right now, it is not tabfocusable and only
> interactive when it has controls. Thus, the interaction that you are after with
> announcing information when the video has keyboard focus can't be achieved.
> I would like to refocus this bug on this problem if it's ok, seen as the
> information that you are after is already available through text tracks and
> synchronized media resources.

-- 
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 Tuesday, 12 June 2012 12:58:53 UTC

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