This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
How does longdesc and @aria-describedby work together? What should happen when/if both are used on the same <img>? Solving this problem will tell authors whether it is useful to use both, or always just a waste of time/space, sometimes useful etc. Example: <img aria-describedby=samepage-fragment longdesc=#samepage-fragment src=foo alt="Foo. Bar."> What if aria-describedby contains a IDREF _list_? Should that impact how one uses @longdesc? Example: <img aria-describedby=samepage-fragment-1 samepage-fragment-2 samepage-fragment-3 longdesc=#samepage-fragment-1 src=foo alt="Foo. Bar."> Are there cases when it is useful to _both_ point to long description on the same page (via aria-describedby) _and_ to a long description on another page? Or should this cause a warning, for some reason? Example: <img aria-describedby=samepage-fragment longdesc=other-page src=foo alt="Foo. Bar.">
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: The longdesc is obsolete, per WG decision.
ISSUE-30 has been appealed, and the Appeal is awaiting response from the Team Contact and/or Director. http://www.w3.org/mid/20100815024127561631.58433bf1@xn--mlform-iua.no
Please don't reopen unless the appeal succeeds.
http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0013.html The bug triage sub-team thinks the HTML A11Y TF does not need to formally follow this bug. Original submitters or other interested parties may choose to continue to push this issue on their own. Notes from the sub-team may follow in a separate comment.
Bug triage sub-team notes that this issue is captured in the text alternatives proposal http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126 and it is already defined that ARIA overrides native features.