<?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:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"

	>
<channel>
	<title>
	Comments on: SeroTalk Extra: Tech Chat Edition	</title>
	<atom:link href="/2015/04/06/serotalk-extra-tech-chat-edition/feed/" rel="self" type="application/rss+xml" />
	<link>/2015/04/06/serotalk-extra-tech-chat-edition/</link>
	<description>A podcast and interactive blog on the accessible digital lifestyle, produced by Serotek, the Accessibility Anywhere people</description>
	<lastBuildDate>Tue, 14 Apr 2015 13:45:48 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.3</generator>
	<item>
		<title>
		By: Beth		</title>
		<link>/2015/04/06/serotalk-extra-tech-chat-edition/comment-page-1/#comment-716285</link>

		<dc:creator><![CDATA[Beth]]></dc:creator>
		<pubDate>Thu, 09 Apr 2015 03:03:12 +0000</pubDate>
		<guid isPermaLink="false">/?p=4925#comment-716285</guid>

					<description><![CDATA[In another podcast last year, Mike said something about Windows Phone having Samnet on it, this topic was not mentioned in the most current &quot;Extras&quot; podcast but it goes along with the mobile theme.  Please, Mike, tell us more about this.  Thanks.  Beth]]></description>
			<content:encoded><![CDATA[<p>In another podcast last year, Mike said something about Windows Phone having Samnet on it, this topic was not mentioned in the most current &#8220;Extras&#8221; podcast but it goes along with the mobile theme.  Please, Mike, tell us more about this.  Thanks.  Beth</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: BlindEducator		</title>
		<link>/2015/04/06/serotalk-extra-tech-chat-edition/comment-page-1/#comment-716279</link>

		<dc:creator><![CDATA[BlindEducator]]></dc:creator>
		<pubDate>Wed, 08 Apr 2015 15:01:25 +0000</pubDate>
		<guid isPermaLink="false">/?p=4925#comment-716279</guid>

					<description><![CDATA[After listening to the podcast, a few questions pop out. 
1. How can the Pebble be compared to the AppleWatch when they are 2 different things? By the way matt described the Pebble, and Mike carried on about it. They made it sound as it is a smart ban and not a watch. And even though accessibility wasn&#039;t mentioned in the Apple keynotes. As most times it isn&#039;t. You know it will have accessibility. Can we say the same about the Pebble. And as I mentioned in an AudioBoom back in September October time. The battery of a product will be as good as the user makes it. All the bench marks presented for a product on a keynote. Is in a controlled environment. So the 18 hours was given with someone constantly moving. other then a few blind people. Can you really see all that requires accessibility be as active as the people used to demo the product? 

2. If the AppleWatch is this shiny new thing that may or may not work, What then is the Amazon Echo which is still in beta and can be said the same as the AppleWatch? Specially with Amazon&#039;s track record that some of their products aren&#039;t with us any more. Like the Fire Phone. And the Echo was demonstrated in the podcast. 

Over all, it was a good podcast, and Joe was right, at times I did want to yell at the round table of presenters. Specially, as I mentioned it in my blog. The whole thing sounded as if you were all going by a script and when one would go off that script. Mike would pose a question to get back on the script, and then it sounded as if a deer was caught by headlights. Hope, Derek, and Matt sounded as if they were shooting off the hip, but there were times. That when being challenged by Mike, Hope kind of wanted to take a couple of things back. Even though it was a pretty good informative podcast. It was pretty lengthy and way too many people and stuff presented. Thank you for reading.]]></description>
			<content:encoded><![CDATA[<p>After listening to the podcast, a few questions pop out.<br />
1. How can the Pebble be compared to the AppleWatch when they are 2 different things? By the way matt described the Pebble, and Mike carried on about it. They made it sound as it is a smart ban and not a watch. And even though accessibility wasn&#8217;t mentioned in the Apple keynotes. As most times it isn&#8217;t. You know it will have accessibility. Can we say the same about the Pebble. And as I mentioned in an AudioBoom back in September October time. The battery of a product will be as good as the user makes it. All the bench marks presented for a product on a keynote. Is in a controlled environment. So the 18 hours was given with someone constantly moving. other then a few blind people. Can you really see all that requires accessibility be as active as the people used to demo the product? </p>
<p>2. If the AppleWatch is this shiny new thing that may or may not work, What then is the Amazon Echo which is still in beta and can be said the same as the AppleWatch? Specially with Amazon&#8217;s track record that some of their products aren&#8217;t with us any more. Like the Fire Phone. And the Echo was demonstrated in the podcast. </p>
<p>Over all, it was a good podcast, and Joe was right, at times I did want to yell at the round table of presenters. Specially, as I mentioned it in my blog. The whole thing sounded as if you were all going by a script and when one would go off that script. Mike would pose a question to get back on the script, and then it sounded as if a deer was caught by headlights. Hope, Derek, and Matt sounded as if they were shooting off the hip, but there were times. That when being challenged by Mike, Hope kind of wanted to take a couple of things back. Even though it was a pretty good informative podcast. It was pretty lengthy and way too many people and stuff presented. Thank you for reading.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Beth		</title>
		<link>/2015/04/06/serotalk-extra-tech-chat-edition/comment-page-1/#comment-716278</link>

		<dc:creator><![CDATA[Beth]]></dc:creator>
		<pubDate>Wed, 08 Apr 2015 14:10:34 +0000</pubDate>
		<guid isPermaLink="false">/?p=4925#comment-716278</guid>

					<description><![CDATA[I wrote to the APH BP18 list and got a very interesting response to the question of the future of that and I assume also similar android phones slash notetakers for the blind:  The difference in normal phones and the bp18 is that, if desired, the screen reader can be implanted in the system and the internals of the device can be changed.  Beth]]></description>
			<content:encoded><![CDATA[<p>I wrote to the APH BP18 list and got a very interesting response to the question of the future of that and I assume also similar android phones slash notetakers for the blind:  The difference in normal phones and the bp18 is that, if desired, the screen reader can be implanted in the system and the internals of the device can be changed.  Beth</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Beth		</title>
		<link>/2015/04/06/serotalk-extra-tech-chat-edition/comment-page-1/#comment-716277</link>

		<dc:creator><![CDATA[Beth]]></dc:creator>
		<pubDate>Wed, 08 Apr 2015 14:00:44 +0000</pubDate>
		<guid isPermaLink="false">/?p=4925#comment-716277</guid>

					<description><![CDATA[If third party screen readers will someday die, what about note takers?  Also, it was stated that Apple, though not an A T vendor, is providing access, since there is no room for third party innovation.  Though not an Apple user, I have read and listened to podcasts enough to question where Apple came up with VoiceOver, were blind people consulted during the planning and testing stages, I assume they were and still are.  Well, VoiceOver is very inefficient, in my opinion, compared to Windows.  I&#039;m concerned about how A T will fare regarding efficiency in the years ahead.  Beth]]></description>
			<content:encoded><![CDATA[<p>If third party screen readers will someday die, what about note takers?  Also, it was stated that Apple, though not an A T vendor, is providing access, since there is no room for third party innovation.  Though not an Apple user, I have read and listened to podcasts enough to question where Apple came up with VoiceOver, were blind people consulted during the planning and testing stages, I assume they were and still are.  Well, VoiceOver is very inefficient, in my opinion, compared to Windows.  I&#8217;m concerned about how A T will fare regarding efficiency in the years ahead.  Beth</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Beth		</title>
		<link>/2015/04/06/serotalk-extra-tech-chat-edition/comment-page-1/#comment-716270</link>

		<dc:creator><![CDATA[Beth]]></dc:creator>
		<pubDate>Wed, 08 Apr 2015 00:32:23 +0000</pubDate>
		<guid isPermaLink="false">/?p=4925#comment-716270</guid>

					<description><![CDATA[I so enjoyed the show on the future of tech, fascinating stuff!  Laugh if you will but, for years, I have wondered why there has never, at least to my knowledge, been cell phone availability on PCs.  No, you wouldn&#039;t hold it to your face, it would be assumed that you would use a speakerphone function or some kind of headset.  Would someone please tell me:  Why hasn&#039;t this been done?  Why not have a SIM card in a PC or some other means of cellular technology?  Thanks and keep up the great work!  Beth]]></description>
			<content:encoded><![CDATA[<p>I so enjoyed the show on the future of tech, fascinating stuff!  Laugh if you will but, for years, I have wondered why there has never, at least to my knowledge, been cell phone availability on PCs.  No, you wouldn&#8217;t hold it to your face, it would be assumed that you would use a speakerphone function or some kind of headset.  Would someone please tell me:  Why hasn&#8217;t this been done?  Why not have a SIM card in a PC or some other means of cellular technology?  Thanks and keep up the great work!  Beth</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
