<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Accessibility&gt;Writing</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Accessibility/Writing</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and Accessibility and Writing in the field of technical communication (and technical writing).</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;Web Design&gt;Accessibility&gt;Writing</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Accessibility/Writing</link>
	</image>
	<item>
		<title>New Accessibility Guidelines Part III: Understandability</title>
		<link>http://tc.eserver.org/34618.html</link>
		<guid>http://tc.eserver.org/34618.html</guid>
		<description>The understandability of text is crucial to web accessibility. At broad levels, this means specifying text languages, explaining the meanings of jargon or idioms, and expanding abbreviations to clarify text. It&apos;s not just text that can present a barrier to accessibility, however. A lack of organizational predictability or proper error management can greatly decrease the accessibility of any website.</description>
	</item>
	<item>
		<title>Best Practices: Writing for Accessibility</title>
		<link>http://tc.eserver.org/32906.html</link>
		<guid>http://tc.eserver.org/32906.html</guid>
		<description>Most of the time, the primary focus of information about accessibility has to do with making non-text information available as text. Captioning and audio description for video, transcriptions for audio, simple text alternatives for static images. But what about the content itself?</description>
	</item>
	<item>
		<title>National Policies for Government Web Writers</title>
		<link>http://tc.eserver.org/26144.html</link>
		<guid>http://tc.eserver.org/26144.html</guid>
		<description>Every country has its own requirements for public sector web sites. Legislation and policies vary greatly, and express an attitude. I base my Quality Web Content workshops for government web content writers on the policy of the country concerned. Some countries consider that an accessible site requires accessible writing. Others don&apos;t.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Accessibility/Writing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>