<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Bartlett, Kynn</title>	<link>http://tc.eserver.org/authors/Bartlett,_Kynn</link>
	<description>A bibliography of works by Bartlett, Kynn 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>Bartlett, Kynn</title>
		<link>http://tc.eserver.org/dir/Bartlett,_Kynn</link>
	</image>
	<item>
		<title>Designing Pages Accessible to Limited Textual Comprehension Users</title>
		<link>http://tc.eserver.org/32915.html</link>
		<guid>http://tc.eserver.org/32915.html</guid>
		<description>Little has been written or done to advance the cause of web users with cognitive disabilities -- users who may actually require the use of graphics in order to make sense of a web site. For purposes of this document, we will use the term &quot;Limited Textual Comprehension&quot; to refer to anyone, disabled or not, who is unable to understand a web page -- and thus cannot access the information contained within in it -- due to the textual content of the page.</description>
	</item>
	<item>
		<title>Accessibility and Cascading Style Sheets</title>
		<link>http://tc.eserver.org/23822.html</link>
		<guid>http://tc.eserver.org/23822.html</guid>
		<description>An essay from an accessibility class, on the use of CSS to increase  access to a page.</description>
	</item>
	<item>
		<title>Designing Pages Accessible to Limited Textual Comprehension Users</title>
		<link>http://tc.eserver.org/23820.html</link>
		<guid>http://tc.eserver.org/23820.html</guid>
		<description>Many pages relating to web accessibility address the needs of web  users who have sensory limitations -- the classic example of accessible web authoring is the proper use of the ALT attribute of the IMG (image)  tag to provide a textual equivalent that benefits, among others,  web users with visual impairments. Similarly, keyboard-accessible techniques can open up the World Wide Web to users who are unable to  use a mouse or other &apos;traditional&apos; input device due to motor or dexterity disabilities.</description>
	</item>
	<item>
		<title>Six Principles of Accessible Web Design: An Introduction to the WAI Page Author Guidelines</title>
		<link>http://tc.eserver.org/23825.html</link>
		<guid>http://tc.eserver.org/23825.html</guid>
		<description>An introduction to the W3C&apos;s Web Content Accessibility Guidelines.</description>
	</item>
	<item>
		<title>User-Defined Style Sheets and Accessibility</title>
		<link>http://tc.eserver.org/23823.html</link>
		<guid>http://tc.eserver.org/23823.html</guid>
		<description>How you can set your own stylesheet for greater accessibility; another lecture/essay.</description>
	</item>
	<item>
		<title>Web Accessibility Icons and Graphics</title>
		<link>http://tc.eserver.org/23821.html</link>
		<guid>http://tc.eserver.org/23821.html</guid>
		<description>How can you display that your site is accessible? Why would you want to? These questions are answered.</description>
	</item>
	<item>
		<title>Web Authoring Strategies for Voice Browsers</title>
		<link>http://tc.eserver.org/23824.html</link>
		<guid>http://tc.eserver.org/23824.html</guid>
		<description>A HWG position paper for a W3C workshop on voice browsers.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Bartlett,_Kynn.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>