- From: David Singer <singer@apple.com>
- Date: Wed, 21 Mar 2012 16:48:32 -0700
- To: John Foliot <john@foliot.ca>
- Cc: 'Sean Hayes' <Sean.Hayes@microsoft.com>, janina@rednote.net, 'Silvia Pfeiffer' <silviapfeiffer1@gmail.com>, "'"'xn--mlform-iua@målform.no'"'" <xn--mlform-iua@xn--mlform-iua.no>, rubys@intertwingly.net, laura.lee.carlson@gmail.com, mjs@apple.com, 'Paul Cotton' <Paul.Cotton@microsoft.com>, public-html-a11y@w3.org, public-html@w3.org
I don't have formal proposals; but I don't see any problem with * a formalized short name (omigod alt text), but it shouldn't be an attribute value (in case it needs attributes, and anyway, we should never present attribute values, presented text should be part of the stuff that's marked up) * where the long description is * where the transcript is I would explore in the direction of elements under audio/video and parallel to track: (sketching furiously here) <video…> <track…> <link rel="longdesc" href="…" /> <link rel="transcript" href="…" /> <div rel="alt" lang="cn-US">alternative text</div> </video> Similarly the tracks could indicate timed accessibility alternatives via their "kind" label. And these are all useful for all users; a programmatic way to find the transcript, description, and short text benefit all boats. David Singer Multimedia and Software Standards, Apple Inc.
Received on Wednesday, 21 March 2012 23:49:06 UTC