<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Books&gt;Web Design&gt;Accessibility</title>	<link>http://tc.eserver.org/dir/Books/Web-Design/Accessibility</link>
	<description>A listing of the most recently indexed works about Books and Web Design and Accessibility 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>Books&gt;Web Design&gt;Accessibility</title>
		<link>http://tc.eserver.org/dir/Books/Web-Design/Accessibility</link>
	</image>
	<item>
		<title>Affrontare l&apos;Accessibilità</title>
		<link>http://tc.eserver.org/27665.html</link>
		<guid>http://tc.eserver.org/27665.html</guid>
		<description>Questo libro risponde a due domande. La prima  è &quot;Perchè dovrei rendere più accessibile il mio sito?&quot;  E se non avete un sito web, questo libro non è per voi. La seconda domanda è  &quot;Come posso rendere il mio sito più accessibile?&quot;  Se non siete convinti della vostra prima risposta, non sarete di certo interessati alla seconda.</description>
	</item>
	<item>
		<title>Kast deg ut i Tilgjengelighet</title>
		<link>http://tc.eserver.org/27663.html</link>
		<guid>http://tc.eserver.org/27663.html</guid>
		<description>Denne boka vil besvare to spørsmål. Det første spørsmålet er «Hvorfor bør jeg gjøre nettstedet mitt mer tilgjengelig?» Om du ikke har et nettsted, så er ikke denne boka for deg. Det andre spørsmålet er «Hvordan kan jeg gjøre nettstedet mitt mer tilgjengelig?» Er du ikke overbevist av svaret på det første spørsmålet, vil du nok ikke være interessert i det andre.</description>
	</item>
	<item>
		<title>Plongez dans l&apos;Accessibilité</title>
		<link>http://tc.eserver.org/27664.html</link>
		<guid>http://tc.eserver.org/27664.html</guid>
		<description>Ce livre répond à deux questions. La première question est Pourquoi je dois rendre mon site web plus accessible ? Si vous n&apos;avez pas de sites web, ce livre n&apos;est pas pour vous. La seconde question est Comment puis-je rendre mon site web plus accessible ? Si vous n&apos;êtes pas convaincu par la première réponse, vous ne serez pas interessé par la seconde.</description>
	</item>
	<item>
		<title>W g&amp;#322;&amp;#261;b Dost&amp;#281;pno&amp;#347;ci</title>
		<link>http://tc.eserver.org/27667.html</link>
		<guid>http://tc.eserver.org/27667.html</guid>
		<description>Niniejsza ksi&amp;#261;&amp;#380;ka odpowiada na dwa pytania. Pierwsze brzmi: &apos;Dlaczego powinienem uczyni&amp;#263; swoj&amp;#261; stron&amp;#281; WWW bardziej dost&amp;#281;pn&amp;#261;?&apos; Je&amp;#380;eli nie masz strony w sieci, ta ksi&amp;#261;&amp;#380;ka nie jest dla Ciebie. Drugie pytanie to &apos;Jak mog&amp;#281; uczyni&amp;#263; moj&amp;#261; stron&amp;#281; bardziej dost&amp;#281;pn&amp;#261;?&apos; Je&amp;#380;eli nie zostaniesz przekonany przez odpowied&amp;#378; na pierwsze pytanie, nie b&amp;#281;dziesz zainteresowany odpowiedzi&amp;#261; na drugie.</description>
	</item>
	<item>
		<title>もっとアクセシブルなサイトにする30日計画</title>
		<link>http://tc.eserver.org/27666.html</link>
		<guid>http://tc.eserver.org/27666.html</guid>
		<description>この文書は2つの質問に答えるために書いてみたんだ。 1コ目は、「なんでサイトをアクセシブルにした方がいいのか」。だから、ここの情報はサイトを持ってない人には向かないかも。 2コ目は、「じゃどうしたらサイトをアクセシブルにできるのか」。 1コ目の答えが納得できるものじゃなかったら、2コ目はどうでもいいってことになるよね。</description>
	</item>
	<item>
		<title>在 30 天內打造更具親和力的網站</title>
		<link>http://tc.eserver.org/27662.html</link>
		<guid>http://tc.eserver.org/27662.html</guid>
		<description>這本書要回答兩個問題：第一個問題是「為什麼該讓我的網站更具親和力？」如果妳根本就沒有網站的話，顯然就不會成為本書的讀者了。第二個問題是「該如何讓我的網站更具親和力？」如果第一個問題的回答說服不了妳，那麼第二個問題大概也將無法引起妳的興趣。</description>
	</item>
	<item>
		<title>Advanced Techniques for Creating Accessible Adobe® PDF Files</title>
		<link>http://tc.eserver.org/27140.html</link>
		<guid>http://tc.eserver.org/27140.html</guid>
		<description>A step-by-step guide that covers more advanced techniques for optimizing Adobe Portable Document Format (PDF) files so that they can be made accessible to users with disabilities such as blindness or low vision.</description>
	</item>
	<item>
		<title>More Than Screen Deep: Toward Every-Citizen Interfaces to the Nation&apos;s Information Infrastructure</title>
		<link>http://tc.eserver.org/25801.html</link>
		<guid>http://tc.eserver.org/25801.html</guid>
		<description>The spread of information systems and, in particular, information infrastructure throughout the economy and social fabric raises questions about the technology&apos;s ease of use by different people, from those with limited technical know-how to those with various disabilities to the so-called power users who push for higher performance on many dimensions.</description>
	</item>
	<item>
		<title>Dive Into Accessibility: 30 Days to a More Accessible Web Site</title>
		<link>http://tc.eserver.org/21041.html</link>
		<guid>http://tc.eserver.org/21041.html</guid>
		<description>This book answers two questions. The first question is &apos;Why should I make my web site more accessible?&apos; If you do not have a web site, this book is not for you. The second question is &apos;How can I make my web site more accessible?&apos; If you are not convinced by the first answer, you will not be interested in the second.</description>
	</item>
	<item>
		<title>Building Accessible Websites: Serialization</title>
		<link>http://tc.eserver.org/20055.html</link>
		<guid>http://tc.eserver.org/20055.html</guid>
		<description>Designers assume accessibility means a boring site, a myth borne out by oldschool accessibility advocates, whose hostility to visual appeal is barely suppressed. Neither camp has its head screwed on right. It&apos;s not either/or; it&apos;s both/and.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Books/Web-Design/Accessibility.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>