<?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: Stylish Accessible Buttons</title>
	<atom:link href="http://nickcowie.com/2005/stylish-accessible-buttons/feed/" rel="self" type="application/rss+xml" />
	<link>http://nickcowie.com/2005/stylish-accessible-buttons/</link>
	<description>Web standards, accessibility  and such like with a bias toward  Government web sites</description>
	<lastBuildDate>Wed, 25 Jan 2012 22:47:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: RE Mogul</title>
		<link>http://nickcowie.com/2005/stylish-accessible-buttons/comment-page-1/#comment-37033</link>
		<dc:creator>RE Mogul</dc:creator>
		<pubDate>Thu, 26 Jun 2008 17:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=31#comment-37033</guid>
		<description>Wasn&#039;t mobile-device-access the genesis of SVGs?
SVG is also XML-based abilities, which opens to a myriad of possibility.

About button element:
One could easily embed the image in another recognizable tag.




IE &amp; Adobe Love Silverlight &amp; Flash more than SVG.

I love them too, I just wish the plugin-code was open source -- so they could be included in browsers by default.</description>
		<content:encoded><![CDATA[<p>Wasn’t mobile-device-access the genesis of SVGs?<br />
SVG is also XML-based abilities, which opens to a myriad of possibility.</p>
<p>About button element:<br />
One could easily embed the image in another recognizable tag.</p>
<p>IE &amp; Adobe Love Silverlight &amp; Flash more than SVG.</p>
<p>I love them too, I just wish the plugin-code was open source — so they could be included in browsers by default.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://nickcowie.com/2005/stylish-accessible-buttons/comment-page-1/#comment-37023</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Thu, 26 Jun 2008 00:53:51 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=31#comment-37023</guid>
		<description>Mogul while your comments are perfectly valid for somebody with good eyesight who is accessing the web through a modern computer and monitor. It fails badly on mobile devices, no flash support and numeric keypad only. And most mobile browsers do not even support the button element.</description>
		<content:encoded><![CDATA[<p>Mogul while your comments are perfectly valid for somebody with good eyesight who is accessing the web through a modern computer and monitor. It fails badly on mobile devices, no flash support and numeric keypad only. And most mobile browsers do not even support the button element.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RE Mogul</title>
		<link>http://nickcowie.com/2005/stylish-accessible-buttons/comment-page-1/#comment-37019</link>
		<dc:creator>RE Mogul</dc:creator>
		<pubDate>Wed, 25 Jun 2008 23:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=31#comment-37019</guid>
		<description>Images are THE ULTIMATE in accessibility -- any and every device can display them the way THEIR MAKER INTENDED them to look.

Images are also the most efficient means of achieving near-perfect beauty with the minimum of code-testing labor. They are so easy. They simply work.

Bandwidth limitations are a BYGONE of the past.
Use (small) images for buttons. Your page will still be lightning-quick.


:::::THE REAL ISSUE:::::

The web simply needs better standards for image-scaling.

Too bad SVGs are not-yet universal. One can only hope for soon. 
IE, why do you forsake us?


:::::THE IDEAL SOLUTION:::::

The best buttons are right under your nose.
Make all of your buttons keyboard-equivalent.

[TAB], [ENTER], [SPACEBAR], ah yes, spacebar, the most useful and most obvious button -- so under-appreciated.

Appreciate what we already have.</description>
		<content:encoded><![CDATA[<p>Images are THE ULTIMATE in accessibility — any and every device can display them the way THEIR MAKER INTENDED them to look.</p>
<p>Images are also the most efficient means of achieving near-perfect beauty with the minimum of code-testing labor. They are so easy. They simply work.</p>
<p>Bandwidth limitations are a BYGONE of the past.<br />
Use (small) images for buttons. Your page will still be lightning-quick.</p>
<p>:::::THE REAL ISSUE:::::</p>
<p>The web simply needs better standards for image-scaling.</p>
<p>Too bad SVGs are not-yet universal. One can only hope for soon.<br />
IE, why do you forsake us?</p>
<p>:::::THE IDEAL SOLUTION:::::</p>
<p>The best buttons are right under your nose.<br />
Make all of your buttons keyboard-equivalent.</p>
<p>[TAB], [ENTER], [SPACEBAR], ah yes, spacebar, the most useful and most obvious button — so under-appreciated.</p>
<p>Appreciate what we already have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yong Bakos</title>
		<link>http://nickcowie.com/2005/stylish-accessible-buttons/comment-page-1/#comment-1168</link>
		<dc:creator>Yong Bakos</dc:creator>
		<pubDate>Wed, 19 Jul 2006 17:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=31#comment-1168</guid>
		<description>The problem with Microsoft&#039;s implementation of the button element is that it friggin doesn&#039;t behave according to standard, and is pretty much useless. It declares its value to be the value of InnerHTML (the label of the button) instead of the value of the value attribute.

I hope its fixed in IE7.</description>
		<content:encoded><![CDATA[<p>The problem with Microsoft’s implementation of the button element is that it friggin doesn’t behave according to standard, and is pretty much useless. It declares its value to be the value of InnerHTML (the label of the button) instead of the value of the value attribute.</p>
<p>I hope its fixed in IE7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Cowie &#187; I am doing a presentation</title>
		<link>http://nickcowie.com/2005/stylish-accessible-buttons/comment-page-1/#comment-283</link>
		<dc:creator>Nick Cowie &#187; I am doing a presentation</dc:creator>
		<pubDate>Sat, 04 Feb 2006 12:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=31#comment-283</guid>
		<description>[...] The advantage of doing a presentation on the button element, which are the most popular posts on this blogs, is I have already done most of the research for those posts: Stylish Accessible Buttons, More about the button element and a half written post about how to position buttons. So there is very little work to do, except try and find out how IE7 beta deals with the button element and exactly what extra padding IE5 and IE6 adds to the button element, it is not as I previously stated a fixed amount but appears to be proportional to the width of the button element. Still all of this can be packaged into a 30 minute presentation, as long I only briefly touch on conditional comments for serving an additional stylesheet to IE and how to use absolutely position an element inside a relatively positioned element. [...]</description>
		<content:encoded><![CDATA[<p>[…] The advantage of doing a presentation on the button element, which are the most popular posts on this blogs, is I have already done most of the research for those posts: Stylish Accessible Buttons, More about the button element and a half written post about how to position buttons. So there is very little work to do, except try and find out how IE7 beta deals with the button element and exactly what extra padding IE5 and IE6 adds to the button element, it is not as I previously stated a fixed amount but appears to be proportional to the width of the button element. Still all of this can be packaged into a 30 minute presentation, as long I only briefly touch on conditional comments for serving an additional stylesheet to IE and how to use absolutely position an element inside a relatively positioned element. […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Lewis</title>
		<link>http://nickcowie.com/2005/stylish-accessible-buttons/comment-page-1/#comment-34</link>
		<dc:creator>Joe Lewis</dc:creator>
		<pubDate>Mon, 28 Nov 2005 06:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=31#comment-34</guid>
		<description>Very slick. I can give that a whirl on one of my current projects!</description>
		<content:encoded><![CDATA[<p>Very slick. I can give that a whirl on one of my current projects!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

