<?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: Attach hotkeys to links</title>
	<atom:link href="http://thenew.oddend.com/2006/attach-hotkeys-to-links/feed/" rel="self" type="application/rss+xml" />
	<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/</link>
	<description>The weblog of web designer and developer Martin Kool</description>
	<pubDate>Wed,  7 Jan 2009 13:15:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Jader Rubini</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3188</link>
		<dc:creator>Jader Rubini</dc:creator>
		<pubDate>Mon, 16 Oct 2006 12:53:50 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3188</guid>
		<description>Great job, man. Works perfectly on Opera 9. ;)</description>
		<content:encoded><![CDATA[<p>Great job, man. Works perfectly on Opera 9. <img src='http://thenew.oddend.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Kool</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3187</link>
		<dc:creator>Martin Kool</dc:creator>
		<pubDate>Sat, 14 Oct 2006 00:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3187</guid>
		<description>The implementation is indeed standard, but the execution is not. While Firefox on PC follows a link when the accesskey is pressed, Internet Explorer (7) only focuses the link, requiring the Enter key pressed to have it followed.

If I was using hotkeys for extended functionality in forms, acceskeys would indeed be the way to go. With links however, behavior varies and any usage instructions would have to keep in account what browser the client is using.

It so happens that I am currently deploying this script for a site that needs to be accessible by disabled persons. The advantage it has is that of one keypress over a keypress combination. Pressing both the Alt key and another can be just as challenging as using a mouse.

Oh, I understand now what you mean with the insertion point, it's worth checking out if it can be remedied even if it is a Safari-only problem.</description>
		<content:encoded><![CDATA[<p>The implementation is indeed standard, but the execution is not. While Firefox on PC follows a link when the accesskey is pressed, Internet Explorer (7) only focuses the link, requiring the Enter key pressed to have it followed.</p>
<p>If I was using hotkeys for extended functionality in forms, acceskeys would indeed be the way to go. With links however, behavior varies and any usage instructions would have to keep in account what browser the client is using.</p>
<p>It so happens that I am currently deploying this script for a site that needs to be accessible by disabled persons. The advantage it has is that of one keypress over a keypress combination. Pressing both the Alt key and another can be just as challenging as using a mouse.</p>
<p>Oh, I understand now what you mean with the insertion point, it&#8217;s worth checking out if it can be remedied even if it is a Safari-only problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Armstrong</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3186</link>
		<dc:creator>Paul Armstrong</dc:creator>
		<pubDate>Fri, 13 Oct 2006 20:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3186</guid>
		<description>Have you really looked at how &lt;code&gt;accesskey&lt;/code&gt;s work? The implementation is standard, just different per operating system. See an &lt;a href="http://www.w3.org/WAI/wcag-curric/sam76-0.htm" title="WAI Web Accessibility Example" rel="nofollow"&gt;example of accesskeys&lt;/a&gt;.

And for the form stuff, I mean the insertion point... the spot at which the text you type will be placed in the body of the field. There should be a blinking line denoting the current position you will type in the text... it is there, but incredibly hard to see. Further testing shows that this is only a Safari problem. I'm not able to find any documentation on it, but it seems logical that this should be inherited from the element's color style. So, I'm not sure what you could do at this point, seems as though WebKit could use some more work (and Apple should get the updates they've made working).</description>
		<content:encoded><![CDATA[<p>Have you really looked at how <code>accesskey</code>s work? The implementation is standard, just different per operating system. See an <a href="http://www.w3.org/WAI/wcag-curric/sam76-0.htm" title="WAI Web Accessibility Example" rel="nofollow">example of accesskeys</a>.</p>
<p>And for the form stuff, I mean the insertion point&#8230; the spot at which the text you type will be placed in the body of the field. There should be a blinking line denoting the current position you will type in the text&#8230; it is there, but incredibly hard to see. Further testing shows that this is only a Safari problem. I&#8217;m not able to find any documentation on it, but it seems logical that this should be inherited from the element&#8217;s color style. So, I&#8217;m not sure what you could do at this point, seems as though WebKit could use some more work (and Apple should get the updates they&#8217;ve made working).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Kool</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3185</link>
		<dc:creator>Martin Kool</dc:creator>
		<pubDate>Fri, 13 Oct 2006 20:18:29 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3185</guid>
		<description>Paul, I don't think we have the same conception of 'tried and true', &lt;code&gt;accesskey&lt;/code&gt; implementation in the various browsers is anything but standard.

I agree with you on the Home key. Although I believe you can use both the up and down arrow keys as well as home and end to scroll. Never the less, I broke an existing hotkey and that is not smart.

As for the black on black, there is a 10% difference in the brightness of form field's border and background, but only 5% between the form field's background and the page background. Thanks for pointing out that it's hard to see, I may increase the contrast a bit.</description>
		<content:encoded><![CDATA[<p>Paul, I don&#8217;t think we have the same conception of &#8216;tried and true&#8217;, <code>accesskey</code> implementation in the various browsers is anything but standard.</p>
<p>I agree with you on the Home key. Although I believe you can use both the up and down arrow keys as well as home and end to scroll. Never the less, I broke an existing hotkey and that is not smart.</p>
<p>As for the black on black, there is a 10% difference in the brightness of form field&#8217;s border and background, but only 5% between the form field&#8217;s background and the page background. Thanks for pointing out that it&#8217;s hard to see, I may increase the contrast a bit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Armstrong</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3184</link>
		<dc:creator>Paul Armstrong</dc:creator>
		<pubDate>Fri, 13 Oct 2006 19:14:16 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3184</guid>
		<description>Have you thought about this from a &lt;em&gt;usability&lt;/em&gt; or &lt;em&gt;accessibility&lt;/em&gt; standpoint? Doesn't it seem that using the &lt;code&gt;accesskey&lt;/code&gt; attribute would be a more defined way of navigating? Don't get me wrong, this makes your site quite memorable, but it is like you are trying to change the standards that are already put in place—the ones that are tried and true.

Also, on a Mac, the Home and End keys are used as page-scrolling keys. Granted, not many people probably know this or use it, but to the few that are might become seriously annoyed at losing the page they were on.

Lastly, I can't even see the insertion point in the input and textarea fields in this comment form because it is black on (almost) black... quite confusing.</description>
		<content:encoded><![CDATA[<p>Have you thought about this from a <em>usability</em> or <em>accessibility</em> standpoint? Doesn&#8217;t it seem that using the <code>accesskey</code> attribute would be a more defined way of navigating? Don&#8217;t get me wrong, this makes your site quite memorable, but it is like you are trying to change the standards that are already put in place—the ones that are tried and true.</p>
<p>Also, on a Mac, the Home and End keys are used as page-scrolling keys. Granted, not many people probably know this or use it, but to the few that are might become seriously annoyed at losing the page they were on.</p>
<p>Lastly, I can&#8217;t even see the insertion point in the input and textarea fields in this comment form because it is black on (almost) black&#8230; quite confusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Kool</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3183</link>
		<dc:creator>Martin Kool</dc:creator>
		<pubDate>Fri, 13 Oct 2006 16:39:46 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3183</guid>
		<description>Thanks Jorge. Keep in mind when implementing this that the hotkeys &lt;em&gt;always&lt;/em&gt; work, even when you are using a form input field or textarea.

Check the source of my site to see how I solved this for the search form using onfocus and onblur.</description>
		<content:encoded><![CDATA[<p>Thanks Jorge. Keep in mind when implementing this that the hotkeys <em>always</em> work, even when you are using a form input field or textarea.</p>
<p>Check the source of my site to see how I solved this for the search form using onfocus and onblur.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge Epuñan</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3182</link>
		<dc:creator>Jorge Epuñan</dc:creator>
		<pubDate>Fri, 13 Oct 2006 16:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3182</guid>
		<description>it works great on Safari 2. Congratulations, excelent resource, and tnx to share it.</description>
		<content:encoded><![CDATA[<p>it works great on Safari 2. Congratulations, excelent resource, and tnx to share it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cagintranet Networks &#187; Coming Attraction: Hot Key Accessibility</title>
		<link>http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3181</link>
		<dc:creator>Cagintranet Networks &#187; Coming Attraction: Hot Key Accessibility</dc:creator>
		<pubDate>Fri, 13 Oct 2006 16:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://thenew.oddend.com/2006/attach-hotkeys-to-links/#comment-3181</guid>
		<description>[...] OddEnd.com has a great article showing you how to easily implement hotkey functionality to your Wordpress blog or website. Using the Left Arrow, Right Arrow or Home buttons on your keyboard will allow you to navigate to the Previous Post, Next Post or Homepage (respectively). [...]</description>
		<content:encoded><![CDATA[<p>[...] OddEnd.com has a great article showing you how to easily implement hotkey functionality to your Wordpress blog or website. Using the Left Arrow, Right Arrow or Home buttons on your keyboard will allow you to navigate to the Previous Post, Next Post or Homepage (respectively). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
