<?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/"
	>

<channel>
	<title>Accessibility Tips &#187; text-equivalent</title>
	<atom:link href="http://accessibilitytips.com/tag/text-equivalent/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessibilitytips.com</link>
	<description>A collection of tips, guidance and practical suggestions in developing accessible websites</description>
	<lastBuildDate>Sat, 02 May 2009 05:07:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Punctuating text-equivalents</title>
		<link>http://accessibilitytips.com/2009/01/02/punctuating-text-equivalents/</link>
		<comments>http://accessibilitytips.com/2009/01/02/punctuating-text-equivalents/#comments</comments>
		<pubDate>Fri, 02 Jan 2009 19:09:33 +0000</pubDate>
		<dc:creator>Isofarro</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[alt]]></category>
		<category><![CDATA[alt attribute]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[fallback]]></category>
		<category><![CDATA[image]]></category>
		<category><![CDATA[images]]></category>
		<category><![CDATA[meaning]]></category>
		<category><![CDATA[null alt]]></category>
		<category><![CDATA[screenreaders]]></category>
		<category><![CDATA[text]]></category>
		<category><![CDATA[text-equivalent]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=22</guid>
		<description><![CDATA[When we have an image on a web page and that image conveys content, then we know it is important to provide a text equivalent of the content that image offers. The most typical (but not only) way of doing this is to add the text equivalent content in an alt attribute on that image. [...]]]></description>
			<content:encoded><![CDATA[<p>When we have an image on a web page and that image conveys content, then we know it is important to provide a text equivalent of the content that image offers. The most typical (but not only) way of doing this is to add the text equivalent content in an <code>alt</code> attribute on that image. The text content of this attribute should convey the equivalent information that the image contains.</p>
<h3>Altered meaning</h3>
<p>When a screen reader user, for example, reads the page all of the images are replaced with their text equivalents, and the resulting block of text is what the visitor gets. The two conceptually independent sources of text are merged into one block.</p>
<p>We need to consider the state of the merged content when that happens. Is the content still accurate, is the meaning and intention still clear.</p>
<p>When applying text equivalents to images we sometimes fail to consider how this new text will change the existing adjacent text content. The implications of this are:</p>
<ul>
<li>the content is not understandable</li>
<li>the content becomes unintelligible</li>
<li>the content changes meaning</li>
<li>the content loses it&#8217;s accuracy</li>
<li>the content becomes invalid or incorrect</li>
<li>the content conveys a message that was not intended</li>
</ul>
<h3>Unintentional humour</h3>
<p>Sometimes the end result is humourous. The late Dr. Alan Flavell in his notes on <a href="http://web.archive.org/web/20060518005758/http://ppewww.ph.gla.ac.uk/~flavell/alt/alt-text.html#howlers">alt attribute howlers</a> noted a real world example of two adjacent images, one was a picture of the page author in a canoe, and the other was a picture of a herd of buffalo. Two images of what interested the page author, and both with decent text equivalents. Unfortunately, in context, the block of text became: <q>Photo of a buffaloes in the water canoeing</q>, which was not quite the intended meaning.</p>
<p>Some simple punctuation would have avoided this unintentional joke.</p>
<h3>Punctuating or extra markup</h3>
<p>For this reason it is important to consider punctuating an image&#8217;s text-equivalent. A well-thought out comma or full stop, or parenthesis may be enough to protect the meaning and intention of existing text content from being changed when an image&#8217;s text equivalent is inserted where an image used to be.</p>
<p>If the text-equivalent can&#8217;t be written in a way that doesn&#8217;t hinder the meaning of the text content around it, then we need to consider moving the text-equivalent elsewhere; whether that means moving the image markup somewhere else, or leaving the image in place, and moving the text-equivalent to a more suitable spot (by using a null <code>alt</code> attribute and then inserting the text as a block of markup in the page).</p>
]]></content:encoded>
			<wfw:commentRss>http://accessibilitytips.com/2009/01/02/punctuating-text-equivalents/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

