E-mail List Archives
Re: LongDesc for documents, not websites
From: Karlen Communications
Date: Apr 20, 2011 4:51AM
- Next message: Will Grignon: "Re: LongDesc for documents, not websites"
- Previous message: Jukka K. Korpela: "Re: Do screen readers read title attirbute if there is no label tag on form elements?"
- Next message in Thread: Will Grignon: "Re: LongDesc for documents, not websites"
- Previous message in Thread: Bevi Chagnon | PubCom: "LongDesc for documents, not websites"
- View all messages in this Thread
For PDF I suggest using the ability to attach documents to a PDF. I also
point people to the Wright State University/Dayton Art Institute project "A
Picture is worth 300 Words" which was a CSUN presentation.
http://www.csun.edu/cod/conf/2001/proceedings/0031alonzo.htm
Although created for artwork, the guidelines can be used to build a
framework for describing complex images in documents so that the
descriptions don't become essays themselves.
For PDF this lets the descriptions travel with the PDF which means that
people don't have to go looking for them. As someone who uses a screen
reader I will seldom go looking for a description of something on another
web site. I just figure that it isn't important enough to travel with the
document. I also suggest using a TXT file to house the description or a
plain vanilla Word document without a lot of formatting/formatting as
needed. Of course I'm not in school depending on access to a textbook.
The Alt Text for the image is something like "detailed description attached:
filename X." If the document author has used captions I refer to the figure
number in the filename. Depending on how many complex images there are in a
document I may have a detail document for each image or one file with all
descriptions formatted with headings for navigation.
For Word documents the only suggestion I have is creating the actual link to
the Appendices once the document has been approved. Again I hate having to
go somewhere else on a server or site to read details of complex images or
other information. That is my preference but it has made me think about how
to integrate everything so that it is easy to find for everyone.
I also suggest that if someone is not going to use the Notes area of
PowerPoint that this area be used to provide the more detailed information
about an image on a slide. This is part of the decision making process in
determining how the PowerPoint document will be distributed and what types
of content are accessible or not given the distribution methods.
My PDF exploration in figuring out a solution for this type of content came
about when trying to make Visio based PDF accessible. I had a huge process
chart with tons of acronyms and abbreviations and the attachment of a plain
Word document with expanded acronyms and abbreviations made the chart easier
for everyone to understand.
Now your post has me considering a solution for this in Word. <smile>
Cheers, Karen
- Next message: Will Grignon: "Re: LongDesc for documents, not websites"
- Previous message: Jukka K. Korpela: "Re: Do screen readers read title attirbute if there is no label tag on form elements?"
- Next message in Thread: Will Grignon: "Re: LongDesc for documents, not websites"
- Previous message in Thread: Bevi Chagnon | PubCom: "LongDesc for documents, not websites"
- View all messages in this Thread