<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: The Inaccessibility of Automated Accessibility Tools</title>
	<atom:link href="http://universallydesigned.net/standards/the-inaccessibility-of-accessibility-toolbars/feed/" rel="self" type="application/rss+xml" />
	<link>http://universallydesigned.net/standards/the-inaccessibility-of-accessibility-toolbars/</link>
	<description>Knowbility blogs about technology that everyone can use.</description>
	<lastBuildDate>Fri, 19 Feb 2010 07:49:10 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Karl Groves</title>
		<link>http://universallydesigned.net/standards/the-inaccessibility-of-accessibility-toolbars/comment-page-1/#comment-1113</link>
		<dc:creator>Karl Groves</dc:creator>
		<pubDate>Wed, 06 Jan 2010 17:05:16 +0000</pubDate>
		<guid isPermaLink="false">http://universallydesigned.net/?p=156#comment-1113</guid>
		<description>Desiree,

First, thanks for mentioning AMP Express in your post! 

Accessibility testing tools abound these days, especially for testing websites.  Much can be done to provide an assessment of a website for accessibility using automated means and most of the tools out there will provide the same level of quality with respect to their results because, frankly, they (we?) all test for the same things using much the same methods.   Unfortunately, automated testing - regardless of the tool - can only get you about 20% of the data necessary for one to make an informed decision of how accessible your cite is.  The rest of the process is manual.

There are numerous ways to test using non-automated means, ranging from manual code inspection to manipulation of browser settings, manipulation of hardware settings, use of assistive technologies, or simple things like using a keyboard only to navigate.   Additionally, an audit is not complete without performing use case testing with actual users of assistive technologies completing typical system tasks.

Clearly, toolbars fit squarely in with the manual inspection process.  Many of the toolbars out there will provide you with good results specific to the things they can test for, be it the WAVE toolbar, the Firefox Accessibility toolbar, or something else.  Regarding your question about these toolbars&#039; level of accessibility, I have no specific knowledge of them though given their context-of-use I&#039;d be shocked if they weren&#039;t themselves accessible.

Here at SSB BART Group, we include the InFocus Toolbar for IE with all licenses of our Accessibility Management Platform (Better known as AMP: http://amp.ssbbartgroup.com).  The InFocus Toolbar is meant as a complimentary tool to help the web accessibility auditing process be more efficient for users of AMP and can do loads of things all the other toolbars can do, such as turning on &amp; off stylesheets, turning on &amp; off JavaScript, grayscale previews, text-only view, view header info, and so on.  Additionally, it performs screen captures and captures of the live DOM (including session-based capture) to assist in your auditing.   

SSB BART Group has more than 8 blind or low-vision client services employees who use the InFocus Toolbar on a daily basis, so we know it is accessible too! 

Hope this helps.</description>
		<content:encoded><![CDATA[<p>Desiree,</p>
<p>First, thanks for mentioning AMP Express in your post! </p>
<p>Accessibility testing tools abound these days, especially for testing websites.  Much can be done to provide an assessment of a website for accessibility using automated means and most of the tools out there will provide the same level of quality with respect to their results because, frankly, they (we?) all test for the same things using much the same methods.   Unfortunately, automated testing &#8211; regardless of the tool &#8211; can only get you about 20% of the data necessary for one to make an informed decision of how accessible your cite is.  The rest of the process is manual.</p>
<p>There are numerous ways to test using non-automated means, ranging from manual code inspection to manipulation of browser settings, manipulation of hardware settings, use of assistive technologies, or simple things like using a keyboard only to navigate.   Additionally, an audit is not complete without performing use case testing with actual users of assistive technologies completing typical system tasks.</p>
<p>Clearly, toolbars fit squarely in with the manual inspection process.  Many of the toolbars out there will provide you with good results specific to the things they can test for, be it the WAVE toolbar, the Firefox Accessibility toolbar, or something else.  Regarding your question about these toolbars&#8217; level of accessibility, I have no specific knowledge of them though given their context-of-use I&#8217;d be shocked if they weren&#8217;t themselves accessible.</p>
<p>Here at SSB BART Group, we include the InFocus Toolbar for IE with all licenses of our Accessibility Management Platform (Better known as AMP: <a href="http://amp.ssbbartgroup.com)" rel="nofollow">http://amp.ssbbartgroup.com)</a>.  The InFocus Toolbar is meant as a complimentary tool to help the web accessibility auditing process be more efficient for users of AMP and can do loads of things all the other toolbars can do, such as turning on &amp; off stylesheets, turning on &amp; off JavaScript, grayscale previews, text-only view, view header info, and so on.  Additionally, it performs screen captures and captures of the live DOM (including session-based capture) to assist in your auditing.   </p>
<p>SSB BART Group has more than 8 blind or low-vision client services employees who use the InFocus Toolbar on a daily basis, so we know it is accessible too! </p>
<p>Hope this helps.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
