<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Inclusive New Media Design &#187; Screen readers and text helpers</title>
	<atom:link href="http://www.inclusivenewmedia.org/blog/category/id-accessible-websites/information-about-accessibility/screen-readers-and-text-helpers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inclusivenewmedia.org/blog</link>
	<description>including people with intellectual disabilities in the WWW</description>
	<lastBuildDate>Mon, 16 Nov 2009 14:38:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Screen Readers and Text Helpers</title>
		<link>http://www.inclusivenewmedia.org/blog/360/id-accessible-websites/information-about-accessibility/screen-readers-and-text-helpers/</link>
		<comments>http://www.inclusivenewmedia.org/blog/360/id-accessible-websites/information-about-accessibility/screen-readers-and-text-helpers/#comments</comments>
		<pubDate>Tue, 06 Oct 2009 19:54:52 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Information about accessibility]]></category>
		<category><![CDATA[Screen readers and text helpers]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=360</guid>
		<description><![CDATA[Screen reading software can often be of great facility to users with ID in supporting limited literacy, additional to mitigating the affect of visual impairment. We have yet to come across a user with significant ID capable of using full-featured interfaces such as JAWS or WindowsEyes, since the technical competencies and literacy required to access [...]]]></description>
			<content:encoded><![CDATA[<p>Screen reading software can often be of great facility to users with ID in supporting limited literacy, additional to mitigating the affect of visual impairment. We have yet to come across a user with significant ID capable of using full-featured interfaces such as JAWS or WindowsEyes, since the technical competencies and literacy required to access such applications are considerable. Nonetheless, it is likely that sites tested or developed with facilitation of these applications in mind are likely to provide a better experience for users relying on more basic text helpers.</p>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/AT-screenreader.jpg" alt="AT-screenreader" title="AT-screenreader" width="147" height="100" class="alignnone size-full wp-image-733" />screen reader</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/10/txt2speech.jpg" alt="txt2speech" title="txt2speech" width="280" height="190" class="alignnone size-full wp-image-757" />text-to-speech</span></p>
<p>Simpler applications, working transparently to convert text-to-speech and providing more selective announcement of semantic elements, are likely to be the most effective solutions for ID users. Provision of text-to-speech server-side may also be a preferred solution for developers, particularly if a predictable, testable and consistent approach is required for their audience. Numerous text-helper and server-side tools exist, some of which are free to end users, the most common we have encountered are summarised on the &#8216;text-to-speech applications&#8217; page.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/360/id-accessible-websites/information-about-accessibility/screen-readers-and-text-helpers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
