<?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: 13 Tips For An Accessible Site</title>
	<atom:link href="http://blackwidows.co.uk/blog/2008/07/10/13-tips-for-an-accessible-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://blackwidows.co.uk/blog/2008/07/10/13-tips-for-an-accessible-site/</link>
	<description>The meanderings of a black widow...</description>
	<pubDate>Fri, 21 Nov 2008 12:44:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Black Widow</title>
		<link>http://blackwidows.co.uk/blog/2008/07/10/13-tips-for-an-accessible-site/#comment-64711</link>
		<dc:creator>Black Widow</dc:creator>
		<pubDate>Thu, 17 Jul 2008 13:01:42 +0000</pubDate>
		<guid isPermaLink="false">http://blackwidows.co.uk/blog/?p=179#comment-64711</guid>
		<description>@Stevie D: I appreciate your point but then they're not the kind of CAPTCHAs I meant when I used the term "visual CAPTCHAs". I'd class them as text based. it's the standard distorted characters on patterned backgrounds that I think have to be avoided at all costs. I failed such a CAPTCHA 4 times the other week. And I was wearing my glasses! So what chance does someone with a significant visual impairment or dyslexia have?

Yes, the text based CAPTCHAs have their own problems - not least of which is the fact that they depend completely on what kind of question is used. Standard &lt;abbr title="Intelligence Quotient"&gt;I.Q.&lt;/abbr&gt; tests are often criticised for being culturally biased and I think there is a risk that the questions used in text CAPTCHAs can be, quite unconsciously, similarly biased in a way that has nothing to do with language skills or cognitive abilities.

