<?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: Use Alt-Tags for Image Optimization</title>
	<atom:link href="http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html</link>
	<description>Web Marketing Strategies for Small Business</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:51:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: john e brandt</title>
		<link>http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html/comment-page-1#comment-243</link>
		<dc:creator>john e brandt</dc:creator>
		<pubDate>Tue, 18 Nov 2008 17:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html#comment-243</guid>
		<description>&lt;p&gt;Interesting, but has some flaws. You might want to scan the dozens (hundreds?) of comments made after the video clip was posted in Dec 2007. While I understand that many web designers are more interested in SEO than accessibility, you will see that this mindset is challenged in the comments. Screen reader users NEED to have accurate ALT attributes particularly if the image is of text (e.g. part of a logo or header). But very often the image with a long, highly descriptive ALT attribute may actually detract and/or confuse the screen reader user. The screen reader will read the ALT information in the same sentence (based upon its location in the HTML) and this may be totally irrelevant to the topic of the page. So issues related to semantics are also important in choosing the proper ALT text. I know this sounds like a rant...probably is. But this is a complicated issue and I have been wrestling with for some time. And I often choose to encourage designers to choose the NULL ALT (ALT=&quot;&quot;) so as to NOT confuse the screen reader user. Other thoughts?&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Interesting, but has some flaws. You might want to scan the dozens (hundreds?) of comments made after the video clip was posted in Dec 2007. While I understand that many web designers are more interested in SEO than accessibility, you will see that this mindset is challenged in the comments. Screen reader users NEED to have accurate ALT attributes particularly if the image is of text (e.g. part of a logo or header). But very often the image with a long, highly descriptive ALT attribute may actually detract and/or confuse the screen reader user. The screen reader will read the ALT information in the same sentence (based upon its location in the HTML) and this may be totally irrelevant to the topic of the page. So issues related to semantics are also important in choosing the proper ALT text. I know this sounds like a rant&#8230;probably is. But this is a complicated issue and I have been wrestling with for some time. And I often choose to encourage designers to choose the NULL ALT (ALT=&quot;&quot;) so as to NOT confuse the screen reader user. Other thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john e brandt</title>
		<link>http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html/comment-page-1#comment-8095</link>
		<dc:creator>john e brandt</dc:creator>
		<pubDate>Tue, 18 Nov 2008 17:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html#comment-8095</guid>
		<description>Interesting, but has some flaws. You might want to scan the dozens (hundreds?) of comments made after the video clip was posted in Dec 2007. While I understand that many web designers are more interested in SEO than accessibility, you will see that this mindset is challenged in the comments. Screen reader users NEED to have accurate ALT attributes particularly if the image is of text (e.g. part of a logo or header). But very often the image with a long, highly descriptive ALT attribute may actually detract and/or confuse the screen reader user. The screen reader will read the ALT information in the same sentence (based upon its location in the HTML) and this may be totally irrelevant to the topic of the page. So issues related to semantics are also important in choosing the proper ALT text. I know this sounds like a rant...probably is. But this is a complicated issue and I have been wrestling with for some time. And I often choose to encourage designers to choose the NULL ALT (ALT=&quot;&quot;) so as to NOT confuse the screen reader user. Other thoughts?</description>
		<content:encoded><![CDATA[<p>Interesting, but has some flaws. You might want to scan the dozens (hundreds?) of comments made after the video clip was posted in Dec 2007. While I understand that many web designers are more interested in SEO than accessibility, you will see that this mindset is challenged in the comments. Screen reader users NEED to have accurate ALT attributes particularly if the image is of text (e.g. part of a logo or header). But very often the image with a long, highly descriptive ALT attribute may actually detract and/or confuse the screen reader user. The screen reader will read the ALT information in the same sentence (based upon its location in the HTML) and this may be totally irrelevant to the topic of the page. So issues related to semantics are also important in choosing the proper ALT text. I know this sounds like a rant&#8230;probably is. But this is a complicated issue and I have been wrestling with for some time. And I often choose to encourage designers to choose the NULL ALT (ALT=&quot;&quot;) so as to NOT confuse the screen reader user. Other thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john e brandt</title>
		<link>http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html/comment-page-1#comment-8096</link>
		<dc:creator>john e brandt</dc:creator>
		<pubDate>Tue, 18 Nov 2008 17:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.flyteblog.com/flyte/2008/11/use-alt-tags-for-image-optimization.html#comment-8096</guid>
		<description>Interesting, but has some flaws. You might want to scan the dozens (hundreds?) of comments made after the video clip was posted in Dec 2007. While I understand that many web designers are more interested in SEO than accessibility, you will see that this mindset is challenged in the comments. Screen reader users NEED to have accurate ALT attributes particularly if the image is of text (e.g. part of a logo or header). But very often the image with a long, highly descriptive ALT attribute may actually detract and/or confuse the screen reader user. The screen reader will read the ALT information in the same sentence (based upon its location in the HTML) and this may be totally irrelevant to the topic of the page. So issues related to semantics are also important in choosing the proper ALT text. I know this sounds like a rant...probably is. But this is a complicated issue and I have been wrestling with for some time. And I often choose to encourage designers to choose the NULL ALT (ALT=&quot;&quot;) so as to NOT confuse the screen reader user. Other thoughts?</description>
		<content:encoded><![CDATA[<p>Interesting, but has some flaws. You might want to scan the dozens (hundreds?) of comments made after the video clip was posted in Dec 2007. While I understand that many web designers are more interested in SEO than accessibility, you will see that this mindset is challenged in the comments. Screen reader users NEED to have accurate ALT attributes particularly if the image is of text (e.g. part of a logo or header). But very often the image with a long, highly descriptive ALT attribute may actually detract and/or confuse the screen reader user. The screen reader will read the ALT information in the same sentence (based upon its location in the HTML) and this may be totally irrelevant to the topic of the page. So issues related to semantics are also important in choosing the proper ALT text. I know this sounds like a rant&#8230;probably is. But this is a complicated issue and I have been wrestling with for some time. And I often choose to encourage designers to choose the NULL ALT (ALT=&quot;&quot;) so as to NOT confuse the screen reader user. Other thoughts?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

