Edit comment LC-786 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1075 Next: LC-1326

Comment LC-786: Comment Shortname:; Commenter: Joe Clark 1 <joeclark@joeclark.org>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Comment:

From http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/0120.html

Text alternatives

[INS: [For n] :INS] on-text content that is multimedia... it is important that users know what it is when they encounter it on a page so they can decide what action if any they want to take with it. A text alternative that describes the multimedia and/or gives its title is therefore provided.

How do I do that with, say, embed, which permits no fallback content? (Of course there's noembed, but, since all graphical browsers understand embed, noembed content will never be displayed. In any event, there is no actual or official specification for embed and especially noembed.) Does this not mean I have to label each video in plain text?; Related issues: (space separated ids); WG Notes: [TEAMC] [HOLD] With <object>, if the browser cannot retreive the requested object and successfully process it, either by executing the applet or by processing the object's data with a plug-in application, the browser will display the contents of the <object> element. With <embed>, there is no way to provide alternative content within the element. And the <noembed> element content is only rendered if the browser doesn't support <embed>. I don't know what happens if the browser supports <embed> but something goes wrong with trying to render the content. But Joe is saying that all browsers support <embed> so the <noembed> content will never be rendered and there is no way to provide alternative content. Discussed in the 02 November 2006 telecon: Resolution: Accept 786 as revised http://www.w3.org/WAI/GL/2006/11/02-wai-wcag-minutes.html Moved H46 to advisory section and added an editorial note to H46 about pending action item. XML source updated 16 January 2007. DONE move "Using noembed with embed" to advisory and add user agent notes section to reflect details about user agents that support this {accept} NOT DONE Create a technique for providing text alternatives for EMBED in same doc (or as 'd-link') BBC: The action to create a technique about d-link type strategy is already covered by existing general techs, so was not included in the draft.; Resolution: We have moved the technique on using noembed with embed to advisory. General techniques are available which describe alternative methods on providing text alternatives for EMBED.; (Please make sure the resolution is adapted for public consumption)