Ideally, I'd like to see all forms of CAPTCHA abandoned (sooner rather than later) in favour of security methods that don't make users jump through hoops but I freely admit that I don't have any solutions myself. For now, I think text-based CAPTCHAs are the best of a bad lot providing they're implemented as sympathetically as possible.</description>
		<content:encoded><![CDATA[<p>@Stevie D: I appreciate your point but then they&#8217;re not the kind of CAPTCHAs I meant when I used the term &#8220;visual CAPTCHAs&#8221;. I&#8217;d class them as text based. it&#8217;s the standard distorted characters on patterned backgrounds that I think have to be avoided at all costs. I failed such a CAPTCHA 4 times the other week. And I was wearing my glasses! So what chance does someone with a significant visual impairment or dyslexia have?</p>
<p>Yes, the text based CAPTCHAs have their own problems - not least of which is the fact that they depend completely on what kind of question is used. Standard <abbr title="Intelligence Quotient">I.Q.</abbr> tests are often criticised for being culturally biased and I think there is a risk that the questions used in text CAPTCHAs can be, quite unconsciously, similarly biased in a way that has nothing to do with language skills or cognitive abilities.</p>
<p>Ideally, I&#8217;d like to see all forms of CAPTCHA abandoned (sooner rather than later) in favour of security methods that don&#8217;t make users jump through hoops but I freely admit that I don&#8217;t have any solutions myself. For now, I think text-based CAPTCHAs are the best of a bad lot providing they&#8217;re implemented as sympathetically as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stevie D</title>
		<link>http://blackwidows.co.uk/blog/2008/07/10/13-tips-for-an-accessible-site/#comment-64703</link>
		<dc:creator>Stevie D</dc:creator>
		<pubDate>Thu, 17 Jul 2008 11:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://blackwidows.co.uk/blog/?p=179#comment-64703</guid>
		<description>I know that it is not right to discriminate against anyone, but realistically, if someone has such poor English skills, or such severe cognitive disabilities, that they can't answer the question "Is fire hot or cold?", you have to ask how much value they will be getting out of your website. It's a serious question - if someone can't answer a simple question like that, are they really likely to be reading and commenting on your blog?</description>
		<content:encoded><![CDATA[<p>I know that it is not right to discriminate against anyone, but realistically, if someone has such poor English skills, or such severe cognitive disabilities, that they can&#8217;t answer the question &#8220;Is fire hot or cold?&#8221;, you have to ask how much value they will be getting out of your website. It&#8217;s a serious question - if someone can&#8217;t answer a simple question like that, are they really likely to be reading and commenting on your blog?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JackP</title>
		<link>http://blackwidows.co.uk/blog/2008/07/10/13-tips-for-an-accessible-site/#comment-64116</link>
		<dc:creator>JackP</dc:creator>
		<pubDate>Sat, 12 Jul 2008 16:03:29 +0000</pubDate>
		<guid isPermaLink="false">http://blackwidows.co.uk/blog/?p=179#comment-64116</guid>
		<description>I don't necessarily see 'a completely automated test to tell computers and humans apart' as a &lt;strong&gt;bad&lt;/strong&gt; thing. What is a bad thing is having 'a completely automated test which will block all blind users and about 80% of spam bots'. If you're going to have a CAPTCHA, use some form of logic CAPTCHA (but it needs to be relatively simple, and with an element of randomness). Don't just use the standard 'distorted text' business.

...admittedly, even if you do that, your site will not be usable to people with certain cognitive disabilities, but if you pitch it so that the difficulty of the question is no more difficult than the complexity of the site &lt;em&gt;content&lt;/em&gt;, that ought to ease that problem slightly...

[other than that, top list!]</description>
		<content:encoded><![CDATA[<p>I don&#8217;t necessarily see &#8216;a completely automated test to tell computers and humans apart&#8217; as a <strong>bad</strong> thing. What is a bad thing is having &#8216;a completely automated test which will block all blind users and about 80% of spam bots&#8217;. If you&#8217;re going to have a CAPTCHA, use some form of logic CAPTCHA (but it needs to be relatively simple, and with an element of randomness). Don&#8217;t just use the standard &#8216;distorted text&#8217; business.</p>
<p>&#8230;admittedly, even if you do that, your site will not be usable to people with certain cognitive disabilities, but if you pitch it so that the difficulty of the question is no more difficult than the complexity of the site <em>content</em>, that ought to ease that problem slightly&#8230;</p>
<p>[other than that, top list!]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stevie D</title>
		<link>http://blackwidows.co.uk/blog/2008/07/10/13-tips-for-an-accessible-site/#comment-64024</link>
		<dc:creator>Stevie D</dc:creator>
		<pubDate>Fri, 11 Jul 2008 12:20:54 +0000</pubDate>
		<guid isPermaLink="false">http://blackwidows.co.uk/blog/?p=179#comment-64024</guid>
		<description>Re: point 5
Be as flexible as you can when requesting data in form fields.

For example, I have seen some sites that require you to enter the date in the form dd/mm/yyyy, and won't accept d/m/yy.
By contrast, there's another site that will read and parse the date in whatever format you write it (eg UK or ISO), including "11th July", "tomorrow", "next Thursday".
If one hobbyist site can do this, why are some huge professional sites so finicky?

Similarly, any site that requires telephone numbers or addresses to be entered in a particular format is likely to be difficult/impossible for overseas users, as well as putting up considerable accessibility barriers to "local" users.</description>
		<content:encoded><![CDATA[<p>Re: point 5<br />
Be as flexible as you can when requesting data in form fields.</p>
<p>For example, I have seen some sites that require you to enter the date in the form dd/mm/yyyy, and won&#8217;t accept d/m/yy.<br />
By contrast, there&#8217;s another site that will read and parse the date in whatever format you write it (eg <acronym title="United Kingdom">UK</acronym> or ISO), including &#8220;11th July&#8221;, &#8220;tomorrow&#8221;, &#8220;next Thursday&#8221;.<br />
If one hobbyist site can do this, why are some huge professional sites so finicky?</p>
<p>Similarly, any site that requires telephone numbers or addresses to be entered in a particular format is likely to be difficult/impossible for overseas users, as well as putting up considerable accessibility barriers to &#8220;local&#8221; users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blair Millen</title>
		<link>http://blackwidows.co.uk/blog/2008/07/10/13-tips-for-an-accessible-site/#comment-63957</link>
		<dc:creator>Blair Millen</dc:creator>
		<pubDate>Thu, 10 Jul 2008 21:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://blackwidows.co.uk/blog/?p=179#comment-63957</guid>
		<description>Excellent list. As you say Mel, keeping the list down to ten (even thirteen) is tough, but I have to say you've covered, rather comprehensively, every important aspect one should consider when trying to make their site accessible.

A good reference point for any web designer whatever level of expertise they claim.</description>
		<content:encoded><![CDATA[<p>Excellent list. As you say Mel, keeping the list down to ten (even thirteen) is tough, but I have to say you&#8217;ve covered, rather comprehensively, every important aspect one should consider when trying to make their site accessible.</p>
<p>A good reference point for any web designer whatever level of expertise they claim.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
