<?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: More about the &#60;button&#62; element</title>
	<atom:link href="http://nickcowie.com/2005/accessible-buttons-more/feed/" rel="self" type="application/rss+xml" />
	<link>http://nickcowie.com/2005/accessible-buttons-more/</link>
	<description>Web standards, accessibility  and such like with a bias toward  Government web sites</description>
	<pubDate>Wed, 19 Nov 2008 04:20:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: RE Mogul</title>
		<link>http://nickcowie.com/2005/accessible-buttons-more/#comment-37021</link>
		<dc:creator>RE Mogul</dc:creator>
		<pubDate>Wed, 25 Jun 2008 23:32:19 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=36#comment-37021</guid>
		<description>Buttons should be usable, without the ability to read their text.

For example, the button I clicked to post this was obvious. 
It submits. It is the only one. What else would it do?

If you asked me later, I wouldn't be able to tell you what it actually read. I can easily discern its function from context. Focus on context.

Everything else is simply diversion, in regards to accessibility.


:::::::::CODING for the KEYBOARD:::::::::

IN THE PERFECT WORLD:
All developers design keyboard-friendly interfaces.


Case in Point:

Keyboard a submit button, make it read:

 [SHIFT] [ENTER] to Submit.

Notice the shift-enter convenience. 
Try it. It just feels right.
Use actual keyboard button images. 

It would make for a super-large button -- an EZ target.


Precision-pointing is the most difficult thing one can ask of a user.
Need Proof? Program a robot to point and click a virtual button. Then program a robot to shift-enter. Then tell me which is the EZiest task.</description>
		<content:encoded><![CDATA[<p>Buttons should be usable, without the ability to read their text.</p>
<p>For example, the button I clicked to post this was obvious.<br />
It submits. It is the only one. What else would it do?</p>
<p>If you asked me later, I wouldn&#8217;t be able to tell you what it actually read. I can easily discern its function from context. Focus on context.</p>
<p>Everything else is simply diversion, in regards to accessibility.</p>
<p>:::::::::CODING for the KEYBOARD:::::::::</p>
<p>IN THE PERFECT WORLD:<br />
All developers design keyboard-friendly interfaces.</p>
<p>Case in Point:</p>
<p>Keyboard a submit button, make it read:</p>
<p> [SHIFT] [ENTER] to Submit.</p>
<p>Notice the shift-enter convenience.<br />
Try it. It just feels right.<br />
Use actual keyboard button images. </p>
<p>It would make for a super-large button &#8212; an EZ target.</p>
<p>Precision-pointing is the most difficult thing one can ask of a user.<br />
Need Proof? Program a robot to point and click a virtual button. Then program a robot to shift-enter. Then tell me which is the EZiest task.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adrian</title>
		<link>http://nickcowie.com/2005/accessible-buttons-more/#comment-17095</link>
		<dc:creator>adrian</dc:creator>
		<pubDate>Wed, 15 Aug 2007 02:13:24 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=36#comment-17095</guid>
		<description>On Safari 2.0.4, it seems like BUTTON elements are not included in the forms.elements collection. Has there been a fix to this?</description>
		<content:encoded><![CDATA[<p>On Safari 2.0.4, it seems like BUTTON elements are not included in the forms.elements collection. Has there been a fix to this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Cowie &#187; I am doing a presentation</title>
		<link>http://nickcowie.com/2005/accessible-buttons-more/#comment-300</link>
		<dc:creator>Nick Cowie &#187; I am doing a presentation</dc:creator>
		<pubDate>Mon, 06 Mar 2006 10:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=36#comment-300</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: Lea de Groot</title>
		<link>http://nickcowie.com/2005/accessible-buttons-more/#comment-186</link>
		<dc:creator>Lea de Groot</dc:creator>
		<pubDate>Tue, 27 Dec 2005 06:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=36#comment-186</guid>
		<description>Ah, much better :)</description>
		<content:encoded><![CDATA[<p>Ah, much better :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Smoljak</title>
		<link>http://nickcowie.com/2005/accessible-buttons-more/#comment-175</link>
		<dc:creator>Kay Smoljak</dc:creator>
		<pubDate>Mon, 26 Dec 2005 02:40:35 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=36#comment-175</guid>
		<description>I fall into the category of not really knowing about the button element (at least until I read this). Thanks Nick for edja-ma-catin' me!</description>
		<content:encoded><![CDATA[<p>I fall into the category of not really knowing about the button element (at least until I read this). Thanks Nick for edja-ma-catin&#8217; me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lea de Groot</title>
		<link>http://nickcowie.com/2005/accessible-buttons-more/#comment-97</link>
		<dc:creator>Lea de Groot</dc:creator>
		<pubDate>Sat, 24 Dec 2005 11:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/?p=36#comment-97</guid>
		<description>Probably want to check those buttons in Safari before you go live - the icon is overlapping the words :(
Looks fine in Mac/FF, of course :)

I must admit that I don't use Buttons, principally because I didn't know what an appropriate usage was; I shall experiment with them next time I do a form (oh, look, thats scheduled for sometime next week :))

Lea</description>
		<content:encoded><![CDATA[<p>Probably want to check those buttons in Safari before you go live - the icon is overlapping the words :(<br />
Looks fine in Mac/FF, of course :)</p>
<p>I must admit that I don&#8217;t use Buttons, principally because I didn&#8217;t know what an appropriate usage was; I shall experiment with them next time I do a form (oh, look, thats scheduled for sometime next week :))</p>
<p>Lea</p>
]]></content:encoded>
	</item>
</channel>
</rss>
