<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Easton, Bob</title>	<link>http://tc.eserver.org/authors/Easton,_Bob</link>
	<description>A bibliography of works by Easton, Bob 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>Easton, Bob</title>
		<link>http://tc.eserver.org/dir/Easton,_Bob</link>
	</image>
	<item>
		<title>Screen Readers and CSS Layout</title>
		<link>http://tc.eserver.org/32859.html</link>
		<guid>http://tc.eserver.org/32859.html</guid>
		<description>Screen readers are mostly mystical devices for almost all of us. Few of us actually own them. They’re incredibly expensive. Fewer yet know how to use them well, what their capabilities are, or how they actually work. Is it little wonder then, that big names in our web design world question how screen readers handle modern layout techniques? Not at all. The two gurus quoted below have other strengths, and specialities. They probably haven’t used a screen reader in ages.</description>
	</item>
	<item>
		<title>Speaking ALT Text</title>
		<link>http://tc.eserver.org/32866.html</link>
		<guid>http://tc.eserver.org/32866.html</guid>
		<description>I have a few late model screen readers and I also have simple audio recording tools. I&apos;ll use them to get you closer to what these screen readers actually say. I&apos;ll start a collection of recordings so you can hear for yourself what these tools say.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Easton,_Bob.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>