This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10077 - The <embed> should support an alt attribute. While the embedded content should provide for accessilibility of the embedded object, the developer doesn't always have control over those content, some embeddable formats are inherently less accessible, and th
Summary: The <embed> should support an alt attribute. While the embedded content shoul...
Status: VERIFIED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: a11y, a11ytf, a11y_text-alt
Depends on:
Blocks:
 
Reported: 2010-07-04 17:59 UTC by contributor
Modified: 2010-10-04 14:55 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2010-07-04 17:59:17 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-embed-element

Comment:
The <embed> should support an alt attribute. While the embedded content should
provide for accessilibility of the embedded object, the developer doesn't
always have control over those content, some embeddable formats are inherently
less accessible, and the developer should have a means to provide added
context (title can help, but different purpose) to help the user determine
whether the embedded content is worth navigating into.

Posted from: 99.170.149.16
Comment 1 Ian 'Hixie' Hickson 2010-08-30 18:27:01 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Just use <object> if you have something to fall back to.
Comment 2 Michael Cooper 2010-08-31 13:31:20 UTC 
http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0013.html

The bug triage sub-team recommends the accessibility task force follow this.
Comment 3 Michael Cooper 2010-08-31 13:33:26 UTC 
The bug triage sub-team thinks we need to determine how text alternative approach works on <embed>
Comment 4 Michael Cooper 2010-08-31 16:54:58 UTC 
Bug triage sub-team accepts wontfix status of this bug. The core issue is represented by Bug 8885, and we will work on providing the needed information there.