<?xml version="1.0"  encoding="utf-8"?>
	<feed xmlns="http://www.w3.org/2005/Atom">
		<title>Comments to Quick Query: Filmmaker Joseph Monks And Web Accessibility</title>
		<link href="http://www.practicalecommerce.com/atom/article/587/" rel="self"/>
  	<updated>2008-03-25T16:59:45-07:00</updated>
		<author>
  	  <name>Practical Ecommerce</name>
			<email>info@practicalecommerce.com</email>
  	</author>
  	<id>http://www.practicalecommerce.com/</id>
		<rights>Copyright 2007 Confluence Publishing DBA Practical Ecommerce</rights>
		<entry>
			<title>Cindy E.</title>
			<link href="http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment8128" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment8128</id>
			<updated>2008-03-25T16:59:45-07:00</updated>
			<summary>As a self-instructed web designer and developer this article really opened my eyes to what I need to do. I have been lazy with my ALT tags not realizing how important they really were. Although I have wondered about creating accessible websites, I had no idea it could be done so easily.</summary>
			</entry>
			
				<entry>
			<title>Kerry M.</title>
			<link href="http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment3938" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment3938</id>
			<updated>2007-10-24T15:19:28-07:00</updated>
			<summary>Mr. Monks reports that this Practical eCommerce website is inaccessible for blind users. That&#039;s due to the captcha code (below) that we use to prevent spam comments. That code requires a visual ability to read it because, Mr. Monks reports, most screenreaders fail to interpret the captcha characters.  He notes that there&#039;s additional information on captchas, including audio captchas for the blind, at Captcha.net.

As for this site, we&#039;ll soon be correcting the problem.

Kerry Murdock
Publisher</summary>
			</entry>
			
				<entry>
			<title>Joe Monks</title>
			<link href="http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment3923" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment3923</id>
			<updated>2007-10-22T10:53:13-07:00</updated>
			<summary>With all the publicity surrounding the lawsuit brought against the TARGET chain, it seems to me that there will be a lot of work for developers as e-tailers address (many for the first time) the accessibility issue. The TARGET lawsuit looks like it will define a lot of grey areas when it is all said and done, and having the skills necessary to make sites as accessible and easy to use as possible for the greatest amount of potential customers will be a necessity. </summary>
			</entry>
			
				<entry>
			<title>Jennifer Bruce</title>
			<link href="http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment3896" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/587/Quick-Query-Filmmaker-Joseph-Monks-And-Web-Accessibility/#comment3896</id>
			<updated>2007-10-17T17:26:18-07:00</updated>
			<summary>I&#039;m taking a web development class (intro) and this article raises my awareness on why I need to define the alt tag - instead of being lazy and leaving it undefined.  Understanding how other people use web sites improves my web design and construction skills, so articles like these are helpful.</summary>
			</entry>
			
				
	</feed>