<?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 for Web Access Centre Blog</title>
	<atom:link href="http://www.rnib.org.uk/wacblog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rnib.org.uk/wacblog</link>
	<description></description>
	<pubDate>Fri, 16 May 2008 09:52:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>Comment on CAPTCHA - if your name&#8217;s not down you&#8217;re not coming in. by Movies Clips</title>
		<link>http://www.rnib.org.uk/wacblog/images/captcha-if-youre-names-not-down-youre-not-coming-in/#comment-68850</link>
		<dc:creator>Movies Clips</dc:creator>
		<pubDate>Wed, 07 May 2008 10:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/images/captcha-if-youre-names-not-down-youre-not-coming-in/#comment-68850</guid>
		<description>Hi,Thanks for the informative post Henny. These things are a real nuisance and crop up everywhere, though I suspect you may be right in that there is no easy solution. I came across an example of a website which uses a trivia question to weed out spammers.</description>
		<content:encoded><![CDATA[<p>Hi,Thanks for the informative post Henny. These things are a real nuisance and crop up everywhere, though I suspect you may be right in that there is no easy solution. I came across an example of a website which uses a trivia question to weed out spammers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WebAnywhere: a free screen reader accessed via the web by Henny</title>
		<link>http://www.rnib.org.uk/wacblog/access-technology/webanywhere-a-free-screen-reader-accessed-via-the-web/#comment-68483</link>
		<dc:creator>Henny</dc:creator>
		<pubDate>Tue, 06 May 2008 15:16:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/?p=187#comment-68483</guid>
		<description>Hi Adrian, 
I appreciate your concerns and have also followed comments about WebAnywhere on BCAB. I agree that the devlopment of screen reader tools certainly does seem to have been growing a fair amount recently creating wider choice and with it the possiblity of confusion. I do think there are many positive aspects to having such choice however as long as there is enough information out there that correctly describes all of these products. As you so rightly point out . 
In many cases I'm sure the questions "Which product shall I use" will be answered by what environment you are working in. While a screen reader on a USB or CD such as NVDA may be the right solution for a user with no PC of their own it wont necessarily be for people in developing countries where access to even this basic form of storage is not readily available. A solution such as WebAnywhere could fill that gap. On a personal note I feel that we have a responsibility to help facilitate people accessing the web in developing countries and this hardware / software free solution seems highly attractive, especially with the one laptop per child initiative.
Like you say the market is becoming increasingly swamped but again this may lead to future collaboration rather than dilution as vendors team up, many of the newer screen readers on offer are still in their infancy after all. Overall I think your point about ensuring that there is clear understanding on what each solution offers is key. Wikipedia a page listing screen readers http://en.wikipedia.org/wiki/List_of_screen_readers which would be great to expand. It is also a piece of work that organisations such as RNIB, AbilityNet, Becta and others could also work together on.</description>
		<content:encoded><![CDATA[<p>Hi Adrian,<br />
I appreciate your concerns and have also followed comments about WebAnywhere on BCAB. I agree that the devlopment of screen reader tools certainly does seem to have been growing a fair amount recently creating wider choice and with it the possiblity of confusion. I do think there are many positive aspects to having such choice however as long as there is enough information out there that correctly describes all of these products. As you so rightly point out .<br />
In many cases I&#8217;m sure the questions &#8220;Which product shall I use&#8221; will be answered by what environment you are working in. While a screen reader on a USB or CD such as NVDA may be the right solution for a user with no PC of their own it wont necessarily be for people in developing countries where access to even this basic form of storage is not readily available. A solution such as WebAnywhere could fill that gap. On a personal note I feel that we have a responsibility to help facilitate people accessing the web in developing countries and this hardware / software free solution seems highly attractive, especially with the one laptop per child initiative.<br />
Like you say the market is becoming increasingly swamped but again this may lead to future collaboration rather than dilution as vendors team up, many of the newer screen readers on offer are still in their infancy after all. Overall I think your point about ensuring that there is clear understanding on what each solution offers is key. Wikipedia a page listing screen readers <a href="http://en.wikipedia.org/wiki/List_of_screen_readers" rel="nofollow">http://en.wikipedia.org/wiki/List_of_screen_readers</a> which would be great to expand. It is also a piece of work that organisations such as RNIB, AbilityNet, Becta and others could also work together on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WebAnywhere: a free screen reader accessed via the web by Adrian Higginbotham</title>
		<link>http://www.rnib.org.uk/wacblog/access-technology/webanywhere-a-free-screen-reader-accessed-via-the-web/#comment-64118</link>
		<dc:creator>Adrian Higginbotham</dc:creator>
		<pubDate>Wed, 23 Apr 2008 09:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/?p=187#comment-64118</guid>
		<description>always good to see new free to use tools and open source activity that adds to the knowledge of the overall community but this side of the market seems to be growing rapidly of late and I fear we're in danger of giving those who stand to benefit most, the individual new to the technology, too much choice and too little information about which products are appropriate.  Which free product shall I use? NVDA the open source screenreader that requires no installation (and can be run from a a USB drive or CD), System Access to go, (recently made freely available to anyone via the accessibility is a right (air) foundation), Thunder (which has been free to individuals for some time) but which has recently been made free to organisations too. or maybe I only need a website screenreader such as the one mentioned here, or Firevox, the free plug-in for the Firefox browser that serves much the same function.  and as they are the ones I can think of from the top of my head it seems likely there are others.  Anything that means we don't need to pay $1000 or £500+ for access to a computer is of course welcomed but too much choice and too few unique selling points might just lead to confused users vulnerable to salesmen (and women too) and nothing chaging.  It would be nice to see a bit more collaboration between freeware and open source projects leading to fewer but more comprehensive and capable tools rather than all this duplication of effert.</description>
		<content:encoded><![CDATA[<p>always good to see new free to use tools and open source activity that adds to the knowledge of the overall community but this side of the market seems to be growing rapidly of late and I fear we&#8217;re in danger of giving those who stand to benefit most, the individual new to the technology, too much choice and too little information about which products are appropriate.  Which free product shall I use? NVDA the open source screenreader that requires no installation (and can be run from a a USB drive or CD), System Access to go, (recently made freely available to anyone via the accessibility is a right (air) foundation), Thunder (which has been free to individuals for some time) but which has recently been made free to organisations too. or maybe I only need a website screenreader such as the one mentioned here, or Firevox, the free plug-in for the Firefox browser that serves much the same function.  and as they are the ones I can think of from the top of my head it seems likely there are others.  Anything that means we don&#8217;t need to pay $1000 or £500+ for access to a computer is of course welcomed but too much choice and too few unique selling points might just lead to confused users vulnerable to salesmen (and women too) and nothing chaging.  It would be nice to see a bit more collaboration between freeware and open source projects leading to fewer but more comprehensive and capable tools rather than all this duplication of effert.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility 2.0 - Conference by joanne finch</title>
		<link>http://www.rnib.org.uk/wacblog/conferences/accessibility-20-conference/#comment-63977</link>
		<dc:creator>joanne finch</dc:creator>
		<pubDate>Tue, 22 Apr 2008 12:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/?p=185#comment-63977</guid>
		<description>I'll be there too!
Might be a bit tired after having to get up at 5.30am to get there on time.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll be there too!<br />
Might be a bit tired after having to get up at 5.30am to get there on time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility 2.0 - Conference by patrick h. lauke</title>
		<link>http://www.rnib.org.uk/wacblog/conferences/accessibility-20-conference/#comment-63896</link>
		<dc:creator>patrick h. lauke</dc:creator>
		<pubDate>Mon, 21 Apr 2008 22:29:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/?p=185#comment-63896</guid>
		<description>I'll be there, though my train comes in late so I'll probably miss the first session.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll be there, though my train comes in late so I&#8217;ll probably miss the first session.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Too much accessibility - TITLE attributes by Bim</title>
		<link>http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-title-attributes/#comment-62858</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Wed, 16 Apr 2008 11:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-title-attributes/#comment-62858</guid>
		<description>Hi Peter,  I'm not sure that I understand how a potentially 
confusing repetition  can be better than clear static link text.  The 
user can easily get the link read again, if they aren't sure where it 
leads.  But the convergence of a link, for instance to, "About us", 
with an identical TITLE attribute is likely to be announced 
as, "About usabout us". The only way to avoid this is to include 
punctuation and spaces in the TITLE, such as "About us. ".  
Punctuation in "tooltip" text is so rare, that there's a greater 
likelihood of increasing, rather than reducing confusion.

Where TITLE attributes may be useful, is in providing a call to 
action, or expansion of the link text.  For instance a link to "Sport" 
is self-explanatory, but can mean different things depending on the 
sporting season, or the content being provided on the site. Here 
the TITLE "attribute could be useful, identifying the sports being 
covered.  Then it would be explaining the "Sport" link, without   
confusion or repetition, although the link text, "Sport",  is accurate 
in itself.  So there are winners, but no losers. 

I do take your point on the width of text in our Blog though, and 
thank you for raising it.  We've started working on a way to get this 
under  control, and hope to have it changed in the near future.</description>
		<content:encoded><![CDATA[<p>Hi Peter,  I&#8217;m not sure that I understand how a potentially<br />
confusing repetition  can be better than clear static link text.  The<br />
user can easily get the link read again, if they aren&#8217;t sure where it<br />
leads.  But the convergence of a link, for instance to, &#8220;About us&#8221;,<br />
with an identical TITLE attribute is likely to be announced<br />
as, &#8220;About usabout us&#8221;. The only way to avoid this is to include<br />
punctuation and spaces in the TITLE, such as &#8220;About us. &#8220;.<br />
Punctuation in &#8220;tooltip&#8221; text is so rare, that there&#8217;s a greater<br />
likelihood of increasing, rather than reducing confusion.</p>
<p>Where TITLE attributes may be useful, is in providing a call to<br />
action, or expansion of the link text.  For instance a link to &#8220;Sport&#8221;<br />
is self-explanatory, but can mean different things depending on the<br />
sporting season, or the content being provided on the site. Here<br />
the TITLE &#8220;attribute could be useful, identifying the sports being<br />
covered.  Then it would be explaining the &#8220;Sport&#8221; link, without<br />
confusion or repetition, although the link text, &#8220;Sport&#8221;,  is accurate<br />
in itself.  So there are winners, but no losers. </p>
<p>I do take your point on the width of text in our Blog though, and<br />
thank you for raising it.  We&#8217;ve started working on a way to get this<br />
under  control, and hope to have it changed in the near future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CAPTCHA - if your name&#8217;s not down you&#8217;re not coming in. by imam hossain</title>
		<link>http://www.rnib.org.uk/wacblog/images/captcha-if-youre-names-not-down-youre-not-coming-in/#comment-62676</link>
		<dc:creator>imam hossain</dc:creator>
		<pubDate>Tue, 15 Apr 2008 17:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/images/captcha-if-youre-names-not-down-youre-not-coming-in/#comment-62676</guid>
		<description>need captcha data entry work</description>
		<content:encoded><![CDATA[<p>need captcha data entry work</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Too much accessibility - TITLE attributes by Peter Stevens</title>
		<link>http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-title-attributes/#comment-61295</link>
		<dc:creator>Peter Stevens</dc:creator>
		<pubDate>Wed, 09 Apr 2008 00:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-title-attributes/#comment-61295</guid>
		<description>Hello Folks,
I'm not convinced by this article at all, I'm sorry. For me accessibility
is about balancing functionality with practicality. For someone using
a screen reader with disabled hands and suffering from short-term 
memory loss, repitition is vital!

Often there is a delay in deciding whether or not to follow that link, 
so those few seconds whilst the "confirmation" of where the link 
leads becomes vital! 

There is one really peeving thing about _this_ page! Good readability
is limiting lines of text to around 12 to 15 per line. That provides the 
ability to speed-read (with assimilation) and does not hurt the eyes 
of people with reasonable vision have it badly hampered by trying 
to follow long lines of text right across the screen. 
...and No! resizing the browser window is _not_ an option.

Both the article and this page layout demonstrate excuses for not
putting enough thought into the design process. Expending a bit of
thought into how title texts are composed is by far better than just
leaving them out.</description>
		<content:encoded><![CDATA[<p>Hello Folks,<br />
I&#8217;m not convinced by this article at all, I&#8217;m sorry. For me accessibility<br />
is about balancing functionality with practicality. For someone using<br />
a screen reader with disabled hands and suffering from short-term<br />
memory loss, repitition is vital!</p>
<p>Often there is a delay in deciding whether or not to follow that link,<br />
so those few seconds whilst the &#8220;confirmation&#8221; of where the link<br />
leads becomes vital! </p>
<p>There is one really peeving thing about _this_ page! Good readability<br />
is limiting lines of text to around 12 to 15 per line. That provides the<br />
ability to speed-read (with assimilation) and does not hurt the eyes<br />
of people with reasonable vision have it badly hampered by trying<br />
to follow long lines of text right across the screen.<br />
&#8230;and No! resizing the browser window is _not_ an option.</p>
<p>Both the article and this page layout demonstrate excuses for not<br />
putting enough thought into the design process. Expending a bit of<br />
thought into how title texts are composed is by far better than just<br />
leaving them out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hidden barriers - out of sight by Bim</title>
		<link>http://www.rnib.org.uk/wacblog/css/hidden-barriers-out-of-sight/#comment-60990</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Mon, 07 Apr 2008 12:28:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-out-of-sight/#comment-60990</guid>
		<description>You're absolutely right, "display: none"  does prevent most screen reader from announcing hidden content .

You aren't quite right in thinking that  this is only used for image replacement though.  It's also used to display and collapse menus where, if screen readers ignored the "display: none" command, their users would have the dubious treat of having to read every second and third level link on a page, even though they aren't visible.  It's also used for showing and hiding FAQ answers on some pages, and because that technique is used, rather than in-page links, the creen reader would need to read through all unwanted answers until they reach the one they want.</description>
		<content:encoded><![CDATA[<p>You&#8217;re absolutely right, &#8220;display: none&#8221;  does prevent most screen reader from announcing hidden content .</p>
<p>You aren&#8217;t quite right in thinking that  this is only used for image replacement though.  It&#8217;s also used to display and collapse menus where, if screen readers ignored the &#8220;display: none&#8221; command, their users would have the dubious treat of having to read every second and third level link on a page, even though they aren&#8217;t visible.  It&#8217;s also used for showing and hiding FAQ answers on some pages, and because that technique is used, rather than in-page links, the creen reader would need to read through all unwanted answers until they reach the one they want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is your site half-naked? by Bim</title>
		<link>http://www.rnib.org.uk/wacblog/css/is-your-site-half-naked/#comment-60983</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Mon, 07 Apr 2008 11:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/general/is-your-site-half-naked/#comment-60983</guid>
		<description>Hi Aazim,

It's possible that you have your browser settings for colour set to override the  web site designed colours, or to ignore CSS colours defined by the web site.  Which browser are you using?

If you can let us know, we may be able to tell you how to fix it.</description>
		<content:encoded><![CDATA[<p>Hi Aazim,</p>
<p>It&#8217;s possible that you have your browser settings for colour set to override the  web site designed colours, or to ignore CSS colours defined by the web site.  Which browser are you using?</p>
<p>If you can let us know, we may be able to tell you how to fix it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
