<?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 Lioncourt.com</title>
	<atom:link href="http://www.lioncourt.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lioncourt.com</link>
	<description>Mac-cessibility News</description>
	<lastBuildDate>Sun, 28 Jun 2009 01:41:17 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on The Mac-cessibility Round Table Podcast SE #2 &#8212; More Than Meets the iPhone by TVSoundGuy</title>
		<link>http://www.lioncourt.com/2009/06/23/the-mac-cessibility-round-table-podcast-se-2-more-than-meets-the-iphone/comment-page-1/#comment-193</link>
		<dc:creator>TVSoundGuy</dc:creator>
		<pubDate>Sun, 28 Jun 2009 01:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=411#comment-193</guid>
		<description>Greetings all,

I recently took a trip to my local apple store and asked to see the 3GS with Voiceover on it. The store staff were well-informed and brought me over to a phone. Unfortunatley, the phone on display was running a demo version of the iPhone OS X software. This meant Voiceover started and I could run my finger over the display, but it did not let us switch applications so I could try Mail or Safari.

The Lead Creative at the store, a nice woman named Kristy, was very apologetic and offered to have a fully functional phone brought into the store so I could try it. She then proposed that once the phone was brought in, that we sit down for 30 minutes so I could learn how the phone worked. (Although, I think they wanted to see how Voiceover functioned for themselves alongside a blind user.) I will gladly report my experiences here and on my radio show.

I fully nominate Josh and Cara as the Neil Armstrong and Buzz Aldrin of the accessibility features of the iPhone 3GS. 

I&#039;m so pleased to see Apple&#039;s inginuity and creativity continue with the iPhone in addition to the other Apple products that are changing lives. I am anxiously awaiting my Mac Book Pro in two days and will have a homecoming ceremony for myself as I am finally repatriating myself back to mac after 12 years of swimming in shark-infested waters on the PC side. (wink, wink)

