<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Clark, Joe</title>	<link>http://tc.eserver.org/authors/Clark,_Joe</link>
	<description>A bibliography of works by Clark, Joe 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>Clark, Joe</title>
		<link>http://tc.eserver.org/dir/Clark,_Joe</link>
	</image>
	<item>
		<title>Unwebbable</title>
		<link>http://tc.eserver.org/35174.html</link>
		<guid>http://tc.eserver.org/35174.html</guid>
		<description>It’s time we came to grips with the fact that not every “document” can be a “web page.” Some forms of writing just cannot be expressed in HTML—or they need to be bent and distorted to do so. But for once, XML might actually help.</description>
	</item>
	<item>
		<title>This is How the Web Gets Regulated</title>
		<link>http://tc.eserver.org/33309.html</link>
		<guid>http://tc.eserver.org/33309.html</guid>
		<description>As in finance, so on the web: self-regulation has failed. Nearly ten years after specifications first required it, video captioning can barely be said to exist on the web. The big players, while swollen with self-congratulation, are technically incompetent, and nobody else is even trying. So what will it take to support the human and legal rights of hearing impaired web users? It just might take the law, says Joe Clark.</description>
	</item>
	<item>
		<title>Screen-Reader Usability at a Standards-Compliant E-Commerce Site</title>
		<link>http://tc.eserver.org/32860.html</link>
		<guid>http://tc.eserver.org/32860.html</guid>
		<description>An E-commerce site was redesigned with Web standards in mind. The revised site used semantic HTML markup that usually passes validation tests and also incorporated many common accessibility features. A study was carried out with screen-reader users to determine how well compliance with Web standards and accessibility guidelines translated into actual usability and accessibility. </description>
	</item>
	<item>
		<title>ATAG (Authoring Tool Accessibility Guidelines) Assessment of WordPress</title>
		<link>http://tc.eserver.org/30604.html</link>
		<guid>http://tc.eserver.org/30604.html</guid>
		<description>This document assesses WordPress 2.01 against the Authoring Tool Accessibility Guidelines 1.0.</description>
	</item>
	<item>
		<title>Best Practices in Online Captioning</title>
		<link>http://tc.eserver.org/30603.html</link>
		<guid>http://tc.eserver.org/30603.html</guid>
		<description>Use of online video has grown faster than the use of accessibility in online video. Though bandwidth costs for video files can still be high compared to ordinary text-and-graphics Web pages, it is nonetheless easy to digitize video and post it online. It&apos;s easier to broadcast your video to the world via the Internet than it is to get the same video on television. Online multimedia are a useful and valid new medium of communication - for most people.</description>
	</item>
	<item>
		<title>DVDs with Audio Description</title>
		<link>http://tc.eserver.org/30606.html</link>
		<guid>http://tc.eserver.org/30606.html</guid>
		<description>DVDs can carry up to eight audio tracks. It is theoretically possible to provide main audio and dubbing in three languages and audio description in all four languages. In practice, all anybody&apos;s asking for is an audio description track in the main language of the audio.</description>
	</item>
	<item>
		<title>Zoom Layouts</title>
		<link>http://tc.eserver.org/30605.html</link>
		<guid>http://tc.eserver.org/30605.html</guid>
		<description>A zoom layout uses CSS (cascading stylesheets) to automatically reformat a page so it&apos;s easier for a low-vision user to read. Multiple columns become single columns, navigation gets simplified and put at the top, fonts become bigger, and (usually) colours are set to light on dark.</description>
	</item>
	<item>
		<title>To Hell with WCAG 2</title>
		<link>http://tc.eserver.org/27674.html</link>
		<guid>http://tc.eserver.org/27674.html</guid>
		<description>The Web Content Accessibility Guidelines 1.0 were published in 1999 and quickly grew out of date. The proposed new WCAG 2.0 is the result of five long years’ work by a Web Accessibility Initiative (WAI) committee that never quite got its act together. In an effort to be all things to all web content, the fundamentals of WCAG 2 are nearly impossible for a working standards-compliant developer to understand. WCAG 2 backtracks on basics of responsible web development that are well accepted by standardistas. WCAG 2 is not enough of an improvement and was not worth the wait.</description>
	</item>
	<item>
		<title>Facts and Opinions About PDF Accessibility</title>
		<link>http://tc.eserver.org/26228.html</link>
		<guid>http://tc.eserver.org/26228.html</guid>
		<description>PDF accessibility is not as straightforward as HTML accessibility. But it can be done, if you put the same care into marking up your PDFs that you put into marking up websites. Joe Clark tells all.</description>
	</item>
	<item>
		<title>How to Save Web Accessibility from Itself</title>
		<link>http://tc.eserver.org/25505.html</link>
		<guid>http://tc.eserver.org/25505.html</guid>
		<description>If you choose to make standards-compliant websites, inevitably you will have to follow the guidelines. It&apos;s foreseeable that you could be legally required to follow WCAG 2.0. You could opt into following the guidelines or they could be foisted upon you. You thus have an enlightened self-interest in ensuring the new guidelines actually make sense. Moreover, we simply need more contributors.</description>
	</item>
	<item>
		<title>Big, Stark and Chunky</title>
		<link>http://tc.eserver.org/25262.html</link>
		<guid>http://tc.eserver.org/25262.html</guid>
		<description>Research shows that low-vision people need dramatically different web design. CSS lets you give them what they need.</description>
	</item>
	<item>
		<title>AccessiBlog</title>
		<link>http://tc.eserver.org/23172.html</link>
		<guid>http://tc.eserver.org/23172.html</guid>
		<description>AccessiBlog was a weblog of articles and sites dealing with the topic of Web accessibility (though it is no longer updated).</description>
	</item>
	<item>
		<title>Joe Clark&apos;s Answers -- in Valid XHTML</title>
		<link>http://tc.eserver.org/23173.html</link>
		<guid>http://tc.eserver.org/23173.html</guid>
		<description>An extremely interesting but rather long read -- answers each question thoroughly and, there is plenty of discourse following the piece itself.</description>
	</item>
	<item>
		<title>Accessibility on the Mac</title>
		<link>http://tc.eserver.org/22946.html</link>
		<guid>http://tc.eserver.org/22946.html</guid>
		<description>It pains me to say that pretty much any computer user with a relevant disability ought to be using Windows, not a Mac.</description>
	</item>
	<item>
		<title>Facts and Opinion About Fahrner Image Replacement</title>
		<link>http://tc.eserver.org/20367.html</link>
		<guid>http://tc.eserver.org/20367.html</guid>
		<description>Fahrner Image Replacement and its analogues aim to combine the benefits of high design with the requirements of accessibility. But how well do these methods really work? Accessibility expert Joe Clark digs up much-needed empirical data on how FIR works (and doesn’t) in leading screen readers.</description>
	</item>
	<item>
		<title>The Web Is Like Canada</title>
		<link>http://tc.eserver.org/20251.html</link>
		<guid>http://tc.eserver.org/20251.html</guid>
		<description>Those who &apos;get&apos; the web create it. Those who do not get the web are put in charge. Joe Clark presents a vision for defending our web against their worst ideas.</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>
	<item>
		<title>Flash MX: Clarifying the Concept</title>
		<link>http://tc.eserver.org/18426.html</link>
		<guid>http://tc.eserver.org/18426.html</guid>
		<description>The new Flash MX authoring environment and the equally new Flash Player 6 solve a few accessibility problems.&#xD;&#xD;Screen reader compatibility is the first Macromedia access milestone. Screen readers—which, by the way, are not called “voice browsers” or “text readers”—are software that reads web pages, and anything else on your computer, out loud. (I’d show you a picture, but apart from a few uninteresting configuration screens, these programs have no overt visible form.)</description>
	</item>
	<item>
		<title>Flash Access: Unclear on the Concept</title>
		<link>http://tc.eserver.org/13621.html</link>
		<guid>http://tc.eserver.org/13621.html</guid>
		<description>In Christian theology, it doesn’t matter exactly when you accept Jesus Christ as your personal saviour. As long as you do it before you croak and ask forgiveness for your sins, you’re in like Flynn. This, apparently, is the Macromedia philosophy when it comes to accessibility. The company’s flagship product, Flash, is intrinsically inaccessible to anyone who cannot see properly and is very often inaccessible to a deaf or hard-of-hearing person. It’s also completely inaccessible on slow computers or any machine that lacks the Flash plug-in, rendering those viewers more functionally disabled than they actually are.</description>
	</item>
	<item>
		<title>All the Access Money Can Buy</title>
		<link>http://tc.eserver.org/13228.html</link>
		<guid>http://tc.eserver.org/13228.html</guid>
		<description>Just when you think online multimedia will never be truly accessible, someone proves you wrong. In BMW Films, Clark sees a tantalizing glimpse of a better web.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Clark,_Joe.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>