- From: <bugzilla@jessica.w3.org>
- Date: Mon, 12 Dec 2011 05:06:45 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12794 --- Comment #8 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-12-12 05:06:44 UTC --- (In reply to comment #7) > Why do authors need anything other than just regular markup? To take your > example: > > <h1>A Clockwork Orange Trailer</h1> > <video src="file.mp4" poster="poster.png"></video> > <p><a href="file.mp4">Download the video file</a>. > <a href="transcript.html">Veiw the transcript</a>.</p> That's certainly possible, and if @aria-describedby attribute was added to the video that linked to the transcript, that would allow screenreaders to announce it early, too. 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. > Can you point me to some existing sites to show how they handle this today? > e.g. how does YouTube handle this? YouTube doesn't have a means to expose transcripts to embedded videos right now. This is actually a drawback with YouTube videos and users are trying to fix it by cutting and pasting he whole transcript into the "description" section. However, that is lost when YouTube videos are embedded. -- 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 Monday, 12 December 2011 05:08:46 UTC