<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for alt tags</title>
	<link>http://www.alttags.org</link>
	<description>Accessibility, Usability and Web Standards</description>
	<pubDate>Thu, 28 Aug 2008 04:14:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>Comment on The Content Inventory: Roadmap to a Successful CMS Implementation by Kirk Biglione</title>
		<link>http://www.alttags.org/content-management/the-content-inventory-roadmap-to-a-succesful-cms-implementation/#comment-122773</link>
		<dc:creator>Kirk Biglione</dc:creator>
		<pubDate>Wed, 12 Dec 2007 02:16:19 +0000</pubDate>
		<guid>http://www.alttags.org/content-management/the-content-inventory-roadmap-to-a-succesful-cms-implementation/#comment-122773</guid>
		<description>Uma, if you really know your content very well, then you may be able to get away with only document the content types.  However, it's been my experience that those implementing CMS systems are typically not in touch with all of the various content types in any organization.  Conversely, the users who really know the content (domain experts) usually aren't involved in the CMS implementation.  The content inventory is a chance for the implementation team to collaborate with the domain experts in order to uncover all of the various content types, as well as exceptions and variations.  Essentially, the content inventory is a form of content type discovery.</description>
		<content:encoded><![CDATA[<p>Uma, if you really know your content very well, then you may be able to get away with only document the content types.  However, it&#8217;s been my experience that those implementing CMS systems are typically not in touch with all of the various content types in any organization.  Conversely, the users who really know the content (domain experts) usually aren&#8217;t involved in the CMS implementation.  The content inventory is a chance for the implementation team to collaborate with the domain experts in order to uncover all of the various content types, as well as exceptions and variations.  Essentially, the content inventory is a form of content type discovery.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Content Inventory: Roadmap to a Successful CMS Implementation by uma</title>
		<link>http://www.alttags.org/content-management/the-content-inventory-roadmap-to-a-succesful-cms-implementation/#comment-122772</link>
		<dc:creator>uma</dc:creator>
		<pubDate>Mon, 10 Dec 2007 12:47:21 +0000</pubDate>
		<guid>http://www.alttags.org/content-management/the-content-inventory-roadmap-to-a-succesful-cms-implementation/#comment-122772</guid>
		<description>Can you explain why we need to identify every content. What significance it has got esp. for a CMS? I had always thought that in a CMS we need to understand only the types of content and their general schema... and the no of individual items based on the schema is typically populated by content users... so how will it affect the implementation?</description>
		<content:encoded><![CDATA[<p>Can you explain why we need to identify every content. What significance it has got esp. for a CMS? I had always thought that in a CMS we need to understand only the types of content and their general schema&#8230; and the no of individual items based on the schema is typically populated by content users&#8230; so how will it affect the implementation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CMS Do&#8217;s and Don&#8217;ts by We need editors, not a content management system &#187; Alex around the world</title>
		<link>http://www.alttags.org/content-management/cms-dos-and-donts/#comment-8066</link>
		<dc:creator>We need editors, not a content management system &#187; Alex around the world</dc:creator>
		<pubDate>Mon, 20 Mar 2006 17:02:14 +0000</pubDate>
		<guid>http://www.alttags.org/content-management/cms-dos-and-donts/#comment-8066</guid>
		<description>[...] Another interesting article listing some Do&#8217;s and Don&#8217;ts about CMS is posted on Alttags blog. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Another interesting article listing some Do&#8217;s and Don&#8217;ts about CMS is posted on Alttags blog. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on AJAX Hall of Shame: MarketWatch Reinvents The Blink Tag by Artueel blog &#187; Blog Archive &#187; Ajax en usability</title>
		<link>http://www.alttags.org/usability/ajax-hall-of-shame-marketwatch-reinvents-the-blink-tag/#comment-7621</link>
		<dc:creator>Artueel blog &#187; Blog Archive &#187; Ajax en usability</dc:creator>
		<pubDate>Tue, 28 Feb 2006 19:49:07 +0000</pubDate>
		<guid>http://www.alttags.org/usability/ajax-hall-of-shame-marketwatch-reinvents-the-blink-tag/#comment-7621</guid>
		<description>[...] Een (grappig) artikel over overgebruiken van ajax vind je op alt tags. De site die in het artikel wordt vermeld is de website van Marketwatch.com [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Een (grappig) artikel over overgebruiken van ajax vind je op alt tags. De site die in het artikel wordt vermeld is de website van Marketwatch.com [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Businesses Agree to Make Websites Accessible by Miguel from Ottawa, Canada</title>
		<link>http://www.alttags.org/accessibility/businesses-agree-to-make-websites-accessible/#comment-7569</link>
		<dc:creator>Miguel from Ottawa, Canada</dc:creator>
		<pubDate>Thu, 23 Feb 2006 19:00:52 +0000</pubDate>
		<guid>http://www.alttags.org/accessibility/businesses-agree-to-make-websites-accessible/#comment-7569</guid>
		<description>Red Baron, you make me nervous.  I hope you made your comments because you are merely ignorant and don't understand what is being discussed.  Because, if you think for a second that someone other than the owner of a website should be responsible for the barriers it creates, it's time to grow up and learn to take some responsibility for your actions (and inactions).
 
Although I haven't experienced any barriers because of my disability (mobility impaired, but highly functional) I still have a lot of sympathy for those who find web sites impossible to use.  For those who don't seem to get it, I wish I could show you a video of a visually impaired individual, spending quite a while filling out a form, only to find, in the end, he can't click the submit button becuase the web designer used an image whcih captures XY coordinates instead.  It's exasperating, to say the least.

There are too many myths about refitting a website to make  it more accessible.  Of course refitting would take considerable more resources than accommodating accessibility at design stage, but the task can be done in chunks.  Break it down into areas of effort and return on investment.  First do the low effort/high return work. Then, bit by bit, the site becomes more accessible.

There are several reasons other than accomodating disabled persons as well.  Consider the increased readability and better indexing by search engines.

But, I would like to think one would be doing it out of kindness, compassion and a desire to not exclude someone.  Certainly, if the site is for a limited audience of friends, that's one thing, but if it's for a larger group or the public at large, it should be accessible.  You wouldn't keep a person of a certain race out of a site, why would you keep a disabled person out?  Or are they less deserving?

My $0.02,
Miguel Sanchez</description>
		<content:encoded><![CDATA[<p>Red Baron, you make me nervous.  I hope you made your comments because you are merely ignorant and don&#8217;t understand what is being discussed.  Because, if you think for a second that someone other than the owner of a website should be responsible for the barriers it creates, it&#8217;s time to grow up and learn to take some responsibility for your actions (and inactions).</p>
<p>Although I haven&#8217;t experienced any barriers because of my disability (mobility impaired, but highly functional) I still have a lot of sympathy for those who find web sites impossible to use.  For those who don&#8217;t seem to get it, I wish I could show you a video of a visually impaired individual, spending quite a while filling out a form, only to find, in the end, he can&#8217;t click the submit button becuase the web designer used an image whcih captures XY coordinates instead.  It&#8217;s exasperating, to say the least.</p>
<p>There are too many myths about refitting a website to make  it more accessible.  Of course refitting would take considerable more resources than accommodating accessibility at design stage, but the task can be done in chunks.  Break it down into areas of effort and return on investment.  First do the low effort/high return work. Then, bit by bit, the site becomes more accessible.</p>
<p>There are several reasons other than accomodating disabled persons as well.  Consider the increased readability and better indexing by search engines.</p>
<p>But, I would like to think one would be doing it out of kindness, compassion and a desire to not exclude someone.  Certainly, if the site is for a limited audience of friends, that&#8217;s one thing, but if it&#8217;s for a larger group or the public at large, it should be accessible.  You wouldn&#8217;t keep a person of a certain race out of a site, why would you keep a disabled person out?  Or are they less deserving?</p>
<p>My $0.02,<br />
Miguel Sanchez</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Content Inventory: Roadmap to a Successful CMS Implementation by Stig Andersen</title>
		<link>http://www.alttags.org/content-management/the-content-inventory-roadmap-to-a-succesful-cms-implementation/#comment-7277</link>
		<dc:creator>Stig Andersen</dc:creator>
		<pubDate>Tue, 07 Feb 2006 13:05:08 +0000</pubDate>
		<guid>http://www.alttags.org/content-management/the-content-inventory-roadmap-to-a-succesful-cms-implementation/#comment-7277</guid>
		<description>Tomas, Word really isn't an option in my experience. I've tried it once, and will never do it again. Word documents are difficult to handle as they get larger(and they do content inventories do get large).

If I feel I'm out of control and elements may pop up, I leave numbers in between like this: 2.00.00; 2.10.00; 2.20.00; 2.20.10; etc. That way I can insert 2.15.00 if something pops up. Next best solution</description>
		<content:encoded><![CDATA[<p>Tomas, Word really isn&#8217;t an option in my experience. I&#8217;ve tried it once, and will never do it again. Word documents are difficult to handle as they get larger(and they do content inventories do get large).</p>
<p>If I feel I&#8217;m out of control and elements may pop up, I leave numbers in between like this: 2.00.00; 2.10.00; 2.20.00; 2.20.10; etc. That way I can insert 2.15.00 if something pops up. Next best solution</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Five Steps To A Better Website In The New Year by Dustin Y</title>
		<link>http://www.alttags.org/tips-tutorials/five-steps-to-a-better-website-in-the-new-year/#comment-7216</link>
		<dc:creator>Dustin Y</dc:creator>
		<pubDate>Tue, 31 Jan 2006 21:49:01 +0000</pubDate>
		<guid>http://www.alttags.org/tips-tutorials/five-steps-to-a-better-website-in-the-new-year/#comment-7216</guid>
		<description>Great post! definitly gave me some outlook on my own site.</description>
		<content:encoded><![CDATA[<p>Great post! definitly gave me some outlook on my own site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Five Steps To A Better Website In The New Year by Emil Stenström</title>
		<link>http://www.alttags.org/tips-tutorials/five-steps-to-a-better-website-in-the-new-year/#comment-7215</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Tue, 31 Jan 2006 18:27:48 +0000</pubDate>
		<guid>http://www.alttags.org/tips-tutorials/five-steps-to-a-better-website-in-the-new-year/#comment-7215</guid>
		<description>Nice article! Just wanted to add that jargon can be ok sometimes. My site clearly has a target audience of web developers, so putting something move mainstream than CSS and HTML on my navigation to the left would just make them confused. Good list though, I have to go through it and double-check everything.</description>
		<content:encoded><![CDATA[<p>Nice article! Just wanted to add that jargon can be ok sometimes. My site clearly has a target audience of web developers, so putting something move mainstream than CSS and HTML on my navigation to the left would just make them confused. Good list though, I have to go through it and double-check everything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CMS Do&#8217;s and Don&#8217;ts by Brain Frieze</title>
		<link>http://www.alttags.org/content-management/cms-dos-and-donts/#comment-7203</link>
		<dc:creator>Brain Frieze</dc:creator>
		<pubDate>Mon, 30 Jan 2006 11:16:26 +0000</pubDate>
		<guid>http://www.alttags.org/content-management/cms-dos-and-donts/#comment-7203</guid>
		<description>&lt;strong&gt;Do's and Don't of a Content Management System...&lt;/strong&gt;

A Content Management Systems (CMS) can be a great boon for organizations who want to allow a wider audience to publish online. They can also be a major pain in ...</description>
		<content:encoded><![CDATA[<p><strong>Do&#8217;s and Don&#8217;t of a Content Management System&#8230;</strong></p>
<p>A Content Management Systems (CMS) can be a great boon for organizations who want to allow a wider audience to publish online. They can also be a major pain in &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CMS Do&#8217;s and Don&#8217;ts by 3greeneggs &#187; Blog Archive &#187; links for 2006-01-30</title>
		<link>http://www.alttags.org/content-management/cms-dos-and-donts/#comment-7200</link>
		<dc:creator>3greeneggs &#187; Blog Archive &#187; links for 2006-01-30</dc:creator>
		<pubDate>Mon, 30 Jan 2006 04:27:27 +0000</pubDate>
		<guid>http://www.alttags.org/content-management/cms-dos-and-donts/#comment-7200</guid>
		<description>[...] alt tags » CMS Do’s and Don’ts A nice set of guidelines to follow when considering implementing a CMS. (tags: cms webdev) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] alt tags » CMS Do’s and Don’ts A nice set of guidelines to follow when considering implementing a CMS. (tags: cms webdev) [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
