<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Accessibility&gt;Visual</title>	<link>http://tc.eserver.org/dir/Articles/Accessibility/Visual</link>
	<description>A listing of the most recently indexed works about Articles and Accessibility and Visual in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Accessibility&gt;Visual</title>
		<link>http://tc.eserver.org/dir/Articles/Accessibility/Visual</link>
	</image>
	<item>
		<title>Read-Aloud PDFs</title>
		<link>http://tc.eserver.org/35187.html</link>
		<guid>http://tc.eserver.org/35187.html</guid>
		<description>Are you aware that PDF documents are readable by your computer? You can listen to any PDF instead of reading it!</description>
	</item>
	<item>
		<title>Designing for Screen Reader Compatibility</title>
		<link>http://tc.eserver.org/34634.html</link>
		<guid>http://tc.eserver.org/34634.html</guid>
		<description>Techniques that work for one screen reader almost always work in other screen readers. In some cases, one of the screen readers has capabilities that the others do not have, or handles some types of content better than the other screen readers. Still, developers are almost always better off when they focus on accessibility standards and generally-accepted accessibility techniques than when they focus on screen reader differences.</description>
	</item>
	<item>
		<title>How to Avoid Screen Reader &apos;Noise Pollution&apos;</title>
		<link>http://tc.eserver.org/32916.html</link>
		<guid>http://tc.eserver.org/32916.html</guid>
		<description>Surely there can&apos;t be a skill to writing ALT text for images? You just pop a description in there and you&apos;re good to go, right? Well, kind of. Sure, it&apos;s not rocket science, but there are a few guidelines you need to follow.</description>
	</item>
	<item>
		<title>Adaptive Technologies and Techniques for People with Vision Problems</title>
		<link>http://tc.eserver.org/29736.html</link>
		<guid>http://tc.eserver.org/29736.html</guid>
		<description>Talk with Gloria Reece, a senior member of STC’s AccessAbility SIG who can help you understand vision problems and the technologies that exist to make information accessible. Get practical advice for implementing new technologies in your workplace.</description>
	</item>
	<item>
		<title>Accessibility Testing: Case History of Blind Testers of Enterprise Software</title>
		<link>http://tc.eserver.org/26851.html</link>
		<guid>http://tc.eserver.org/26851.html</guid>
		<description>How do software companies evaluate whether accessibility criteria mandated by law are met? Confirmation is often provided by filling out a checklist. However, the method used for determining compliance to the checklist is not specified. Typically the task of filling out the checklist is done by accessibility specialists, usability professionals, quality assurance testers, or, in one case we know of, the development team that wrote the software. We have conducted several types of accessibility evaluations, walkthroughs, and testing with scenarios by sighted test participants and testing by blind test participants. While testing with blind participants takes considerable preparation time, we have uncovered important findings that were not revealed with sighted participants. We consider accessibility testing by blind participants an important component of our evaluations.</description>
	</item>
	<item>
		<title>Copyright and Persons with Print Disabilities in the Digital Age</title>
		<link>http://tc.eserver.org/19442.html</link>
		<guid>http://tc.eserver.org/19442.html</guid>
		<description>The American Foundation for the Blind (AFB) stands squarely in favor of reasonable and prudent technologies to assist in ensuring that copyright holders are fairly compensated for the sale, or other forms of digital access, of the content they publish in digital formats. However,most proposals we have seen to date purporting to establish technologies to prevent illegal copying or publication of copyrighted content simply do not consider, or address in any way, the fair use rights of persons who are blind and visually impaired. We would regard it a serious breach of faith with disabled persons to establish new technologies and copyright provisions which, once again, regard our needs as peripheral and expendable. To this end we offer the following positions on this issue of fundamental importance to this community.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Accessibility/Visual.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>