WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: LongDesc for documents, not websites

for

From: Vlad Alexander (XStandard)
Date: Apr 21, 2011 9:48AM

Bevi wrote "Also, the people creating these documents have no control over the government agency's website and where the documents will eventually reside on the site."

Sounds like a workflow problem rather than a longdesc problem. One solution is for your department to create a URL redirect service similar to TinyURL - let's call it GovURL for the purposes of this discussion.

1. Through GovURL, create URLs that will work as placeholders to these documents. For example:

http://govurl.gov/a6je9 = http://pubcom.com/temp/doc1.doc
http://govurl.gov/9h37d = http://pubcom.com/temp/doc2.pdf
http://govurl.gov/kd8u3 = [no url yet]

2. Use the URLs above in the longdesc attributes.

3. When the final destination of description documents is determined, modify the target URLs in GovURL service.

Regards,
-Vlad
http://xstandard.com


----- Original Message -----
From: <EMAIL REMOVED>
To: <EMAIL REMOVED>
Sent: 2011-04-21T05:50:34
Subject: Re: [WebAIM] LongDesc for documents, not websites

Just to reiterate, the solution must work for stand alone documents (mainly
Word and PDF files), as well as websites.
Also, the people creating these documents have no control over the
government agency's website and where the documents will eventually reside
on the site.

--Bevi

: : : : : : : : : : : : : : : : : : :
: : : : : : : : : : : : :
Bevi Chagnon | PubCom | <EMAIL REMOVED> | 301-585-8805
Government publishing specialists, trainers, consultants | print, press,
web, Acrobat PDF & 508
March-May Classes: www.pubcom.com/classes Section 508 Accessibility for
Word, InDesign, and Acrobat PDF
:�� :�� :�� :�� :�� :�� :�� :�� :�� :�� :�� :�� :�� :��
** It?s our 30th year! 1981-2011 **