<?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"
	>
<channel>
	<title>Comments on: The Skinning Trade-off</title>
	<atom:link href="http://arapehlivanian.com/2008/04/24/the-skinning-trade-off/feed/" rel="self" type="application/rss+xml" />
	<link>http://arapehlivanian.com/2008/04/24/the-skinning-trade-off/</link>
	<description>Web Standards, Web Culture, Web Everything.™</description>
	<pubDate>Mon, 08 Sep 2008 05:01:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Luke Maciak</title>
		<link>http://arapehlivanian.com/2008/04/24/the-skinning-trade-off/#comment-40217</link>
		<dc:creator>Luke Maciak</dc:creator>
		<pubDate>Thu, 24 Apr 2008 20:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=382#comment-40217</guid>
		<description>Well said. I ran into the same set of issues when my boss decided he wants to have a 3-state check box (checked, unchecked and unavailable/grayed out). I had to hide the actual elements, then use JavaScript magic to replace them with images on the fly, and react to clicking.

Keyboard navigation was lost, and the whole system would fail if you were using a screen reader or a browser without JS enabled. In the end it worked out because it was an internal app used only by certain employees.</description>
		<content:encoded><![CDATA[<p>Well said. I ran into the same set of issues when my boss decided he wants to have a 3-state check box (checked, unchecked and unavailable/grayed out). I had to hide the actual elements, then use JavaScript magic to replace them with images on the fly, and react to clicking.</p>
<p>Keyboard navigation was lost, and the whole system would fail if you were using a screen reader or a browser without JS enabled. In the end it worked out because it was an internal app used only by certain employees.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarven Capadisli</title>
		<link>http://arapehlivanian.com/2008/04/24/the-skinning-trade-off/#comment-40206</link>
		<dc:creator>Sarven Capadisli</dc:creator>
		<pubDate>Thu, 24 Apr 2008 13:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=382#comment-40206</guid>
		<description>Not the mention the responsiveness will never be as good as the native support.

No brainer, but, one plus that comes with skinning native browser elements is actually improving the UI visually (invoking certain emotions yadi yadi yada) and have it more consistent with the rest of the page design. Usability vs. Emotions - There is a trade off at some level.</description>
		<content:encoded><![CDATA[<p>Not the mention the responsiveness will never be as good as the native support.</p>
<p>No brainer, but, one plus that comes with skinning native browser elements is actually improving the UI visually (invoking certain emotions yadi yadi yada) and have it more consistent with the rest of the page design. Usability vs. Emotions - There is a trade off at some level.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Snook</title>
		<link>http://arapehlivanian.com/2008/04/24/the-skinning-trade-off/#comment-40202</link>
		<dc:creator>Jonathan Snook</dc:creator>
		<pubDate>Thu, 24 Apr 2008 05:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/?p=382#comment-40202</guid>
		<description>In my presentation at FOWD last year, I talked about this very topic. For every action we look to override, we have to work harder to replicate all the functionality that it used to have. Not just for mouse users, but for keyboard users, and for screenreaders. You have to have a pretty good business justification for breaking a user expectation and "it looks cool" isn't one of them. :)</description>
		<content:encoded><![CDATA[<p>In my presentation at FOWD last year, I talked about this very topic. For every action we look to override, we have to work harder to replicate all the functionality that it used to have. Not just for mouse users, but for keyboard users, and for screenreaders. You have to have a pretty good business justification for breaking a user expectation and &#8220;it looks cool&#8221; isn&#8217;t one of them. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
