This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The algorithm for object specifies that a user agent picks the "first one it supports" -- suggest that this model be revised to allow user agents to identify nested children that may not have been rendered and display them instead. The problem that this addresses is that it allows for situations where the format can be accessible, but often isn't (ex. Flash), allowing users to choose an alternative without having to configure their browsers to render a particular content type differently depending on the site that they happen to be visiting.
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: Accepted Change Description: see diff given below Rationale: The UA can always identify nested children, the spec doesn't need to allow it. However, I've made it clearer in the spec that the UA is also allowed to _show_ such fallback content at the user's option.
Checked in as WHATWG revision r4525. Check-in comment: Allow users to disable an <object> to show its fallback instead. http://html5.org/tools/web-apps-tracker?from=4524&to=4525
Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future.