<?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 on: The Voiceover Screen ReaderComes to the iPhone</title>
	<atom:link href="http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/</link>
	<description>...extra! extra!...</description>
	<lastBuildDate>Mon, 17 Oct 2011 16:05:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: bertp001</title>
		<link>http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/comment-page-1/#comment-103</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Wed, 10 Jun 2009 17:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=395#comment-103</guid>
		<description>Some more observations about the iPhone 3GS.  I have seen and heard Apple&#039;s Quicktime release of the WWDC keynote speech.  First, I now realize VoiceOver accessibility is limited only to the &quot;S&quot; version.  Second, I wonder if the iPhone 3.0 Software Development Kit has some application programming interfaces available for some of the accessibility features of the iPhone 3GS.  Third, the iPhone 3GS has the ability to communicate with attachments through a software interface.  This should provide great potential for specialized devices of many types for greater accessibility.  Fourth,
the ability to locate an iPhone 3GS via the Apple MobileMe service would be a boon to everyone.  Plus the ability to wipe sensitive data is very useful.  Fifth, the compass function in conjunction with maps, and perhaps VoiceOver should be of help to more than the general public.  Sixth, the use of Bluetooth earphones, or wired earphones should allow VoiceOver and Voice Control users to have private use of their iPhone 3GS.  Eighth, in my opinion, Apple is leveraging their software accessibility tools among their range of hardware devices.  Note that the iPhone 3.0 Software Development Kit is derived from the Mac OS X operating system.  Ninth, if Apple can do this now, they can do more in the future, and they are clearly committed to accessibility.  Think of the multi-touch trackpad being extended.  Tenth,  Apple emphasizes great design for their hardware.  I think that emphasis spills over into software and accessibility.  Again, cheers!  I am going to have to become more proficient in VoiceOver.</description>
		<content:encoded><![CDATA[<p>Some more observations about the iPhone 3GS.  I have seen and heard Apple&#8217;s Quicktime release of the WWDC keynote speech.  First, I now realize VoiceOver accessibility is limited only to the &#8220;S&#8221; version.  Second, I wonder if the iPhone 3.0 Software Development Kit has some application programming interfaces available for some of the accessibility features of the iPhone 3GS.  Third, the iPhone 3GS has the ability to communicate with attachments through a software interface.  This should provide great potential for specialized devices of many types for greater accessibility.  Fourth,<br />
the ability to locate an iPhone 3GS via the Apple MobileMe service would be a boon to everyone.  Plus the ability to wipe sensitive data is very useful.  Fifth, the compass function in conjunction with maps, and perhaps VoiceOver should be of help to more than the general public.  Sixth, the use of Bluetooth earphones, or wired earphones should allow VoiceOver and Voice Control users to have private use of their iPhone 3GS.  Eighth, in my opinion, Apple is leveraging their software accessibility tools among their range of hardware devices.  Note that the iPhone 3.0 Software Development Kit is derived from the Mac OS X operating system.  Ninth, if Apple can do this now, they can do more in the future, and they are clearly committed to accessibility.  Think of the multi-touch trackpad being extended.  Tenth,  Apple emphasizes great design for their hardware.  I think that emphasis spills over into software and accessibility.  Again, cheers!  I am going to have to become more proficient in VoiceOver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bertp001</title>
		<link>http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/comment-page-1/#comment-102</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Tue, 09 Jun 2009 00:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=395#comment-102</guid>
		<description>I am impressed.  Porting VoiceOver to the iPhone 3G has to be considered a programming achievement.  For many visually-impaired people, it should provide access to the iPhone 3G if they apply effort and persistence to the learning task.  As for the general public, they benefit from Voice Control for automatic dialing and access to iTunes.

Likewise, extending VoiceOver in Mac OS X 10.6 to the multi-touch pad should be very helpful.  The Apple announcement also mentions VoiceOver Quick Nav for use on the keyboard for those without a multi-touch pad.

So far, no resolution independence in Mac OS X.  For many with poor vision, the smaller icons on higher-resolution screens can be quite a recognition problem.  But Apple has made a start in that direction as well, and I am hopeful resolution independence will be eventually be implemented.

Finally, I am of the view that the new accessibility technologies spill over to provide new programming functions usable for a wider audience than the visually-impaired.  For example, AppleScript GUI scripting is based on VoiceOver technology.
Consider the VoiceOver Kit for the iPod Shuffle.

Progress is being made.  Cheers!</description>
		<content:encoded><![CDATA[<p>I am impressed.  Porting VoiceOver to the iPhone 3G has to be considered a programming achievement.  For many visually-impaired people, it should provide access to the iPhone 3G if they apply effort and persistence to the learning task.  As for the general public, they benefit from Voice Control for automatic dialing and access to iTunes.</p>
<p>Likewise, extending VoiceOver in Mac OS X 10.6 to the multi-touch pad should be very helpful.  The Apple announcement also mentions VoiceOver Quick Nav for use on the keyboard for those without a multi-touch pad.</p>
<p>So far, no resolution independence in Mac OS X.  For many with poor vision, the smaller icons on higher-resolution screens can be quite a recognition problem.  But Apple has made a start in that direction as well, and I am hopeful resolution independence will be eventually be implemented.</p>
<p>Finally, I am of the view that the new accessibility technologies spill over to provide new programming functions usable for a wider audience than the visually-impaired.  For example, AppleScript GUI scripting is based on VoiceOver technology.<br />
Consider the VoiceOver Kit for the iPod Shuffle.</p>
<p>Progress is being made.  Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crister</title>
		<link>http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/comment-page-1/#comment-101</link>
		<dc:creator>crister</dc:creator>
		<pubDate>Mon, 08 Jun 2009 23:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=395#comment-101</guid>
		<description>on the surface, it sounds nice, but when applied to real world usage, voice command technology isn&#039;t as easy or a cure all as it first sounds. I&#039;m a very happy Mobile Speak Pocket and Voice Command user and even with those two programs running on my quadband HTC TYTN PDA, there are many times where because of the situation I&#039;m in, using Voice Command or MSP is impracticle. Either by ambient noise making it impossible to hear feedback, the same noise making it impossible for the program to understand what I&#039;m saying or situations where it just isnt&#039; appropriate to have a talking phone blathering on and on about battery life, caller information, text messages etc.   in a private or quiet business setting. Not to mention, I don&#039;t thinkn I&#039;d like for everyone to be able to hear my business. Whether it be who I&#039;m calling, Whose calling me, what I&#039;m browsing or whatever other tasks I&#039;m performing on my device.

The intention is good and of course go in the right direction, but I&#039;d imagine that initially, the accessibility features on the IPhone will be more gimmicky for the average sighted person and incredibly frustrating for a visually impaired one.

I think I&#039;m going to stick with my boring old Windows Mobiel based PDA and MSP for now. I love my qwerty keyboard and the flexibility that MSP offers. Not to mention all the blue tooth and not being locked into a crazy sim card or contract either. I&#039;m not ready to sacrifice functionality for flashiness just so I can brag about my brand new IPhone that may not be as accessible than my trusty PDA.

All that said, It&#039;s encouraging to hear that Apple is taking a greater interest in making it&#039;s various products more accessible. Regardless of what the initial steps towards accessibility they make, they&#039;re at the very least steps in the right direction.

Now, if only they&#039;d fix that terrible iTunes 8.2 update that they just put out and makes iTunes pretty much impossible for Jaws user to navigate things would be really encouraging.</description>
		<content:encoded><![CDATA[<p>on the surface, it sounds nice, but when applied to real world usage, voice command technology isn&#8217;t as easy or a cure all as it first sounds. I&#8217;m a very happy Mobile Speak Pocket and Voice Command user and even with those two programs running on my quadband HTC TYTN PDA, there are many times where because of the situation I&#8217;m in, using Voice Command or MSP is impracticle. Either by ambient noise making it impossible to hear feedback, the same noise making it impossible for the program to understand what I&#8217;m saying or situations where it just isnt&#8217; appropriate to have a talking phone blathering on and on about battery life, caller information, text messages etc.   in a private or quiet business setting. Not to mention, I don&#8217;t thinkn I&#8217;d like for everyone to be able to hear my business. Whether it be who I&#8217;m calling, Whose calling me, what I&#8217;m browsing or whatever other tasks I&#8217;m performing on my device.</p>
<p>The intention is good and of course go in the right direction, but I&#8217;d imagine that initially, the accessibility features on the IPhone will be more gimmicky for the average sighted person and incredibly frustrating for a visually impaired one.</p>
<p>I think I&#8217;m going to stick with my boring old Windows Mobiel based PDA and MSP for now. I love my qwerty keyboard and the flexibility that MSP offers. Not to mention all the blue tooth and not being locked into a crazy sim card or contract either. I&#8217;m not ready to sacrifice functionality for flashiness just so I can brag about my brand new IPhone that may not be as accessible than my trusty PDA.</p>
<p>All that said, It&#8217;s encouraging to hear that Apple is taking a greater interest in making it&#8217;s various products more accessible. Regardless of what the initial steps towards accessibility they make, they&#8217;re at the very least steps in the right direction.</p>
<p>Now, if only they&#8217;d fix that terrible iTunes 8.2 update that they just put out and makes iTunes pretty much impossible for Jaws user to navigate things would be really encouraging.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

