Improper use of longdesc attribute and user interface confusion

Hi!
you are right
to solve the problem you can edit

1) marinelli_configure_cycle.js using -> var description = $(this).attr("alt");
2) marinelli_banner text.js using ->var desc = $('img.slide').attr("alt");
3) banners.inc removing 'longdesc' => t('@image_desc', array('@image_desc'=>$banner['image_description'])) line

Hi I have used longdesc only once on a website where I published flyers for an event. I had the text of the flyer on another page anyway, so I pointed longdesc to other-page.html#text. Though on other-page.html was a smaller image of the flyer, and that also pointed to #text. That seemed reasonable. What I didn't know then was that browsers or rather screenreaders fail to implement the mechanism to open longdescs properly, so I used it on a linked image. Thanks for sharing that. Essay Examples l Essay Sample

But the whole case reminds me of the alt-attribute. We have an attribute where people don't know how to use it properly. Also we have faulty browser implementations that lead people to misuse the attribute (as a tooltip). Is that reason enough to remove it from the specification, or shouldn't we rather educate developers and build pressure on browser and screenreader vendors? longdesc is obscure, but in certain cases it is very useful and less pain than adding a link. I would rather tell screenreader vendors to fix that behavior according to the specs than removing a reasonable element.

Patch

Bump....