<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">

<channel>
	<title>Curb Cut &#187; Images</title>
	<atom:link href="http://curbcut.net/category/format/images/feed/" rel="self" type="application/rss+xml" />
	<link>http://curbcut.net</link>
	<description>open and accessible</description>
	<lastBuildDate>Sat, 07 Jan 2012 16:24:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<cloud domain='curbcut.net' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<creativeCommons:license>http://creativecommons.org/licenses/by/3.0/us/</creativeCommons:license>		<item>
		<title>Avoiding the Gray Areas</title>
		<link>http://curbcut.net/accessibility/avoiding-the-gray-areas/</link>
		<comments>http://curbcut.net/accessibility/avoiding-the-gray-areas/#comments</comments>
		<pubDate>Sat, 08 Mar 2008 18:48:37 +0000</pubDate>
		<dc:creator>Christopher Phillips</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Images]]></category>

		<guid isPermaLink="false">http://curbcut.net/accessibility/avoiding-the-gray-areas/</guid>
		<description><![CDATA[I just caught the last of Shawn Henry’s SXSW panel. Key takeway– there are white areas of things that are good to do for accessibility and black areas of things that are bad for accessibility– avoid worrying about the gray area in the middle. She mentioned the ability of web accessibility experts to endlessly debate [...]]]></description>
			<content:encoded><![CDATA[<p>I just caught the last of <a href="http://2008.sxsw.com/interactive/programming/panels_schedule/?action=show&#038;id=IAP060358">Shawn Henry’s SXSW panel</a>. Key takeway– there are white areas of things that are good to do for accessibility and black areas of things that are bad for accessibility– avoid worrying about the gray area in the middle. She mentioned the ability of web accessibility experts to endlessly debate the ins and outs of alt text. For example:</p>
<ul>
<li><a href="http://blogs.cetis.ac.uk/accessibility/2007/02/12/should-alt-text-be-used-to-paint-a-thousand-words/">Should alt text be used to paint a thousand words?</a></li>
<li><a href="http://www.hixie.ch/advocacy/alttext">Mini-FAQ about the alternate text of images</a></li>
<li><a href="http://curbcut.net/standards/alt-text-less-can-be-more/">Alt Text, Less Can be More</a></li>
<li><a href="http://www.webaim.org/search/?q=%22alt+text%22&#038;scope=archives">“Alt Text” search on WebAIM Discussion List</a></li>
<li><a href="http://www.w3.org/Search/Mail/Public/search?type-index=w3c-wai-ig&#038;index-type=t&#038;keywords=%22alt+text%22&#038;search=Search">Search fo “alt text” on The Web Accessibility Initiative Interest Group (WAI IG) mailing list</a></li>
</ul>
<p>These discussions are helpful and essential for establishing best practices. However, these discussions are harmful to the extent that a developer becomes tied up arguing about “gray areas” instead of building accessible content.</p>
]]></content:encoded>
			<wfw:commentRss>http://curbcut.net/accessibility/avoiding-the-gray-areas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.312 seconds -->

