<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for Access Matters</title>
	<link>http://www.access-matters.com</link>
	<description>Seeking Best Accessibility Practices</description>
	<pubDate>Sun, 14 Mar 2010 17:57:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>Comment on Today&#8217;s AJAX and DHTML Best Practices by tatil otelleri</title>
		<link>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-184846</link>
		<pubDate>Sat, 06 Mar 2010 13:51:35 +0000</pubDate>
		<guid>http://www.access-matters.com/2006/10/09/todays-ajax-and-dhtml-best-practices/#comment-184846</guid>
					<description>Access Matters » Blog Archive » Today’s AJAX and DHTML Best Practices (tags: accessibility AJAX javascript webdesign)</description>
		<content:encoded><![CDATA[<p>Access Matters » Blog Archive » Today’s AJAX and DHTML Best Practices (tags: accessibility AJAX javascript webdesign)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Thanks for All the Fish by Jon Gibbins</title>
		<link>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183057</link>
		<pubDate>Tue, 02 Feb 2010 11:45:25 +0000</pubDate>
		<guid>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183057</guid>
					<description>Bob, I think it's only fair that you get a bunch of thanks yous in return! All the very best with your re-retirement!</description>
		<content:encoded><![CDATA[<p>Bob, I think it&#8217;s only fair that you get a bunch of thanks yous in return! All the very best with your re-retirement!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Thanks for All the Fish by Bob Easton</title>
		<link>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183055</link>
		<pubDate>Sun, 31 Jan 2010 22:14:45 +0000</pubDate>
		<guid>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183055</guid>
					<description>What's this with the sympathy? I'm not dead! 

In fact, it's a lot of fun being retired and doing all the things there was no time for a few years ago. No sympathy needed.

No, the content won't be posted elsewhere. It disappears. Most is testing on such old versions of screen readers that it's now obsolete.

Thanks anyway for the well intended greetings Ruth. All the best...</description>
		<content:encoded><![CDATA[<p>What&#8217;s this with the sympathy? I&#8217;m not dead! </p>
<p>In fact, it&#8217;s a lot of fun being retired and doing all the things there was no time for a few years ago. No sympathy needed.</p>
<p>No, the content won&#8217;t be posted elsewhere. It disappears. Most is testing on such old versions of screen readers that it&#8217;s now obsolete.</p>
<p>Thanks anyway for the well intended greetings Ruth. All the best&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Thanks for All the Fish by Ruth Ellison</title>
		<link>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183054</link>
		<pubDate>Sun, 31 Jan 2010 21:00:44 +0000</pubDate>
		<guid>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183054</guid>
					<description>Sorry to hear about that but thanks for the interesting articles. All the best with the retirement!

Cheers,
Ruth

PS: Will the content here be moved to another location when the domain lapses?</description>
		<content:encoded><![CDATA[<p>Sorry to hear about that but thanks for the interesting articles. All the best with the retirement!</p>
<p>Cheers,<br />
Ruth</p>
<p>PS: Will the content here be moved to another location when the domain lapses?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Thanks for All the Fish by Bob Easton</title>
		<link>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183053</link>
		<pubDate>Sun, 31 Jan 2010 10:42:57 +0000</pubDate>
		<guid>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183053</guid>
					<description>No need to be sorry Thierry; I'm having a fine time.  I have always enjoyed watching how you wrestle with and solve problems while maintaining great semantic value. You're one of the people I thank.

Keep having fun.</description>
		<content:encoded><![CDATA[<p>No need to be sorry Thierry; I&#8217;m having a fine time.  I have always enjoyed watching how you wrestle with and solve problems while maintaining great semantic value. You&#8217;re one of the people I thank.</p>
<p>Keep having fun.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Thanks for All the Fish by Thierry Koblentz</title>
		<link>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183052</link>
		<pubDate>Sun, 31 Jan 2010 04:19:50 +0000</pubDate>
		<guid>http://www.access-matters.com/2010/01/29/thanks-for-all-the-fish/#comment-183052</guid>
					<description>Sorry to hear that...
You do not know, but you're the one who triggered my interest for Accessibility many years ago.
Good luck with your future endeavors,
Thierry</description>
		<content:encoded><![CDATA[<p>Sorry to hear that&#8230;<br />
You do not know, but you&#8217;re the one who triggered my interest for Accessibility many years ago.<br />
Good luck with your future endeavors,<br />
Thierry
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Summary of Results for JavaScript - Part 1: Navigating links by Chris</title>
		<link>http://www.access-matters.com/2005/09/15/summary-of-results-for-javascript-part-1-navigating-links/#comment-183030</link>
		<pubDate>Fri, 04 Dec 2009 20:32:27 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/09/15/summary-of-results-for-javascript-part-1-navigating-links/#comment-183030</guid>
					<description>Bit late to this, but those results are pretty handy, thanks for making the effort!</description>
		<content:encoded><![CDATA[<p>Bit late to this, but those results are pretty handy, thanks for making the effort!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Clarifying ALT Text for WordPress Bloggers and Developers by alan &#124; Stooryduster</title>
		<link>http://www.access-matters.com/2009/09/29/clarifying-alt-text-for-wordpress-bloggers-and-developers/#comment-183023</link>
		<pubDate>Tue, 03 Nov 2009 00:34:54 +0000</pubDate>
		<guid>http://www.access-matters.com/2009/09/29/clarifying-alt-text-for-wordpress-bloggers-and-developers/#comment-183023</guid>
					<description>Thanks for the reply I'm still hacking my way through the jungle. I'll post the url once I have the site working to my satisfaction.

Cheers</description>
		<content:encoded><![CDATA[<p>Thanks for the reply I&#8217;m still hacking my way through the jungle. I&#8217;ll post the url once I have the site working to my satisfaction.</p>
<p>Cheers
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Clarifying ALT Text for WordPress Bloggers and Developers by Bob Easton</title>
		<link>http://www.access-matters.com/2009/09/29/clarifying-alt-text-for-wordpress-bloggers-and-developers/#comment-183021</link>
		<pubDate>Sat, 31 Oct 2009 14:11:50 +0000</pubDate>
		<guid>http://www.access-matters.com/2009/09/29/clarifying-alt-text-for-wordpress-bloggers-and-developers/#comment-183021</guid>
					<description>Good for you; trying to be sensible about accessibility.

Here's a suggestion for you. For the blog theme, editing the PHP is OK. For images that you add as posts, you can have your cake and eat it too. Here's how.  After adding an image to a post, (still in the post editor), click on the image and hit the Edit link. You will find several tabs. On one you can change the "Title" to be the text you want to appear on hover. On the Advanced tab, you can change the Alternate text. A lot of people duplicate this text, and that is minimally OK. It's better to have each be suited to its purpose though. Most blind people configure their screen readers to not announce title text because of the repetition. That reduces annoyance and works very well for sites that have really good alternative text.

Thanks for stopping by, and for putting extra effort into accessibility.</description>
		<content:encoded><![CDATA[<p>Good for you; trying to be sensible about accessibility.</p>
<p>Here&#8217;s a suggestion for you. For the blog theme, editing the PHP is OK. For images that you add as posts, you can have your cake and eat it too. Here&#8217;s how.  After adding an image to a post, (still in the post editor), click on the image and hit the Edit link. You will find several tabs. On one you can change the &#8220;Title&#8221; to be the text you want to appear on hover. On the Advanced tab, you can change the Alternate text. A lot of people duplicate this text, and that is minimally OK. It&#8217;s better to have each be suited to its purpose though. Most blind people configure their screen readers to not announce title text because of the repetition. That reduces annoyance and works very well for sites that have really good alternative text.</p>
<p>Thanks for stopping by, and for putting extra effort into accessibility.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Clarifying ALT Text for WordPress Bloggers and Developers by alan &#124; Stooryduster</title>
		<link>http://www.access-matters.com/2009/09/29/clarifying-alt-text-for-wordpress-bloggers-and-developers/#comment-183020</link>
		<pubDate>Sat, 31 Oct 2009 10:38:11 +0000</pubDate>
		<guid>http://www.access-matters.com/2009/09/29/clarifying-alt-text-for-wordpress-bloggers-and-developers/#comment-183020</guid>
					<description>Thankyou. I'm about to use Comicpress as a theme for my cartoon site and was blaming the theme for the misuse of the alt attribute. 

Comicpress uses the title attribute as a deliberate hovertext element of the theme and the name of the file as alt text. Unfortunately the simplest solution for me was to add my alternative text to the title field and hack the php code to make the alt attribute also use the same data that is for the title attribute.

Now I have a dilemma. The hover text adds value for sighted people just as the alt text adds value for the blind or partially sighted but using both as you say is irritating for those using accessibility devices.

Any thoughts? Should I be 'democratic' and go with what will be the majority audience? Would the one's using screen readers be understanding?

Some think it perverse to add accessibility features to what is a visual web site (cartoons) but I like the whole idea that the web is multi layered. If you can communicate an idea, story or point of view visually effectively and with humour (comics and cartoons) then why can't you also try communicating that idea verbally? It's two different methods and work in entirely different ways but it's worth a try.

Which brings me to you describing the alt attribute as a description of the image. The alt attribute is an alternative (it provides another possibility (of understanding)) of the image. The example most people use is of a company logo image. Using 'Image of our company logo' would describe it well. Using 'Company name' alone doesn't but does exactly the same job as the company logo image is doing.

The way I was taught to test it out was to display the web page as text only. Then read it aloud to yourself and if the alt text fits smoothly into the flow of words with not even a hint of interference then you have done it well.</description>
		<content:encoded><![CDATA[<p>Thankyou. I&#8217;m about to use Comicpress as a theme for my cartoon site and was blaming the theme for the misuse of the alt attribute. </p>
<p>Comicpress uses the title attribute as a deliberate hovertext element of the theme and the name of the file as alt text. Unfortunately the simplest solution for me was to add my alternative text to the title field and hack the php code to make the alt attribute also use the same data that is for the title attribute.</p>
<p>Now I have a dilemma. The hover text adds value for sighted people just as the alt text adds value for the blind or partially sighted but using both as you say is irritating for those using accessibility devices.</p>
<p>Any thoughts? Should I be &#8216;democratic&#8217; and go with what will be the majority audience? Would the one&#8217;s using screen readers be understanding?</p>
<p>Some think it perverse to add accessibility features to what is a visual web site (cartoons) but I like the whole idea that the web is multi layered. If you can communicate an idea, story or point of view visually effectively and with humour (comics and cartoons) then why can&#8217;t you also try communicating that idea verbally? It&#8217;s two different methods and work in entirely different ways but it&#8217;s worth a try.</p>
<p>Which brings me to you describing the alt attribute as a description of the image. The alt attribute is an alternative (it provides another possibility (of understanding)) of the image. The example most people use is of a company logo image. Using &#8216;Image of our company logo&#8217; would describe it well. Using &#8216;Company name&#8217; alone doesn&#8217;t but does exactly the same job as the company logo image is doing.</p>
<p>The way I was taught to test it out was to display the web page as text only. Then read it aloud to yourself and if the alt text fits smoothly into the flow of words with not even a hint of interference then you have done it well.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
