<?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; Touchscreens</title>
	<atom:link href="http://www.inclusivenewmedia.org/blog/category/id-accessible-websites/information-about-accessibility/touch-screens/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>Touchscreens</title>
		<link>http://www.inclusivenewmedia.org/blog/358/id-accessible-websites/information-about-accessibility/touchscreens/</link>
		<comments>http://www.inclusivenewmedia.org/blog/358/id-accessible-websites/information-about-accessibility/touchscreens/#comments</comments>
		<pubDate>Tue, 06 Oct 2009 19:53:53 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Information about accessibility]]></category>
		<category><![CDATA[Touchscreens]]></category>
		<category><![CDATA[Assistive Technologies]]></category>
		<category><![CDATA[touchscreens]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=358</guid>
		<description><![CDATA[Touchscreens are common place assistive devices for user with ID, due their immediacy compared to a standard mouse, which requires complex correction of control movement abstracted from the focus of interaction. Some operations, such as drag-and-drop, may also present a significant challenge to users with ID, even if modified pointing devices are available. 
touchscreentouchscreen
While essentially [...]]]></description>
			<content:encoded><![CDATA[<p>Touchscreens are common place assistive devices for user with ID, due their immediacy compared to a standard mouse, which requires complex correction of control movement abstracted from the focus of interaction. Some operations, such as drag-and-drop, may also present a significant challenge to users with ID, even if modified pointing devices are available. </p>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/10/touchscreen1.jpg" alt="touchscreen1" title="touchscreen1" width="280" height="190" class="alignnone size-full wp-image-740" />touchscreen</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/10/touchscreen2.jpg" alt="touchscreen2" title="touchscreen2" width="280" height="190" class="alignnone size-full wp-image-741" />touchscreen</span></p>
<p>While essentially just emulating a standard mouse and requiring no major technical adaptations per se, touchscreens have a few implications which developers and designers should account for:</p>
<ul>
<li><strong>Screen Resolution</strong><br />
Touchscreen users often use low screen resolutions such as 640x or 800x to increase the size and accessibility of clickable areas and prevent erroneous ‘clicks’. Pages which do not render fully in smaller viewports and require use of scrollbars will present barriers. Lower viewport widths should be supported without horizontal scrolling and in-page navigation using anchors employed to mitigate requirements to interact with vertical scrollbars or a keyboard.</li>
<li><strong>Button/Icon/Hotspot sizes</strong><br />
Since the hand and finger can often obscure the display during interaction, use of very small buttons, icons and links in close proximity should be avoided</li>
<li><strong>Mouse Button/Click Behaviour</strong><br />
In many circumstances actions should be mapped to mouse button press rather than release events – eg in Flash using the onPress rather than the default onRelease event handler will most often be required for time critical operations such as within games.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/358/id-accessible-websites/information-about-accessibility/touchscreens/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
