WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: longdesc

for

From: Robinson, Norman B - Washington, DC - Contractor
Date: Jan 12, 2005 10:47AM

Thank you for the reference.

We have our own policy that describes those techniques as well. Those
techniques can be found in the AS-508-A Section 508 Technical Reference
Guide via URL:
http://www.usps.com/cpim/ftp/hand/as508a/508a_c6.html#oEx511274mudg.

As I posted an update to my request, I'll simply agree with you that it
is best to provide the text within the same document and via other
methods as long as they add to the end-user to accessing the
information, even if that means using all techniques and having the user
be able to choose.

Regards,


Norman B. Robinson
Section 508 Coordinator, US Postal Service

-----Original Message-----
From: paulb [mailto: <EMAIL REMOVED> ]
Sent: Wednesday, January 12, 2005 12:38 PM
To: WebAIM Discussion List
Subject: [WebAIM] longdesc



In light of the discussion about long descriptions and the longdesc
attribute, I thought I'd give a little input on the techniques of
providing descriptions for complex images, though I realize that my
response will address a larger concern than the specific issue brought
up (how to describe evacuation routes).

In general, there are 4 ways to describe complex graphics, listed below
in order of effectiveness (for most situations):
1. Provide the long description in the context of the document itself.
2. Provide a link to a long description via a normal text link. 3.
Provide a link to a long description via the longdesc attribute. 4.
Provide a link to a long description via a "d" link.

For the majority of cases, it is best to provide the text within the
same document as the image, because that way everyone can access it
without having to go to another page and without having to worry about
problems with assistive technologies or browsers.

The other options listed above may fit different circumstances, but are
less universal.

Both the longdesc attribute and the d-link concept were
well-intentioned, but problematic in terms of technology support, and in

terms of implementation--on a conceptual level--even within the best
technologies.

A bit more detail is available in the WebAIM tutorial at:
http://www.webaim.org/techniques/images/6

--
Paul Bohman
Director of Products and Services
WebAIM (Web Accessibility in Mind)
www.webaim.org
Utah State University
www.usu.edu

----
To subscribe or unsubscribe, visit http://www.webaim.org/discussion/