<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Building Accessible Websites</title>
	<atom:link href="http://www.website-domain-name.com/books/building-accessible-websites/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.website-domain-name.com/books/building-accessible-websites/</link>
	<description>Learn More About Buying Domain Names</description>
	<lastBuildDate>Wed, 19 May 2010 08:53:17 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Xanto</title>
		<link>http://www.website-domain-name.com/books/building-accessible-websites/comment-page-1/#comment-1655</link>
		<dc:creator>Xanto</dc:creator>
		<pubDate>Wed, 18 Nov 2009 02:46:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.website-domain-name.com/books/building-accessible-websites/#comment-1655</guid>
		<description>

Written in 2002, this book is still considered the gold standard in web accessibility.  I have no idea why.  What Joe Clark has accomplished here is to spread about 20 pages of good accessibility information across a 400 page miasma.  Most web designers don&#039;t care about the history of captioning and transcription systems--we just want the facts, man.  What should we do, and what should we avoid.  Best practices.  Etc.  That info is in here, but you have to cut a swath through the verbosity to find much of it.  Or just read the last page of each chapter, which summarizes the previous 40-odd pages in six or less sentences.  Save yourself the price of the book and scan through the entire text of the book online.  In the end, Building Accessible Websites is an inaccessible read.  &#13;</description>
		<content:encoded><![CDATA[<p>Written in 2002, this book is still considered the gold standard in web accessibility.  I have no idea why.  What Joe Clark has accomplished here is to spread about 20 pages of good accessibility information across a 400 page miasma.  Most web designers don&#8217;t care about the history of captioning and transcription systems&#8211;we just want the facts, man.  What should we do, and what should we avoid.  Best practices.  Etc.  That info is in here, but you have to cut a swath through the verbosity to find much of it.  Or just read the last page of each chapter, which summarizes the previous 40-odd pages in six or less sentences.  Save yourself the price of the book and scan through the entire text of the book online.  In the end, Building Accessible Websites is an inaccessible read.  &#13;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sabine</title>
		<link>http://www.website-domain-name.com/books/building-accessible-websites/comment-page-1/#comment-1654</link>
		<dc:creator>Sabine</dc:creator>
		<pubDate>Wed, 18 Nov 2009 01:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.website-domain-name.com/books/building-accessible-websites/#comment-1654</guid>
		<description>

Am I the only one who finds the cover art to be a bit. . .  questionable?
      </description>
		<content:encoded><![CDATA[<p>Am I the only one who finds the cover art to be a bit. . .  questionable?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shlomo</title>
		<link>http://www.website-domain-name.com/books/building-accessible-websites/comment-page-1/#comment-1653</link>
		<dc:creator>Shlomo</dc:creator>
		<pubDate>Tue, 17 Nov 2009 23:27:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.website-domain-name.com/books/building-accessible-websites/#comment-1653</guid>
		<description>

First of all, I would like commend Mr.  Clark for addressing this topic at all.   Accessibility is an important in computer development. While the content seems to be accurate, and quite detailed to the point that you could use the information in the book to actually build a site with it, the writing is so poor and very difficult to read.   Mr.   Clark needs to throw away his thesaurus and hire an editor.   He would be better off delivering his message in a clear and concise manner, and spend less time writing in a very &quot;fancy&quot; way that would be better suited for thesis papers rather than a book targeted towards the masses.   This heavy style of writing makes it a difficult book to digest while riding the subway. Pretentious - the one word I would use to describe the overall style of writing.   This really put me off as a reader, making the content even more difficult to absorb.   (In one case, the author actually explains his choice of word, &quot;indention&quot; as opposed to the more commonly used &quot;indentation&quot;.   His explanation seemed to imply that everyone who uses &quot;indentation&quot; is clearly *wrong*; two online dictionaries confirmed that &quot;indentation&quot; could have been used. )  Of course, my opinion that the writing of this book is pretentious could also come from actually having met the author. Read this book only if you really have the time to struggle through all his big words to get at the meaning behind them. 
      </description>
		<content:encoded><![CDATA[<p>First of all, I would like commend Mr.  Clark for addressing this topic at all.   Accessibility is an important in computer development. While the content seems to be accurate, and quite detailed to the point that you could use the information in the book to actually build a site with it, the writing is so poor and very difficult to read.   Mr.   Clark needs to throw away his thesaurus and hire an editor.   He would be better off delivering his message in a clear and concise manner, and spend less time writing in a very &#8220;fancy&#8221; way that would be better suited for thesis papers rather than a book targeted towards the masses.   This heavy style of writing makes it a difficult book to digest while riding the subway. Pretentious &#8211; the one word I would use to describe the overall style of writing.   This really put me off as a reader, making the content even more difficult to absorb.   (In one case, the author actually explains his choice of word, &#8220;indention&#8221; as opposed to the more commonly used &#8220;indentation&#8221;.   His explanation seemed to imply that everyone who uses &#8220;indentation&#8221; is clearly *wrong*; two online dictionaries confirmed that &#8220;indentation&#8221; could have been used. )  Of course, my opinion that the writing of this book is pretentious could also come from actually having met the author. Read this book only if you really have the time to struggle through all his big words to get at the meaning behind them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

