<?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: Tech Giant Launches Smartphone For Older People</title>
	<atom:link href="http://www.headstar.com/eablive/?feed=rss2&#038;p=838" rel="self" type="application/rss+xml" />
	<link>http://www.headstar.com/eablive/?p=838</link>
	<description>Access to technology for all</description>
	<lastBuildDate>Sun, 01 Apr 2018 16:32:15 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.0.1</generator>
	<item>
		<title>By: Jeff Seager</title>
		<link>http://www.headstar.com/eablive/?p=838&#038;cpage=1#comment-6671</link>
		<dc:creator><![CDATA[Jeff Seager]]></dc:creator>
		<pubDate>Fri, 29 Mar 2013 15:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.headstar.com/eablive/?p=838#comment-6671</guid>
		<description><![CDATA[Bravo and kudos to Fujitsu (though age is only one predictor of such need, so I think their emphasis on that aspect may be skewed a bit)! As with web design, application design for smartphones has a long way to go if we want them to be more accessible to all. I&#039;m a recent convert to a smartphone, and being older now it&#039;s becoming easier for me to imagine the experience of someone with macular degeneration or cataracts, to offer two very common examples that would make using a typical smartphone challenging.

One thing I&#039;ve noticed is that many smartphone and mobile app creators set up their default interfaces beginning with a blank white or otherwise very bright screen, then add their functional elements to that glaring white background. I&#039;m guessing this derives from our old-school understanding of the screen as a metaphor for print, a bleached white page, and it&#039;s simply wrongheaded. We are peering into a light source, after all, so as often as possible we should be designing such that the background pixels are dark and the functional elements are (relatively) the brighter objects on screen. It&#039;s the polite thing to do, to protect and preserve eyesight, and it makes sense in other ways, as the eye is drawn to the brighter and larger elements on a &quot;page&quot; of any kind.

Who knows how much damage can be done to the eyes of people using these things for a lifetime? Must we wait to see the adverse effects to prompt a change in our bad design habits? Well, maybe not for long. I&#039;m using a browser called Dolphin on my Android phone, and among several very nice features it includes a plugin for &quot;Night Mode.&quot; This mode instantly dims the screen significantly and greatly reduces contrast, making for comfortable glare-free reading in very dim light or absolute darkness. Smart. I&#039;d like to see more of such thoughtful design, and I hope Fujitsu&#039;s first steps with the Stylistic SO1 will provoke more thought and action in that direction.]]></description>
		<content:encoded><![CDATA[<p>Bravo and kudos to Fujitsu (though age is only one predictor of such need, so I think their emphasis on that aspect may be skewed a bit)! As with web design, application design for smartphones has a long way to go if we want them to be more accessible to all. I&#8217;m a recent convert to a smartphone, and being older now it&#8217;s becoming easier for me to imagine the experience of someone with macular degeneration or cataracts, to offer two very common examples that would make using a typical smartphone challenging.</p>
<p>One thing I&#8217;ve noticed is that many smartphone and mobile app creators set up their default interfaces beginning with a blank white or otherwise very bright screen, then add their functional elements to that glaring white background. I&#8217;m guessing this derives from our old-school understanding of the screen as a metaphor for print, a bleached white page, and it&#8217;s simply wrongheaded. We are peering into a light source, after all, so as often as possible we should be designing such that the background pixels are dark and the functional elements are (relatively) the brighter objects on screen. It&#8217;s the polite thing to do, to protect and preserve eyesight, and it makes sense in other ways, as the eye is drawn to the brighter and larger elements on a &#8220;page&#8221; of any kind.</p>
<p>Who knows how much damage can be done to the eyes of people using these things for a lifetime? Must we wait to see the adverse effects to prompt a change in our bad design habits? Well, maybe not for long. I&#8217;m using a browser called Dolphin on my Android phone, and among several very nice features it includes a plugin for &#8220;Night Mode.&#8221; This mode instantly dims the screen significantly and greatly reduces contrast, making for comfortable glare-free reading in very dim light or absolute darkness. Smart. I&#8217;d like to see more of such thoughtful design, and I hope Fujitsu&#8217;s first steps with the Stylistic SO1 will provoke more thought and action in that direction.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
