<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for DingoAccess</title>
	<atom:link href="http://www.dingoaccess.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dingoaccess.com</link>
	<description>Random thoughts, stories and ideas from Roger Hudson of Web Usability</description>
	<lastBuildDate>Tue, 31 Jan 2012 17:48:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>Comment on Accessing Nav Drop-Downs by seo</title>
		<link>http://www.dingoaccess.com/accessibility/accessing-nav-drop-downs/comment-page-1/#comment-922</link>
		<dc:creator>seo</dc:creator>
		<pubDate>Tue, 31 Jan 2012 17:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=447#comment-922</guid>
		<description>My spouse and I absolutely love your blog and find most of your post&#039;s to be precisely what I&#039;m looking for. Do you offer guest writers to write content in your case? I wouldn&#039;t mind writing a post or elaborating on a lot of the subjects you write related to here. Again, awesome site!</description>
		<content:encoded><![CDATA[<p>My spouse and I absolutely love your blog and find most of your post&#8217;s to be precisely what I&#8217;m looking for. Do you offer guest writers to write content in your case? I wouldn&#8217;t mind writing a post or elaborating on a lot of the subjects you write related to here. Again, awesome site!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mature Age ICT Users Online Survey Results by Endru nujoma</title>
		<link>http://www.dingoaccess.com/accessibility/mature-age-ict-users-online-survey-results/comment-page-1/#comment-919</link>
		<dc:creator>Endru nujoma</dc:creator>
		<pubDate>Wed, 04 Jan 2012 07:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=523#comment-919</guid>
		<description>I want to find out how i point i got in my test for mature age i dind received my test result jet in my pos addre. can you plz forward for me through my email address above.thank u</description>
		<content:encoded><![CDATA[<p>I want to find out how i point i got in my test for mature age i dind received my test result jet in my pos addre. can you plz forward for me through my email address above.thank u</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility Barrier Scores by JulieG</title>
		<link>http://www.dingoaccess.com/accessibility/accessibility-barrier-scores-2/comment-page-1/#comment-918</link>
		<dc:creator>JulieG</dc:creator>
		<pubDate>Thu, 22 Dec 2011 00:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=647#comment-918</guid>
		<description>I wonder if it would be worth doing some polling of people with various disabilities or who use the different ATs to find out how they&#039;d rate the severity of each of the WCAG2 criteria? It&#039;d be good to have a severity rating based on numbers rather than my (non-AT-using) opinion.</description>
		<content:encoded><![CDATA[<p>I wonder if it would be worth doing some polling of people with various disabilities or who use the different ATs to find out how they&#8217;d rate the severity of each of the WCAG2 criteria? It&#8217;d be good to have a severity rating based on numbers rather than my (non-AT-using) opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Measuring accessibility by michelangelo</title>
		<link>http://www.dingoaccess.com/accessibility/measuring-accessibility/comment-page-1/#comment-899</link>
		<dc:creator>michelangelo</dc:creator>
		<pubDate>Mon, 12 Dec 2011 20:36:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=634#comment-899</guid>
		<description>I always perform both. I fancy it gives me a pretty good picture of a system&#039;s accessibility. My challenge now is how to convey that information to my audience: government customer and IT. In both cases it is very hard to convey the fact that it is a shaded picture; that it is not a simple pass/fail situation; that if you focus on the goals, there are many solutions to the same problem; etc. This is not what they like to hear, and the nuance may be taken as a license to do nothing. IO would welcome any discussion or advice in this area...</description>
		<content:encoded><![CDATA[<p>I always perform both. I fancy it gives me a pretty good picture of a system&#8217;s accessibility. My challenge now is how to convey that information to my audience: government customer and IT. In both cases it is very hard to convey the fact that it is a shaded picture; that it is not a simple pass/fail situation; that if you focus on the goals, there are many solutions to the same problem; etc. This is not what they like to hear, and the nuance may be taken as a license to do nothing. IO would welcome any discussion or advice in this area&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility Barrier Scores by Cliff Tyllick</title>
		<link>http://www.dingoaccess.com/accessibility/accessibility-barrier-scores-2/comment-page-1/#comment-895</link>
		<dc:creator>Cliff Tyllick</dc:creator>
		<pubDate>Fri, 09 Dec 2011 21:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=647#comment-895</guid>
		<description>Roger, there is much to be said for this approach. I&#039;d like to take it one step further by pointing out that both the incidence and significance of a barrier depend on the disability being considered.

Color contrast is one such issue. It is of no consequence to people who are totally blind, but it is supremely important to people with partial vision. Still, it affects different people in different ways. Many people who are sensitive to issues of contrast, it seems, need high contrast. But people with low moderate vision, who must use one method or another to magnify the text highly, actually need &lt;em&gt;low&lt;/em&gt; contrast—a white background can cause great distress when you must keep your eyes just a few centimeters from the screen so you can read.

That&#039;s just one of many conceivable instances in which a method that improves accessibility for one group of people will create a barrier for others.

So to truly be useful, an assessment of accessibility should define these points:

the task being considered
the nature of the barrier
the severity of the barrier
the type of disability a person must have to be affected by this barrier
perhaps even the type of assistive technology the reviewer assumes the person is using
the skill level of the users affected by the barrier (novice? expert? expert in the subject area, but novice to assistive technology?)
the frequency with which these folks are likely to encounter this barrier


This might seem to be an overwhelming degree of detail, but note that an answer to one question might answer others, as well. For example:

An application that is inaccessible except through the mouse would affect (nearly) all people with visual disabilities or mobility impairments—but would have no impact on people with cognitive disabilities or the Deaf.
A site that requires visitors to find and click a randomly positioned Easter egg before they can get beyond a splash page would be inaccessible to just about everybody. (I hope I didn&#039;t just inspire the hottest new trend among would-be designers.)


This approach would require adding two or three columns to your proposed worksheet. I see several significant advantages:


I would feel less hesitant to publish my assessment of a site&#039;s accessibility, because I could clearly show the limitations of my expertise (or at least of this assessment).
Even if I hadn&#039;t directly considered your situation, you would have greater information about  my assessment&#039;s relevance to you.
On more websites, we might see &lt;a / rel=&quot;nofollow&quot;&gt;reasonable commitments to continuously improving accessibility&lt;/a&gt; rather than unsupported claims that the content is fully accessible.


I&#039;m glad you started this discussion. Great idea!</description>
		<content:encoded><![CDATA[<p>Roger, there is much to be said for this approach. I&#8217;d like to take it one step further by pointing out that both the incidence and significance of a barrier depend on the disability being considered.</p>
<p>Color contrast is one such issue. It is of no consequence to people who are totally blind, but it is supremely important to people with partial vision. Still, it affects different people in different ways. Many people who are sensitive to issues of contrast, it seems, need high contrast. But people with low moderate vision, who must use one method or another to magnify the text highly, actually need <em>low</em> contrast—a white background can cause great distress when you must keep your eyes just a few centimeters from the screen so you can read.</p>
<p>That&#8217;s just one of many conceivable instances in which a method that improves accessibility for one group of people will create a barrier for others.</p>
<p>So to truly be useful, an assessment of accessibility should define these points:</p>
<p>the task being considered<br />
the nature of the barrier<br />
the severity of the barrier<br />
the type of disability a person must have to be affected by this barrier<br />
perhaps even the type of assistive technology the reviewer assumes the person is using<br />
the skill level of the users affected by the barrier (novice? expert? expert in the subject area, but novice to assistive technology?)<br />
the frequency with which these folks are likely to encounter this barrier</p>
<p>This might seem to be an overwhelming degree of detail, but note that an answer to one question might answer others, as well. For example:</p>
<p>An application that is inaccessible except through the mouse would affect (nearly) all people with visual disabilities or mobility impairments—but would have no impact on people with cognitive disabilities or the Deaf.<br />
A site that requires visitors to find and click a randomly positioned Easter egg before they can get beyond a splash page would be inaccessible to just about everybody. (I hope I didn&#8217;t just inspire the hottest new trend among would-be designers.)</p>
<p>This approach would require adding two or three columns to your proposed worksheet. I see several significant advantages:</p>
<p>I would feel less hesitant to publish my assessment of a site&#8217;s accessibility, because I could clearly show the limitations of my expertise (or at least of this assessment).<br />
Even if I hadn&#8217;t directly considered your situation, you would have greater information about  my assessment&#8217;s relevance to you.<br />
On more websites, we might see <a / rel="nofollow">reasonable commitments to continuously improving accessibility</a> rather than unsupported claims that the content is fully accessible.</p>
<p>I&#8217;m glad you started this discussion. Great idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility Barrier Scores by David</title>
		<link>http://www.dingoaccess.com/accessibility/accessibility-barrier-scores-2/comment-page-1/#comment-885</link>
		<dc:creator>David</dc:creator>
		<pubDate>Fri, 02 Dec 2011 18:12:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=647#comment-885</guid>
		<description>Remediation priorities &quot;Critical&quot; and &quot;None&quot; are incompatible. They can both apply at the same time in non-realistic hypothetical situations (such as non-public functionality being completely inaccessible).
So no it doesn&#039;t &quot;matter&quot;, but you might as well make it logical by writing:
Critical: Any barrier that has a severity score of 5 and a non-zero incidence score.

As a bonus, it&#039;s shorter than the original.</description>
		<content:encoded><![CDATA[<p>Remediation priorities &#8220;Critical&#8221; and &#8220;None&#8221; are incompatible. They can both apply at the same time in non-realistic hypothetical situations (such as non-public functionality being completely inaccessible).<br />
So no it doesn&#8217;t &#8220;matter&#8221;, but you might as well make it logical by writing:<br />
Critical: Any barrier that has a severity score of 5 and a non-zero incidence score.</p>
<p>As a bonus, it&#8217;s shorter than the original.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility Barrier Scores by Roger</title>
		<link>http://www.dingoaccess.com/accessibility/accessibility-barrier-scores-2/comment-page-1/#comment-874</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Tue, 29 Nov 2011 22:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=647#comment-874</guid>
		<description>Thanks Detlev for your kind words and for referring the article to the EVAL TF. 
With reference to your comments about poor use of heading structure (BTW love your use of the word warbled for this). I feel the suggested barrier probably covers this - if the heading structure on all pages is so warbled that it makes no semantic sense at all, I would suggest an Incidence score of 4 and Severity score of 3 would be appropriate (because even poor use of headers does bring some benefit). However, if the header element wasn&#039;t used at all on any page then the Incidence score would remain the same but the Severity score would be 4.
With regard to your comment about lightboxes (overlays) - good point. I think the suggested barrier &quot;Unable to access and/or operate all page content with the keyboard&quot; may not cover this adequately.</description>
		<content:encoded><![CDATA[<p>Thanks Detlev for your kind words and for referring the article to the EVAL TF.<br />
With reference to your comments about poor use of heading structure (BTW love your use of the word warbled for this). I feel the suggested barrier probably covers this &#8211; if the heading structure on all pages is so warbled that it makes no semantic sense at all, I would suggest an Incidence score of 4 and Severity score of 3 would be appropriate (because even poor use of headers does bring some benefit). However, if the header element wasn&#8217;t used at all on any page then the Incidence score would remain the same but the Severity score would be 4.<br />
With regard to your comment about lightboxes (overlays) &#8211; good point. I think the suggested barrier &#8220;Unable to access and/or operate all page content with the keyboard&#8221; may not cover this adequately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility Barrier Scores by Roger</title>
		<link>http://www.dingoaccess.com/accessibility/accessibility-barrier-scores-2/comment-page-1/#comment-873</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Tue, 29 Nov 2011 22:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=647#comment-873</guid>
		<description>I agree Steve and this is why I suggest the barrier scores should be used by someone who is familiar with accessibility and the needs of people with different abilities, and also in conjunction with some acknowledged standard such as WCAG 2.0.</description>
		<content:encoded><![CDATA[<p>I agree Steve and this is why I suggest the barrier scores should be used by someone who is familiar with accessibility and the needs of people with different abilities, and also in conjunction with some acknowledged standard such as WCAG 2.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on &#8216;Fluro&#8217; Colours by Andrew</title>
		<link>http://www.dingoaccess.com/accessibility/fluro-colours-2/comment-page-1/#comment-854</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 25 Nov 2011 05:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=587#comment-854</guid>
		<description>Hi Roger, 

Another audience to consider is older people. The first ever guide to websites for older people (AFAIK) from the Spry Foundation [1] suggests &quot;Fluorescent colors belong in a slightly different category. These colors are supersaturated, but in addition they reflect both normal light and ultraviolet light. The effect is very intense, but can be exhausting to the eye, especially if there are visual disabilities involved. This effect makes fluorescent colors a less than effective choice for text or background.&quot; This is supported by others working with older people [2].

Andrew
[1] http://www.spry.org/pdf/website_creators_guide.pdf
[2] http://otal.umd.edu/UUPractice/elderly/</description>
		<content:encoded><![CDATA[<p>Hi Roger, </p>
<p>Another audience to consider is older people. The first ever guide to websites for older people (AFAIK) from the Spry Foundation [1] suggests &#8220;Fluorescent colors belong in a slightly different category. These colors are supersaturated, but in addition they reflect both normal light and ultraviolet light. The effect is very intense, but can be exhausting to the eye, especially if there are visual disabilities involved. This effect makes fluorescent colors a less than effective choice for text or background.&#8221; This is supported by others working with older people [2].</p>
<p>Andrew<br />
[1] <a href="http://www.spry.org/pdf/website_creators_guide.pdf" rel="nofollow">http://www.spry.org/pdf/website_creators_guide.pdf</a><br />
[2] <a href="http://otal.umd.edu/UUPractice/elderly/" rel="nofollow">http://otal.umd.edu/UUPractice/elderly/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility Barrier Scores by Kerry Webb</title>
		<link>http://www.dingoaccess.com/accessibility/accessibility-barrier-scores-2/comment-page-1/#comment-850</link>
		<dc:creator>Kerry Webb</dc:creator>
		<pubDate>Wed, 23 Nov 2011 22:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.dingoaccess.com/?p=647#comment-850</guid>
		<description>Bravo,Roger!  This is a very positive response to the problem of people with little real knowledge passing instant judgements on accessibility.

One such expert warned me that someone could lose their job for not putting in ALT text for an image.  What you&#039;ve proposed is sensible and useful.</description>
		<content:encoded><![CDATA[<p>Bravo,Roger!  This is a very positive response to the problem of people with little real knowledge passing instant judgements on accessibility.</p>
<p>One such expert warned me that someone could lose their job for not putting in ALT text for an image.  What you&#8217;ve proposed is sensible and useful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