Again, great job and thank you for blazing the trail.</description>
		<content:encoded><![CDATA[<p>Greetings all,</p>
<p>I recently took a trip to my local apple store and asked to see the 3GS with Voiceover on it. The store staff were well-informed and brought me over to a phone. Unfortunatley, the phone on display was running a demo version of the iPhone OS X software. This meant Voiceover started and I could run my finger over the display, but it did not let us switch applications so I could try Mail or Safari.</p>
<p>The Lead Creative at the store, a nice woman named Kristy, was very apologetic and offered to have a fully functional phone brought into the store so I could try it. She then proposed that once the phone was brought in, that we sit down for 30 minutes so I could learn how the phone worked. (Although, I think they wanted to see how Voiceover functioned for themselves alongside a blind user.) I will gladly report my experiences here and on my radio show.</p>
<p>I fully nominate Josh and Cara as the Neil Armstrong and Buzz Aldrin of the accessibility features of the iPhone 3GS. </p>
<p>I&#8217;m so pleased to see Apple&#8217;s inginuity and creativity continue with the iPhone in addition to the other Apple products that are changing lives. I am anxiously awaiting my Mac Book Pro in two days and will have a homecoming ceremony for myself as I am finally repatriating myself back to mac after 12 years of swimming in shark-infested waters on the PC side. (wink, wink)</p>
<p>Again, great job and thank you for blazing the trail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Review &#8212; The Accessible iPhone 3GS by bertp001</title>
		<link>http://www.lioncourt.com/2009/06/25/review-the-accessible-iphone-3gs/comment-page-1/#comment-192</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Fri, 26 Jun 2009 02:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=429#comment-192</guid>
		<description>Very helpful review.  I liked the discussion about how to approach the learning process for the new accessibility techniques available on the iPhone 3G S.  During the WWDC keynote speech, I was especially excited about the apparent thought Apple has given to  iPhone 3G S attachments.  That is good architecture.  The general public, from what I have read, still does not appreciate how they too will benefit.  For example, Voice Control 1.0 may be a fresh start in voice recognition that could be extended across the Apple line of products.  Time will tell.  Apple is already moving way ahead of their competition in my view.</description>
		<content:encoded><![CDATA[<p>Very helpful review.  I liked the discussion about how to approach the learning process for the new accessibility techniques available on the iPhone 3G S.  During the WWDC keynote speech, I was especially excited about the apparent thought Apple has given to  iPhone 3G S attachments.  That is good architecture.  The general public, from what I have read, still does not appreciate how they too will benefit.  For example, Voice Control 1.0 may be a fresh start in voice recognition that could be extended across the Apple line of products.  Time will tell.  Apple is already moving way ahead of their competition in my view.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mac-cessibility Round Table Podcast SE #2 &#8212; More Than Meets the iPhone by ecardoshinsky</title>
		<link>http://www.lioncourt.com/2009/06/23/the-mac-cessibility-round-table-podcast-se-2-more-than-meets-the-iphone/comment-page-1/#comment-191</link>
		<dc:creator>ecardoshinsky</dc:creator>
		<pubDate>Tue, 23 Jun 2009 21:35:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=411#comment-191</guid>
		<description>Nice thing about the iphone app store, you can rate apps and leave reviews on their accessibility.  I bet you would get some respoonsive updates.


You don&#039;t have to hold both the home and lock key down.  Just hold the lock key down for a few seconds.  Then there is a slider toward the top to power down the phone.  You may need to practice until you can orient yourselves without VO in case of a crash like was mentioned.  You know, practice with VO to get the muscle memory down.

You have to double tap the characters/edit text to enable cut copy paste.  So if there is a pass through feature, you may be able to use that to access cut/copy and paste.  Basically, get focus in the edit field then hit the pass through function, then double tap in the edit field.  The cut/copy and paste appear sort of like bubbles with the text selected for operation.  If you use more fingers you get more text.</description>
		<content:encoded><![CDATA[<p>Nice thing about the iphone app store, you can rate apps and leave reviews on their accessibility.  I bet you would get some respoonsive updates.</p>
<p>You don&#8217;t have to hold both the home and lock key down.  Just hold the lock key down for a few seconds.  Then there is a slider toward the top to power down the phone.  You may need to practice until you can orient yourselves without VO in case of a crash like was mentioned.  You know, practice with VO to get the muscle memory down.</p>
<p>You have to double tap the characters/edit text to enable cut copy paste.  So if there is a pass through feature, you may be able to use that to access cut/copy and paste.  Basically, get focus in the edit field then hit the pass through function, then double tap in the edit field.  The cut/copy and paste appear sort of like bubbles with the text selected for operation.  If you use more fingers you get more text.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 and Accessibility by Chris</title>
		<link>http://www.lioncourt.com/2009/06/14/safari-4-and-accessibility/comment-page-1/#comment-190</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 21 Jun 2009 02:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=403#comment-190</guid>
		<description>I have just updated to the latest version of Safari and I&#039;m glad to have had the foresight to read this post before visiting the ITunes store. You didn&#039;t specifically mention the ITunes store but your reference to &quot;online store pages&quot; has made me somewhat apprehensive about browsing for new podcasts.</description>
		<content:encoded><![CDATA[<p>I have just updated to the latest version of Safari and I&#8217;m glad to have had the foresight to read this post before visiting the ITunes store. You didn&#8217;t specifically mention the ITunes store but your reference to &#8220;online store pages&#8221; has made me somewhat apprehensive about browsing for new podcasts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CNet&#8217;s iPhone 3G S Review Discusses Accessibility by bertp001</title>
		<link>http://www.lioncourt.com/2009/06/17/cnets-iphone-3g-s-review-discusses-accessibility/comment-page-1/#comment-188</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Thu, 18 Jun 2009 16:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=409#comment-188</guid>
		<description>Some additional comments.  First, the capabilities of the processor and the random access memory (not flash memory for photos and songs) in the iPhone 3G S provides support for VoiceOver, Zoom, White-On-Black, and Voice Control. The less capable iPhone 3G and iPod Touch devices do not support these software features.  Second, both the iPhone and iPod Touch have iPhone 3.0 software, an adaptation of Mac OS X Cocoa frameworks software.  Third, it seems reasonable to expect that future models of the iPhone and iPod Touch with more capable processors and more random access memory will support the accessibility features now available in the iPhone 3G S.  Fourth,  the iPhone 3.0 software development kit (SDK) supports accessibility user interface elements (objects) in a manner similar to the Mac OS X Cocoa frameworks, keeping in mind the adaptation needed for handheld devices like the iPhone and iPod Touch.  Fifth, third-party developers of applications for the iPhone (and maybe the iPod Touch in the future) will have accessibility support available for their use built-in to the iPhone 3.0 SDK.  This means that the third-party applications can have accessibility support automatically.  These developers may need do some additional work to support unique aspects of their applications, especially like hardware attachments to the IPhone 3G S.  Sixth, multi-touch trackpad support on recent Apple laptops are using an adaptation of multi-touch technologies that originated with the iPhone.  Seventh, from an architectural point of view, some of Apple&#039;s accessibility technologies, in my opinion, are now cross-platform.  The list now includes at minimum VoiceOver, Zoom, White-On-Black, multi-touch trackpad, and maybe Voice Control (meaning a speech recognition technology).  In the future, this list could be extended because the Macintosh line of computers and the iPhone and iPod Touch handheld computers have an underlying common software base, although with adaptations and limitations.  Disclaimer: I do not have special access to Apple software.  I can and do look at the Apple Developer Connection manuals at the base level, which is free to everyone.</description>
		<content:encoded><![CDATA[<p>Some additional comments.  First, the capabilities of the processor and the random access memory (not flash memory for photos and songs) in the iPhone 3G S provides support for VoiceOver, Zoom, White-On-Black, and Voice Control. The less capable iPhone 3G and iPod Touch devices do not support these software features.  Second, both the iPhone and iPod Touch have iPhone 3.0 software, an adaptation of Mac OS X Cocoa frameworks software.  Third, it seems reasonable to expect that future models of the iPhone and iPod Touch with more capable processors and more random access memory will support the accessibility features now available in the iPhone 3G S.  Fourth,  the iPhone 3.0 software development kit (SDK) supports accessibility user interface elements (objects) in a manner similar to the Mac OS X Cocoa frameworks, keeping in mind the adaptation needed for handheld devices like the iPhone and iPod Touch.  Fifth, third-party developers of applications for the iPhone (and maybe the iPod Touch in the future) will have accessibility support available for their use built-in to the iPhone 3.0 SDK.  This means that the third-party applications can have accessibility support automatically.  These developers may need do some additional work to support unique aspects of their applications, especially like hardware attachments to the IPhone 3G S.  Sixth, multi-touch trackpad support on recent Apple laptops are using an adaptation of multi-touch technologies that originated with the iPhone.  Seventh, from an architectural point of view, some of Apple&#8217;s accessibility technologies, in my opinion, are now cross-platform.  The list now includes at minimum VoiceOver, Zoom, White-On-Black, multi-touch trackpad, and maybe Voice Control (meaning a speech recognition technology).  In the future, this list could be extended because the Macintosh line of computers and the iPhone and iPod Touch handheld computers have an underlying common software base, although with adaptations and limitations.  Disclaimer: I do not have special access to Apple software.  I can and do look at the Apple Developer Connection manuals at the base level, which is free to everyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CNet&#8217;s iPhone 3G S Review Discusses Accessibility by bertp001</title>
		<link>http://www.lioncourt.com/2009/06/17/cnets-iphone-3g-s-review-discusses-accessibility/comment-page-1/#comment-187</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Wed, 17 Jun 2009 23:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=409#comment-187</guid>
		<description>I read this CNET review.  It was very helpful.  Not everyone uses VoiceOver, but instead use Zoom in combination with White-On-Black.  Wow! The new iPhone 3GS has Zoom and White-On-Black support as well.  Plus, I like the landscape keyboard being extended to other applications.  So, I might wait awhile for a cheaper price, but I know it is doable for me.  Cheers!  I&#039;m pleased about what I read about VoiceOver as well.  Cheers again!</description>
		<content:encoded><![CDATA[<p>I read this CNET review.  It was very helpful.  Not everyone uses VoiceOver, but instead use Zoom in combination with White-On-Black.  Wow! The new iPhone 3GS has Zoom and White-On-Black support as well.  Plus, I like the landscape keyboard being extended to other applications.  So, I might wait awhile for a cheaper price, but I know it is doable for me.  Cheers!  I&#8217;m pleased about what I read about VoiceOver as well.  Cheers again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Safari 4 and Accessibility by Jake</title>
		<link>http://www.lioncourt.com/2009/06/14/safari-4-and-accessibility/comment-page-1/#comment-186</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Mon, 15 Jun 2009 03:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=403#comment-186</guid>
		<description>Regarding the crash on the Apple Store pages, as well as a few others, Apple has already fixed this in the most recent builds of Webkit, and they should have a fix out for the general release of Safari 4.0 very soon according to their accessibility folks. They definitely realize this is a major problem, and it is obviously a rather serious regression. One would&#039;ve thought they&#039;d at least use some of their own store pages to test out Voiceover before releasing Safari 4, considering there&#039;s some rather complex scriptlets on that page they&#039;d want to make sure were read by Voiceover for their own site in addition to where similar scripts are used on other pages. The good thing is that they&#039;re on top of it and have the issue resolved, let&#039;s just hope they backport the fix to the system-wide Webkit used by Safari very soon.
It is a bit worrying, for those just trying out Safari 4 and Voiceover it will not leave a good impression, and we all know that first impressions carry a great deal of weight when someone is first using any new bit of technology and, coupled with all the misinformation out there... let&#039;s just say further testing with Voiceover before release would have been a very good idea.</description>
		<content:encoded><![CDATA[<p>Regarding the crash on the Apple Store pages, as well as a few others, Apple has already fixed this in the most recent builds of Webkit, and they should have a fix out for the general release of Safari 4.0 very soon according to their accessibility folks. They definitely realize this is a major problem, and it is obviously a rather serious regression. One would&#8217;ve thought they&#8217;d at least use some of their own store pages to test out Voiceover before releasing Safari 4, considering there&#8217;s some rather complex scriptlets on that page they&#8217;d want to make sure were read by Voiceover for their own site in addition to where similar scripts are used on other pages. The good thing is that they&#8217;re on top of it and have the issue resolved, let&#8217;s just hope they backport the fix to the system-wide Webkit used by Safari very soon.<br />
It is a bit worrying, for those just trying out Safari 4 and Voiceover it will not leave a good impression, and we all know that first impressions carry a great deal of weight when someone is first using any new bit of technology and, coupled with all the misinformation out there&#8230; let&#8217;s just say further testing with Voiceover before release would have been a very good idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Voiceover Screen ReaderComes to the iPhone by bertp001</title>
		<link>http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/comment-page-1/#comment-185</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-185</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>Comment on The Voiceover Screen ReaderComes to the iPhone by bertp001</title>
		<link>http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/comment-page-1/#comment-184</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-184</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>Comment on The Voiceover Screen ReaderComes to the iPhone by crister</title>
		<link>http://www.lioncourt.com/2009/06/08/the-voiceover-screen-readercomes-to-the-iphone/comment-page-1/#comment-183</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-183</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>
	<item>
		<title>Comment on WWDC Keynote to Showcase Snow Leopard, Including Accessibility by Chris</title>
		<link>http://www.lioncourt.com/2009/05/13/wwdc-keynote-to-showcase-snow-leopard-including-accessibility/comment-page-1/#comment-182</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 27 May 2009 23:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=379#comment-182</guid>
		<description>I have heard rumors of greater accessibility with Snow Leopard and I&#039;m glad to know that those rumors are true. I&#039;ve heard another rumor that might not be such good news if it&#039;s true. It is my impression that older Mac Minis won&#039;t support an upgrade to Snow Leopard. Maybe you&#039;ll be able to write an editorial on Snow Leopard as we learn more about it.</description>
		<content:encoded><![CDATA[<p>I have heard rumors of greater accessibility with Snow Leopard and I&#8217;m glad to know that those rumors are true. I&#8217;ve heard another rumor that might not be such good news if it&#8217;s true. It is my impression that older Mac Minis won&#8217;t support an upgrade to Snow Leopard. Maybe you&#8217;ll be able to write an editorial on Snow Leopard as we learn more about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WWDC Keynote to Showcase Snow Leopard, Including Accessibility by bertp001</title>
		<link>http://www.lioncourt.com/2009/05/13/wwdc-keynote-to-showcase-snow-leopard-including-accessibility/comment-page-1/#comment-180</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Wed, 13 May 2009 23:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=379#comment-180</guid>
		<description>I am looking forward to this announcement.  I have thought that the new generation iPod Shuffle hinted at new accessibility technologies under development at Apple.</description>
		<content:encoded><![CDATA[<p>I am looking forward to this announcement.  I have thought that the new generation iPod Shuffle hinted at new accessibility technologies under development at Apple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Updates VoiceOver Kit for the iPod Shuffle 3G by Lioncourt</title>
		<link>http://www.lioncourt.com/2009/04/10/apple-updates-voiceover-kit-for-the-ipod-shuffle-3g/comment-page-1/#comment-179</link>
		<dc:creator>Lioncourt</dc:creator>
		<pubDate>Fri, 10 Apr 2009 23:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=373#comment-179</guid>
		<description>That was never really in doubt, I think. The technology used in the VoiceOver Kit is substantially different than that used in VoiceOver for Mac OS X. Think of it like Safari and Safari Mobile for the iPhone/iPod Touch. Both share some similarities, but they are clearly separate products on separate development cycles.</description>
		<content:encoded><![CDATA[<p>That was never really in doubt, I think. The technology used in the VoiceOver Kit is substantially different than that used in VoiceOver for Mac OS X. Think of it like Safari and Safari Mobile for the iPhone/iPod Touch. Both share some similarities, but they are clearly separate products on separate development cycles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Updates VoiceOver Kit for the iPod Shuffle 3G by bertp001</title>
		<link>http://www.lioncourt.com/2009/04/10/apple-updates-voiceover-kit-for-the-ipod-shuffle-3g/comment-page-1/#comment-178</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Fri, 10 Apr 2009 22:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=373#comment-178</guid>
		<description>So now it is clear that the VoiceOver Utility and the VoiceOver Kit are on separate development tracks.  Each has it&#039;s own release number.</description>
		<content:encoded><![CDATA[<p>So now it is clear that the VoiceOver Utility and the VoiceOver Kit are on separate development tracks.  Each has it&#8217;s own release number.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMWare Releases Fusion 2.0 for Mac with Accessibility by knackslash</title>
		<link>http://www.lioncourt.com/2008/09/16/vmware-releases-fusion-20-for-mac-with-accessibility/comment-page-1/#comment-177</link>
		<dc:creator>knackslash</dc:creator>
		<pubDate>Fri, 10 Apr 2009 20:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=177#comment-177</guid>
		<description>Hello!
 
First of all, as a blind, originally 100% MS-DOS / Windows user who never imagined that the Mac could ever become accessible one day, I&#039;d like to thank all of those who regularly contribute to your site and keep on expanding people&#039;s potential in using VoiceOver! Even more so as you in America and other English-speaking countries seem to be miles ahead of what we are currently in France. At my local Apple store, for example, they just didn&#039;t know anything about Mac OS X&#039;s built-in Universal Access features, so I had to demonstrate them how to turn on VoiceOver and the system zoom in order to show them that it might not be such a silly idea for a blind guy to become an Apple customer...!

However, in order for me to make the switch almost perfect and say good bye to my PC once for all, perhaps with VMware, Windows and/or Jaws for a transitional phase, I still got 3 questions for the moment, and I would be very grateful if you could help me get the best out of my Mac &amp; the few Windows programs I still need from time to time as a professional translator.

To be more specific, I&#039;m currently working both on a rapidly aging Dell notebook on Windows XP SP3 and Jaws 9 - &quot;desperately&quot; waiting for Jaws 10 to be released in my country, which may still take several months- and a 24-inch iMac on a French version of Mac OS X Leopard (10.5.6) with VoiceOver and the system zoom turned on, using Alex for English contents and Assistiveware&#039;s Infovox iVox voices for French, German and Spanish texts, since Alex is only available in American English for now. Two months ago, I also bought Nippon Telesoft&#039;s Seika 40 Braille display, which actually works greater on the Mac than on the Dell notebook. Though I&#039;m quite happy with VoiceOver to read texts and accessible, well-structured pages like this one, record / work on audio files, start working on Garage Band after I read the great tutorial on this site, manage a fast-growing, multi-format media library much better than in Winamp, etc., I still can&#039;t give up my PC once for all, since VoiceOver is still unable to read Flash contents, to render complex web sites quickly enough or to handle language recognition on web sites, while Assistiveware&#039;s voices seem to need so many resources that VoiceOver would regularly lose track with the keyboard focus and get me to waste some time returning where I originally intended to go. Which makes it a bit hard and tricky to use in a multinational professional environment like mine, where time is money.

Therefore, I&#039;m planning to run Windows XP or Vista on my iMac, depending on which system is supposed to be more reliable and compatible with AT used in combination with Firefox / Internet Explorer, Microsoft Office, OpenOffice and some CD-ROM dictionaries...
So, here are my questions.
 
1. What&#039;s the basic difference between VMware Fusion, Parallels Desktop and maybe some other virtualisation software?
2. Since I will definitely need a screen reader to get access to Windows contents, do I absolutely have to install Jaws or does VoiceOver fully support the Windows interface generated through VMware Fusion or Parallels Desktop, allowing me, for instance, to use Microsoft Word for Windows with usual VO commands as I would in Nisus Writer Pro?
3. Should I need to have Jaws installed on my Mac, could you tell me if you have ever had any specific experience with an iMac? Otherwise, should I rather sell both PC and iMac and buy a brand-new MacPro, MacBook or MacBook Pro instead, as so many people use to say that Windows runs better on these machines, which may also be true for the kind of graphic card support that is so critical to AT in general, and Jaws in particular, or even consider installing a Linux distribution like Fedora, since Linux is also said to come with some screen-reading features and Braille display drivers?

Anyway, just in case these details were of any importance, the basic / graphic card specs of my iMac are as follows:

Model ID: iMac 6.1;
Processor / memory: Intel Core 2 Duo running at 2.16 GHz, with 2.5 GB of RAM;
SMC version: 1.10f3;
Graphic card: NVIDIA GeForce 7300 GT;
Built-in 24-inch LCD monitor with Core Image hardware acceleration;
Screen resolution: 1920 x 1200;
Mirror: off.

Thanks in advance for your answers, sorry for leaving such a long comment (but I thought it might be important to be as specific as possible), and good luck for the future of the Mac-cessibility site!
Best regards.
Knackslash</description>
		<content:encoded><![CDATA[<p>Hello!</p>
<p>First of all, as a blind, originally 100% MS-DOS / Windows user who never imagined that the Mac could ever become accessible one day, I&#8217;d like to thank all of those who regularly contribute to your site and keep on expanding people&#8217;s potential in using VoiceOver! Even more so as you in America and other English-speaking countries seem to be miles ahead of what we are currently in France. At my local Apple store, for example, they just didn&#8217;t know anything about Mac OS X&#8217;s built-in Universal Access features, so I had to demonstrate them how to turn on VoiceOver and the system zoom in order to show them that it might not be such a silly idea for a blind guy to become an Apple customer&#8230;!</p>
<p>However, in order for me to make the switch almost perfect and say good bye to my PC once for all, perhaps with VMware, Windows and/or Jaws for a transitional phase, I still got 3 questions for the moment, and I would be very grateful if you could help me get the best out of my Mac &amp; the few Windows programs I still need from time to time as a professional translator.</p>
<p>To be more specific, I&#8217;m currently working both on a rapidly aging Dell notebook on Windows XP SP3 and Jaws 9 &#8211; &#8220;desperately&#8221; waiting for Jaws 10 to be released in my country, which may still take several months- and a 24-inch iMac on a French version of Mac OS X Leopard (10.5.6) with VoiceOver and the system zoom turned on, using Alex for English contents and Assistiveware&#8217;s Infovox iVox voices for French, German and Spanish texts, since Alex is only available in American English for now. Two months ago, I also bought Nippon Telesoft&#8217;s Seika 40 Braille display, which actually works greater on the Mac than on the Dell notebook. Though I&#8217;m quite happy with VoiceOver to read texts and accessible, well-structured pages like this one, record / work on audio files, start working on Garage Band after I read the great tutorial on this site, manage a fast-growing, multi-format media library much better than in Winamp, etc., I still can&#8217;t give up my PC once for all, since VoiceOver is still unable to read Flash contents, to render complex web sites quickly enough or to handle language recognition on web sites, while Assistiveware&#8217;s voices seem to need so many resources that VoiceOver would regularly lose track with the keyboard focus and get me to waste some time returning where I originally intended to go. Which makes it a bit hard and tricky to use in a multinational professional environment like mine, where time is money.</p>
<p>Therefore, I&#8217;m planning to run Windows XP or Vista on my iMac, depending on which system is supposed to be more reliable and compatible with AT used in combination with Firefox / Internet Explorer, Microsoft Office, OpenOffice and some CD-ROM dictionaries&#8230;<br />
So, here are my questions.</p>
<p>1. What&#8217;s the basic difference between VMware Fusion, Parallels Desktop and maybe some other virtualisation software?<br />
2. Since I will definitely need a screen reader to get access to Windows contents, do I absolutely have to install Jaws or does VoiceOver fully support the Windows interface generated through VMware Fusion or Parallels Desktop, allowing me, for instance, to use Microsoft Word for Windows with usual VO commands as I would in Nisus Writer Pro?<br />
3. Should I need to have Jaws installed on my Mac, could you tell me if you have ever had any specific experience with an iMac? Otherwise, should I rather sell both PC and iMac and buy a brand-new MacPro, MacBook or MacBook Pro instead, as so many people use to say that Windows runs better on these machines, which may also be true for the kind of graphic card support that is so critical to AT in general, and Jaws in particular, or even consider installing a Linux distribution like Fedora, since Linux is also said to come with some screen-reading features and Braille display drivers?</p>
<p>Anyway, just in case these details were of any importance, the basic / graphic card specs of my iMac are as follows:</p>
<p>Model ID: iMac 6.1;<br />
Processor / memory: Intel Core 2 Duo running at 2.16 GHz, with 2.5 GB of RAM;<br />
SMC version: 1.10f3;<br />
Graphic card: NVIDIA GeForce 7300 GT;<br />
Built-in 24-inch LCD monitor with Core Image hardware acceleration;<br />
Screen resolution: 1920 x 1200;<br />
Mirror: off.</p>
<p>Thanks in advance for your answers, sorry for leaving such a long comment (but I thought it might be important to be as specific as possible), and good luck for the future of the Mac-cessibility site!<br />
Best regards.<br />
Knackslash</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple Updates iTunes to Version 8.1.1 With Accessibility Fixes by ecardoshinsky</title>
		<link>http://www.lioncourt.com/2009/04/06/apple-updates-itunes-to-version-811/comment-page-1/#comment-176</link>
		<dc:creator>ecardoshinsky</dc:creator>
		<pubDate>Mon, 06 Apr 2009 21:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=359#comment-176</guid>
		<description>Hopefully they will fix that, &quot;man we shouldn&#039;t have shipped this with this type of bug&quot; bug, where if you try and use itunes DJ, it only plays one song then hangs.  Also, if they fixed anything for ipod touch/iphone it is the syncing interface that works fine if an ipod is connected but the interface for iphone/touch is not accessbile with voiceover.  Voiceover simply has no clue it is there.</description>
		<content:encoded><![CDATA[<p>Hopefully they will fix that, &#8220;man we shouldn&#8217;t have shipped this with this type of bug&#8221; bug, where if you try and use itunes DJ, it only plays one song then hangs.  Also, if they fixed anything for ipod touch/iphone it is the syncing interface that works fine if an ipod is connected but the interface for iphone/touch is not accessbile with voiceover.  Voiceover simply has no clue it is there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Talking Email Keyboard for iPhone by 8string</title>
		<link>http://www.lioncourt.com/2009/03/24/talking-email-keyboard-for-iphone/comment-page-1/#comment-175</link>
		<dc:creator>8string</dc:creator>
		<pubDate>Thu, 26 Mar 2009 01:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=347#comment-175</guid>
		<description>Sorry, I forgot to add a YouTube video of the Rim, something you could listen to, if you want a nice overview of the phone. This is out of the UK, and is 9 minutes in depth. 

http://www.youtube.com/watch?v=IqONSAe81sE</description>
		<content:encoded><![CDATA[<p>Sorry, I forgot to add a YouTube video of the Rim, something you could listen to, if you want a nice overview of the phone. This is out of the UK, and is 9 minutes in depth. </p>
<p><a href="http://www.youtube.com/watch?v=IqONSAe81sE" rel="nofollow">http://www.youtube.com/watch?v=IqONSAe81sE</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Talking Email Keyboard for iPhone by 8string</title>
		<link>http://www.lioncourt.com/2009/03/24/talking-email-keyboard-for-iphone/comment-page-1/#comment-174</link>
		<dc:creator>8string</dc:creator>
		<pubDate>Thu, 26 Mar 2009 01:54:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=347#comment-174</guid>
		<description>I use the iPhone and I would have to say it seems like the least friendly phone device for the visually impaired. I would probably look at the recent Blackberry Rim Bold with a great keyboard.I don&#039;t know if the screen has any ability to help the visually impaired, but if I didn&#039;t have sight I would be looking at having a keyboard that I could touch. For what it&#039;s worth. I have no financial interest in Rim.</description>
		<content:encoded><![CDATA[<p>I use the iPhone and I would have to say it seems like the least friendly phone device for the visually impaired. I would probably look at the recent Blackberry Rim Bold with a great keyboard.I don&#8217;t know if the screen has any ability to help the visually impaired, but if I didn&#8217;t have sight I would be looking at having a keyboard that I could touch. For what it&#8217;s worth. I have no financial interest in Rim.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Talking Email Keyboard for iPhone by bertp001</title>
		<link>http://www.lioncourt.com/2009/03/24/talking-email-keyboard-for-iphone/comment-page-1/#comment-173</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Tue, 24 Mar 2009 20:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=347#comment-173</guid>
		<description>Thanks for the information.  I have some vision, but would have a problem with an iPhone with its current set of functions.  Yes, another accessibility problem has been mitigated.

There is a hearing aid (I have a hearing loss as well) with an optional Bluetooth receiver to wear around your neck.  The receiver converts Bluetooth signals into another signal format for re-transmission directly to the right and left hearing aids.  But this option for wirelessly connecting to an iPhone or your computer via Bluetooth is expensive, so I declined this option.  Maybe later.</description>
		<content:encoded><![CDATA[<p>Thanks for the information.  I have some vision, but would have a problem with an iPhone with its current set of functions.  Yes, another accessibility problem has been mitigated.</p>
<p>There is a hearing aid (I have a hearing loss as well) with an optional Bluetooth receiver to wear around your neck.  The receiver converts Bluetooth signals into another signal format for re-transmission directly to the right and left hearing aids.  But this option for wirelessly connecting to an iPhone or your computer via Bluetooth is expensive, so I declined this option.  Maybe later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Editorial &#8211; The iPod shuffle 3G and the Future by bertp001</title>
		<link>http://www.lioncourt.com/2009/03/15/editorial-the-ipod-shuffle-3g-and-the-future/comment-page-1/#comment-172</link>
		<dc:creator>bertp001</dc:creator>
		<pubDate>Sun, 15 Mar 2009 21:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=337#comment-172</guid>
		<description>I can see other Apple devices making use of a capability to synchronize via iTunes 8.1 in conjunction with the new VoiceOver Kit installed on your own computer.  That would include the new multi-lingual support.

I wonder about the &quot;Kit&quot; part of the phrase &quot;VoiceOver Kit&quot;.  Is it just an installed package of functions, or does it imply more?  When searching for &quot;VoiceOver Kit&quot; on the Apple Developer Connection, the search result does not show anything new.</description>
		<content:encoded><![CDATA[<p>I can see other Apple devices making use of a capability to synchronize via iTunes 8.1 in conjunction with the new VoiceOver Kit installed on your own computer.  That would include the new multi-lingual support.</p>
<p>I wonder about the &#8220;Kit&#8221; part of the phrase &#8220;VoiceOver Kit&#8221;.  Is it just an installed package of functions, or does it imply more?  When searching for &#8220;VoiceOver Kit&#8221; on the Apple Developer Connection, the search result does not show anything new.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
