<?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"
	>
<channel>
	<title>Comments on: &#8220;alt&#8221; vs &#8220;title&#8221; tags for HTML images</title>
	<atom:link href="http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images/feed" rel="self" type="application/rss+xml" />
	<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images</link>
	<description>Paul Cook's blog</description>
	<pubDate>Fri, 18 May 2012 17:50:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Leesha</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-7411</link>
		<dc:creator>Leesha</dc:creator>
		<pubDate>Fri, 02 Mar 2007 04:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-7411</guid>
		<description>Are the addresses allowed in alt tags?</description>
		<content:encoded><![CDATA[<p>Are the addresses allowed in alt tags?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-2464</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Fri, 14 Jul 2006 13:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-2464</guid>
		<description>First of all  the main reason for alt and title tag i use em for is SEO. ALTs on images titles on text hyperlinks robot crawlers love it =) alt and title is never a bad idea for anyy site</description>
		<content:encoded><![CDATA[<p>First of all  the main reason for alt and title tag i use em for is SEO. ALTs on images titles on text hyperlinks robot crawlers love it =) alt and title is never a bad idea for anyy site</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paulcook</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-15</link>
		<dc:creator>paulcook</dc:creator>
		<pubDate>Sun, 23 Jan 2005 22:47:54 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-15</guid>
		<description>Yes, those menus are annoying! Perhaps the question that needs to be asked is, "How well would my site work with all of the bells and whistles turned off?" I think that the wonders of popups and flash and so on are great to make the site more interesting and to add additional hints, but if the basic use of the site requires them, then there are three problems: (1) It's hard to use -- cf. your menu comments above; and it's impossible for, say, blind people. (2) It's less likely to work on all browsers, with all security settings.

And (3), a meta-point: I think it adds to the danger in people getting caught up in using technology for the sake of it, rather than for any real reason. This makes the interface more confusing, because there's just too many options.

Ironically, I think my site actually fails the second point, and maybe the third too: my menus don't work without JavaScript, at all. And the reason they're there in that way was because I was wanting to try out some new technology. But in my defense, I have a disclaimer to all this on my homepage.</description>
		<content:encoded><![CDATA[<p>Yes, those menus are annoying! Perhaps the question that needs to be asked is, &#8220;How well would my site work with all of the bells and whistles turned off?&#8221; I think that the wonders of popups and flash and so on are great to make the site more interesting and to add additional hints, but if the basic use of the site requires them, then there are three problems: (1) It&#8217;s hard to use &#8212; cf. your menu comments above; and it&#8217;s impossible for, say, blind people. (2) It&#8217;s less likely to work on all browsers, with all security settings.</p>
<p>And (3), a meta-point: I think it adds to the danger in people getting caught up in using technology for the sake of it, rather than for any real reason. This makes the interface more confusing, because there&#8217;s just too many options.</p>
<p>Ironically, I think my site actually fails the second point, and maybe the third too: my menus don&#8217;t work without JavaScript, at all. And the reason they&#8217;re there in that way was because I was wanting to try out some new technology. But in my defense, I have a disclaimer to all this on my homepage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MDA</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-14</link>
		<dc:creator>MDA</dc:creator>
		<pubDate>Sat, 22 Jan 2005 22:07:54 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-14</guid>
		<description>I had a rather nice reply written out, but my thumb slipped;  I accidentally hit ^A followed by a space, and there is no undo feature.  Man am I pissed.

The gist:  Some of the most transient dynamic content on certain websites out there are the most in need of being made more static.  The example I gave was those javascript menus on many corporate sites that present submenus on mouseover.  You then get subsubmenus on mouseovering a submenu item, and so forth.  How many times has your mouse slipped and you've been forced to start all over at the top of the hierarchy.  This is not just a problem on the web, many layered menus like this have the same problem in seversl OSs out there (including OS X).  The solution is simple - keep the menus around on a click (such as your site does).

Anyway - the point of my now dead comment, and this should not be read as a pointed remark, was to say that dynamic content can be useful, but that more people need to think about whether that content is better served to the user statically (or where on the spectrum of... dynamicity... it should lie).</description>
		<content:encoded><![CDATA[<p>I had a rather nice reply written out, but my thumb slipped;  I accidentally hit ^A followed by a space, and there is no undo feature.  Man am I pissed.</p>
<p>The gist:  Some of the most transient dynamic content on certain websites out there are the most in need of being made more static.  The example I gave was those javascript menus on many corporate sites that present submenus on mouseover.  You then get subsubmenus on mouseovering a submenu item, and so forth.  How many times has your mouse slipped and you&#8217;ve been forced to start all over at the top of the hierarchy.  This is not just a problem on the web, many layered menus like this have the same problem in seversl OSs out there (including OS X).  The solution is simple - keep the menus around on a click (such as your site does).</p>
<p>Anyway - the point of my now dead comment, and this should not be read as a pointed remark, was to say that dynamic content can be useful, but that more people need to think about whether that content is better served to the user statically (or where on the spectrum of&#8230; dynamicity&#8230; it should lie).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paulcook</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-13</link>
		<dc:creator>paulcook</dc:creator>
		<pubDate>Sat, 22 Jan 2005 21:36:02 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-13</guid>
		<description>Hey, I agree entirely that the proper use of the tags is best for blind people. Once one "discovers" the title tag, the distinction is obvious, I think, and useful.

I do, however, think that there can be a use for tooltips. Consider the navigation buttons at the top of my site. Though I've not actually used tooltips, the text below serves the same function. It's not vital, but makes the site that little bit more navigable. Well, I think so anyway!</description>
		<content:encoded><![CDATA[<p>Hey, I agree entirely that the proper use of the tags is best for blind people. Once one &#8220;discovers&#8221; the title tag, the distinction is obvious, I think, and useful.</p>
<p>I do, however, think that there can be a use for tooltips. Consider the navigation buttons at the top of my site. Though I&#8217;ve not actually used tooltips, the text below serves the same function. It&#8217;s not vital, but makes the site that little bit more navigable. Well, I think so anyway!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MDA</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-12</link>
		<dc:creator>MDA</dc:creator>
		<pubDate>Fri, 21 Jan 2005 23:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-12</guid>
		<description>hehe - just realized the irony.</description>
		<content:encoded><![CDATA[<p>hehe - just realized the irony.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MDA</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-11</link>
		<dc:creator>MDA</dc:creator>
		<pubDate>Fri, 21 Jan 2005 22:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-11</guid>
		<description>Damn - can you fix those em tags for me?</description>
		<content:encoded><![CDATA[<p>Damn - can you fix those em tags for me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MDA</title>
		<link>http://langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-10</link>
		<dc:creator>MDA</dc:creator>
		<pubDate>Fri, 21 Jan 2005 22:30:03 +0000</pubDate>
		<guid isPermaLink="false">http://dev.langabi.name/blog/2005/01/21/alt-vs-title-tags-for-html-images#comment-10</guid>
		<description>You mean "to get up to standards level [full-stop]".  You were never there to begin with :)

It's not a bug - it's sloppy coding.  And likely the bane of many visually impared people, lynx users, cell-phone web browsers and the like.  Alt has a specific purpose: it defines what to display when the image can't be seen.  Using it for any other purpose has always been a terrible idea.  Who the hell wants a icon that says "send" on it to display a "send" tooltip when you hover over it?  Annoying.  If you can'y figure out what an image link does without having a tooltip, your site is designed poorly.  On the other hand, you definately need an alt tag of "send" for an send icon, so people who can't see images know what link to click (or you could just use a &lt;em&gt;real&lt;/em&gt; send &lt;em&gt;button&lt;/em&gt;).  That's why alts are alts and titles are titles.

All images should have alts (not that any at my site do, but certainly commercial sites should use them for everything), but very few images should have tooltips.  Why would you need them?  A lot of dynamic crap on web sites these days just makes things harder to use without presenting more information than an analogous static display.  But when you do need extra information to be associated with images (maybe photographs or equations or something), for the love of all that is beautiful and ergonomic, use title not alt.  You'll be making your site more accessible and less annoying.</description>
		<content:encoded><![CDATA[<p>You mean &#8220;to get up to standards level [full-stop]&#8220;.  You were never there to begin with :)</p>
<p>It&#8217;s not a bug - it&#8217;s sloppy coding.  And likely the bane of many visually impared people, lynx users, cell-phone web browsers and the like.  Alt has a specific purpose: it defines what to display when the image can&#8217;t be seen.  Using it for any other purpose has always been a terrible idea.  Who the hell wants a icon that says &#8220;send&#8221; on it to display a &#8220;send&#8221; tooltip when you hover over it?  Annoying.  If you can&#8217;y figure out what an image link does without having a tooltip, your site is designed poorly.  On the other hand, you definately need an alt tag of &#8220;send&#8221; for an send icon, so people who can&#8217;t see images know what link to click (or you could just use a <em>real</em> send <em>button</em>).  That&#8217;s why alts are alts and titles are titles.</p>
<p>All images should have alts (not that any at my site do, but certainly commercial sites should use them for everything), but very few images should have tooltips.  Why would you need them?  A lot of dynamic crap on web sites these days just makes things harder to use without presenting more information than an analogous static display.  But when you do need extra information to be associated with images (maybe photographs or equations or something), for the love of all that is beautiful and ergonomic, use title not alt.  You&#8217;ll be making your site more accessible and less annoying.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

