<?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: Avoiding redundant title attributes</title>
	<atom:link href="http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/</link>
	<description>A collection of tips, guidance and practical suggestions in developing accessible websites</description>
	<lastBuildDate>Thu, 08 Sep 2011 19:48:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: SFCite &#124; Blog &#124; 25 Ways to Make Your WordPress Website More Accessible</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-312</link>
		<dc:creator>SFCite &#124; Blog &#124; 25 Ways to Make Your WordPress Website More Accessible</dc:creator>
		<pubDate>Thu, 27 Jan 2011 18:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-312</guid>
		<description>[...] Title attributes are often misused. Here’s a good example: [...]</description>
		<content:encoded><![CDATA[<p>[...] Title attributes are often misused. Here’s a good example: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anup</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-151</link>
		<dc:creator>Anup</dc:creator>
		<pubDate>Sat, 25 Apr 2009 14:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-151</guid>
		<description>Good post.

Regarding SEO benefits from using title attributes: my understanding and experience is that it has either no bearing on SEO or very little.

Although these two are slightly old posts now, they provide further info:

1) A small note about title tooltips happens to be mentioned here:
http://www.onenaught.com/posts/33/seo-for-sake-of-seo-misses-the-point

2) Includes a list of top factors that prominent SEO experts agree were important in 2007 and compares that to 2005 (as years go on, technical things become less and less of a factor)
http://www.onenaught.com/posts/30/explaining-natural-seo-search-engine-ranking-vs-indexing</description>
		<content:encoded><![CDATA[<p>Good post.</p>
<p>Regarding SEO benefits from using title attributes: my understanding and experience is that it has either no bearing on SEO or very little.</p>
<p>Although these two are slightly old posts now, they provide further info:</p>
<p>1) A small note about title tooltips happens to be mentioned here:<br />
<a href="http://www.onenaught.com/posts/33/seo-for-sake-of-seo-misses-the-point" rel="nofollow">http://www.onenaught.com/posts/33/seo-for-sake-of-seo-misses-the-point</a></p>
<p>2) Includes a list of top factors that prominent SEO experts agree were important in 2007 and compares that to 2005 (as years go on, technical things become less and less of a factor)<br />
<a href="http://www.onenaught.com/posts/30/explaining-natural-seo-search-engine-ranking-vs-indexing" rel="nofollow">http://www.onenaught.com/posts/30/explaining-natural-seo-search-engine-ranking-vs-indexing</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isofarro</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-106</link>
		<dc:creator>Isofarro</dc:creator>
		<pubDate>Mon, 02 Feb 2009 20:34:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-106</guid>
		<description>Peter, no. Web accessibility is making content perceivable, operable, understandable and robust for people with disabilities. There are benefits for non-disabled people, but this is a side-effect of web accessibility, not the primary purpose. It is fairly important that the distinction is understood.</description>
		<content:encoded><![CDATA[<p>Peter, no. Web accessibility is making content perceivable, operable, understandable and robust for people with disabilities. There are benefits for non-disabled people, but this is a side-effect of web accessibility, not the primary purpose. It is fairly important that the distinction is understood.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isofarro</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-105</link>
		<dc:creator>Isofarro</dc:creator>
		<pubDate>Mon, 02 Feb 2009 20:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-105</guid>
		<description>Scott, yes, if the appropriate text-equivalent you put into an alt attribute is content that already exists on the page in a text format, then the alt attribute is essentially redundant and it can be a null alt instead (alt=&quot;&quot;). The one exception to this is when the image is the only thing inside an anchor link - since then a situation will be created where there&#039;s no link text, and the screen reader will attempt to divine something readable from the image source URL.</description>
		<content:encoded><![CDATA[<p>Scott, yes, if the appropriate text-equivalent you put into an alt attribute is content that already exists on the page in a text format, then the alt attribute is essentially redundant and it can be a null alt instead (alt=&#8221;"). The one exception to this is when the image is the only thing inside an anchor link &#8211; since then a situation will be created where there&#8217;s no link text, and the screen reader will attempt to divine something readable from the image source URL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Stevens</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-104</link>
		<dc:creator>Peter Stevens</dc:creator>
		<pubDate>Sun, 22 Jun 2008 16:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-104</guid>
		<description>This is an interesting debate, and I hope you&#039;ll permit me to make the following comment. The view being propounded here is that accessibility design is somehow _only_ for disabled people - can we perish this? My view, even if it seems outrageous, is that designing for accessibility enriches the web experience for _all_ visitors, regardless of disAbility!

So, I&#039;m not sure that I agree with the redundancy of the title attribute for hyperlinks - quite the reverse! Quite apart from the SEO aspects, which are fairly important, giving any visitor a helpful text tooltip of where the link is likely to take them is the main bonus. In Opera for example, links without the title attribute still display a tooltip, but with only an often unintelligible URL. Much better to prefix that with a human readable indicator - surely?

As far as screen readers are concerned, my belief is that users are able to configure how the software deals with the absence, or not, of link title attributes

So far, I&#039;m not sufficiently convinced that ommiting titles from links is a good thing - so I&#039;ll be leaving them in place.</description>
		<content:encoded><![CDATA[<p>This is an interesting debate, and I hope you&#8217;ll permit me to make the following comment. The view being propounded here is that accessibility design is somehow _only_ for disabled people &#8211; can we perish this? My view, even if it seems outrageous, is that designing for accessibility enriches the web experience for _all_ visitors, regardless of disAbility!</p>
<p>So, I&#8217;m not sure that I agree with the redundancy of the title attribute for hyperlinks &#8211; quite the reverse! Quite apart from the SEO aspects, which are fairly important, giving any visitor a helpful text tooltip of where the link is likely to take them is the main bonus. In Opera for example, links without the title attribute still display a tooltip, but with only an often unintelligible URL. Much better to prefix that with a human readable indicator &#8211; surely?</p>
<p>As far as screen readers are concerned, my belief is that users are able to configure how the software deals with the absence, or not, of link title attributes</p>
<p>So far, I&#8217;m not sufficiently convinced that ommiting titles from links is a good thing &#8211; so I&#8217;ll be leaving them in place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Lenger</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-103</link>
		<dc:creator>Scott Lenger</dc:creator>
		<pubDate>Thu, 19 Jun 2008 21:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-103</guid>
		<description>Confirmed what I had assumed. Would the same logic:

&quot;title attribute being used to provide the same information that&#039;s already available and accessible.&quot;

work for the img alt attribute, assuming a description already exists within the page content?</description>
		<content:encoded><![CDATA[<p>Confirmed what I had assumed. Would the same logic:</p>
<p>&#8220;title attribute being used to provide the same information that&#8217;s already available and accessible.&#8221;</p>
<p>work for the img alt attribute, assuming a description already exists within the page content?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isofarro</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-102</link>
		<dc:creator>Isofarro</dc:creator>
		<pubDate>Mon, 12 May 2008 14:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-102</guid>
		<description>Andre asks: &quot;What about microformats? Can´t we use microformats to improve accessibility?&quot;

As they currently stand, microformats do nothing to improve the accessibility of a page. In two particular cases, the abbr datetime pattern and its geo-location relative, the content added in the name of microformats actually creates an accessibility barrier to screen reader users who chose to take advantage of marked up abbreviations.</description>
		<content:encoded><![CDATA[<p>Andre asks: &#8220;What about microformats? Can´t we use microformats to improve accessibility?&#8221;</p>
<p>As they currently stand, microformats do nothing to improve the accessibility of a page. In two particular cases, the abbr datetime pattern and its geo-location relative, the content added in the name of microformats actually creates an accessibility barrier to screen reader users who chose to take advantage of marked up abbreviations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andre</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-101</link>
		<dc:creator>Andre</dc:creator>
		<pubDate>Wed, 07 May 2008 16:21:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-101</guid>
		<description>Hi, well, from an SEO perspective the title-attribute is very useful. It provides machine-readable content that fits into the context (both: context of the page and context of the linked site). It´s one of the most overlooked possibilities in onPge-SEO.

So when I have to decide between SEO an accessibility, I choose SEO, of course. What about microformats? Can´t we use microformats to improve accessibility?</description>
		<content:encoded><![CDATA[<p>Hi, well, from an SEO perspective the title-attribute is very useful. It provides machine-readable content that fits into the context (both: context of the page and context of the linked site). It´s one of the most overlooked possibilities in onPge-SEO.</p>
<p>So when I have to decide between SEO an accessibility, I choose SEO, of course. What about microformats? Can´t we use microformats to improve accessibility?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark McKay</title>
		<link>http://accessibilitytips.com/2008/04/14/avoiding-redundant-title-attributes/comment-page-1/#comment-100</link>
		<dc:creator>Mark McKay</dc:creator>
		<pubDate>Fri, 18 Apr 2008 14:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=20#comment-100</guid>
		<description>Great post!

Another point about titles is that by default screen readers like Jaws don&#039;t read them. You have to enable this feature. Which most people never do. So if a designer uses inappropriate link text and tries to fix this by using a title most users will never see/hear it.

Also different browsers display differing amounts of the title text. So you can&#039;t even be sure that all of the text you put in a title will be seen by a user.

Titles have their place but I think at the present time a lot of people are over/miss using them.

Mark</description>
		<content:encoded><![CDATA[<p>Great post!</p>
<p>Another point about titles is that by default screen readers like Jaws don&#8217;t read them. You have to enable this feature. Which most people never do. So if a designer uses inappropriate link text and tries to fix this by using a title most users will never see/hear it.</p>
<p>Also different browsers display differing amounts of the title text. So you can&#8217;t even be sure that all of the text you put in a title will be seen by a user.</p>
<p>Titles have their place but I think at the present time a lot of people are over/miss using them.</p>
<p>Mark</p>
]]></content:encoded>
	</item>
</channel>
</rss>

