<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Keith, Jeremy</title>	<link>http://tc.eserver.org/authors/Keith,_Jeremy</link>
	<description>A bibliography of works by Keith, Jeremy 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>Keith, Jeremy</title>
		<link>http://tc.eserver.org/dir/Keith,_Jeremy</link>
	</image>
	<item>
		<title>The Language of Accessibility</title>
		<link>http://tc.eserver.org/32508.html</link>
		<guid>http://tc.eserver.org/32508.html</guid>
		<description>Good markup is accessible by default. As long as you’re using HTML elements in a semantically meaningful way—which you should be doing anyway, without even thinking about accessibility—then your documents will be accessible to begin with.</description>
	</item>
	<item>
		<title>They Shoot Browsers, Don&apos;t They?</title>
		<link>http://tc.eserver.org/30886.html</link>
		<guid>http://tc.eserver.org/30886.html</guid>
		<description>Standards-aware developers, by their very nature, will object to adding a line of unnecessary markup to their documents just to get one single browser to behave as it should by default.</description>
	</item>
	<item>
		<title>Year Zero</title>
		<link>http://tc.eserver.org/30608.html</link>
		<guid>http://tc.eserver.org/30608.html</guid>
		<description>I am as frustrated as any other web developer at the glacial pace of the CSS Working Group and the lack of progress with CSS3. I just don&apos;t think we need to dump the baby out with the bathwater. Change is needed. It looks like change is coming. It may even be a regime change. But let&apos;s not start drawing up new calendar systems just yet. The clock of CSS is running slow. We need to wind it up. That doesn&apos;t mean we need to smash it.</description>
	</item>
	<item>
		<title>Behavioral Separation</title>
		<link>http://tc.eserver.org/27854.html</link>
		<guid>http://tc.eserver.org/27854.html</guid>
		<description>Breaking up is hard to do. But in web design, separation can be a good thing. Content, style, and behavior all deserve their own space. One of the greatest advantages to designing with Cascading Style Sheets is the potential for separation of style and content.</description>
	</item>
	<item>
		<title>JavaScript Image Gallery</title>
		<link>http://tc.eserver.org/25549.html</link>
		<guid>http://tc.eserver.org/25549.html</guid>
		<description>Making an online gallery of pictures should be a quick process. The gap between snapping some pictures and publishing them on the web ought to be a short one. Here’s a quick and easy way of making a one-page gallery that uses JavaScript to load images and their captions on the fly.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Keith,_Jeremy.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>