E-mail List Archives
Re: LongDesc for documents, not websites
From: Bevi Chagnon | PubCom
Date: Apr 21, 2011 8:36PM
- Next message: Vlad Alexander (XStandard): "Re: LongDesc for documents, not websites"
- Previous message: Bevi Chagnon | PubCom: "Re: LongDesc for documents, not websites"
- Next message in Thread: Vlad Alexander (XStandard): "Re: LongDesc for documents, not websites"
- Previous message in Thread: Bevi Chagnon | PubCom: "Re: LongDesc for documents, not websites"
- View all messages in this Thread
Vlad wrote:
" Sounds like a workflow problem rather than a longdesc problem"
Hmm. Have you worked on a federal government website with millions of pages with national security requirements? <grin>
The URL redirect could work, but is likely to have several stumbling blocks.
1) The tasks would be performed by 2 distinct groups of people, the document creators and the web team.
2) Successfully coordinating these 2 teams over the course of several months is dicey.
3) At some agencies, a web team will process several hundred documents a day. It's quite likely that they'll overlook changing the 100+ URL redirects in one PDF out of the many other documents they process that day.
I think this can be a viable solution for a smaller organization with tighter work teams, and I'll keep it as an option.
Thanks,
--Bevi
___________________
Bevi Chagnon / PubCom
Government publishing specialists, trainers, consultants
Print, press, web, Acrobat PDF and 508
April-May Classes: www.pubcom.com/classes Section 508 Accessibility for Word, InDesign, and Acrobat PDF
- Next message: Vlad Alexander (XStandard): "Re: LongDesc for documents, not websites"
- Previous message: Bevi Chagnon | PubCom: "Re: LongDesc for documents, not websites"
- Next message in Thread: Vlad Alexander (XStandard): "Re: LongDesc for documents, not websites"
- Previous message in Thread: Bevi Chagnon | PubCom: "Re: LongDesc for documents, not websites"
- View all messages in this Thread