<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Almost Getting it Right with Access Keys</title>
	<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/</link>
	<description>Raising the awareness of Web Site Accessibility and Marketing.</description>
	<pubDate>Sun, 20 Jul 2008 14:17:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Pseudo-Accessibility: Reinventing the Wheel &#124; Joe Dolson Accessible Web Design</title>
		<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-77286</link>
		<dc:creator>Pseudo-Accessibility: Reinventing the Wheel &#124; Joe Dolson Accessible Web Design</dc:creator>
		<pubDate>Mon, 23 Jul 2007 14:18:28 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-77286</guid>
		<description>[...] goal. There are many, many problems with the accesskey attribute, ranging from problems with discoverability to major keyboard shortcut [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] goal. There are many, many problems with the accesskey attribute, ranging from problems with discoverability to major keyboard shortcut [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63971</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Wed, 27 Jun 2007 19:22:04 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63971</guid>
		<description>&lt;blockquote&gt;
I must say, however, making sure a site is accessible to people with a wide array of disabilities is very difficult without having those disabilities yourself.
&lt;/blockquote&gt;

That's definitely the biggest challenge - putting yourself into the position of all the possible users and trying to take their needs into consideration is a huge challenge. There are probably always elements which get left behind, but we just keep trying...

Glad to have been able to help!</description>
		<content:encoded><![CDATA[<blockquote><p>
I must say, however, making sure a site is accessible to people with a wide array of disabilities is very difficult without having those disabilities yourself.
</p></blockquote>
<p>That&#8217;s definitely the biggest challenge - putting yourself into the position of all the possible users and trying to take their needs into consideration is a huge challenge. There are probably always elements which get left behind, but we just keep trying&#8230;</p>
<p>Glad to have been able to help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fahed Bizzari</title>
		<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63964</link>
		<dc:creator>Fahed Bizzari</dc:creator>
		<pubDate>Wed, 27 Jun 2007 19:07:07 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63964</guid>
		<description>Thanks Joe. Their idea was that the enhancement would be de-activated when an input/textarea was involved, but i think we'll leave this "enhancement" off.

I must say, however, making sure a site is accessible to people with a wide array of disabilities is very difficult without having those disabilities yourself.

Thanks again for your insight.</description>
		<content:encoded><![CDATA[<p>Thanks Joe. Their idea was that the enhancement would be de-activated when an input/textarea was involved, but i think we&#8217;ll leave this &#8220;enhancement&#8221; off.</p>
<p>I must say, however, making sure a site is accessible to people with a wide array of disabilities is very difficult without having those disabilities yourself.</p>
<p>Thanks again for your insight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63943</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Wed, 27 Jun 2007 17:48:52 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63943</guid>
		<description>I'm inclined to doubt the value of that kind of an "enhancement." What it does is over-riding the normal behavior of the user-agent, which is never really recommended. Users of accesskeys most likely are very accustomed to the way in which they normally access them - and this enhancement just wouldn't really help them.

It should also be noted that the enhancement will cause major problems with any page which requires user input - any form with a text input. Obviously, if the user is typing an "h" in a form, they probably don't want to be suddenly sent off to the home page.

I can also imagine that it could cause problems for users trying to simply use their browser address bar to type in a new location or typing a search into their Google Toolbar - I'm not certain whether onpage scripting would impact this, but it should be tested, at the least.</description>
		<content:encoded><![CDATA[<p>I&#8217;m inclined to doubt the value of that kind of an &#8220;enhancement.&#8221; What it does is over-riding the normal behavior of the user-agent, which is never really recommended. Users of accesskeys most likely are very accustomed to the way in which they normally access them - and this enhancement just wouldn&#8217;t really help them.</p>
<p>It should also be noted that the enhancement will cause major problems with any page which requires user input - any form with a text input. Obviously, if the user is typing an &#8220;h&#8221; in a form, they probably don&#8217;t want to be suddenly sent off to the home page.</p>
<p>I can also imagine that it could cause problems for users trying to simply use their browser address bar to type in a new location or typing a search into their Google Toolbar - I&#8217;m not certain whether onpage scripting would impact this, but it should be tested, at the least.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fahed Bizzari</title>
		<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63777</link>
		<dc:creator>Fahed Bizzari</dc:creator>
		<pubDate>Wed, 27 Jun 2007 09:30:34 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63777</guid>
		<description>Thankyou.

In the end our developers used their own PHP code and finished this feature today and showed it to me about half an hour ago. I am quite impressed with the final result.

They also showed me a javascript enhancement which removes the need for the additional keys such as ctrl, alt, shift etc. So, instead of alt+shift+H for home, you would simply press H.

My opinion was, although it sounds great, it would be against the norm and may hinder accessibility unknowingly. Their response was that they could make it an option.

What's your thoughts on that? Would you say that, to make things simpler, we're making things more complicated?</description>
		<content:encoded><![CDATA[<p>Thankyou.</p>
<p>In the end our developers used their own <acronym title="Hypertext PreProcessing">PHP</acronym> code and finished this feature today and showed it to me about half an hour ago. I am quite impressed with the final result.</p>
<p>They also showed me a javascript enhancement which removes the need for the additional keys such as ctrl, alt, shift etc. So, instead of alt+shift+H for home, you would simply press H.</p>
<p>My opinion was, although it sounds great, it would be against the norm and may hinder accessibility unknowingly. Their response was that they could make it an option.</p>
<p>What&#8217;s your thoughts on that? Would you say that, to make things simpler, we&#8217;re making things more complicated?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63386</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 26 Jun 2007 14:30:35 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63386</guid>
		<description>If access keys are used at all, allowing the user to define them is absolutely the best choice. That leaves the options open to the user: they know what shortcuts they're likely to use with their own browser which they can then avoid assigning; they can standardize their choice of access keys in a manner which is intuitive to them. 

Assigning access keys via client-side scripting isn't really ideal, however. I'd suggest using a server-side solution --- I know of two freely available scripts for assigning access keys: &lt;a href="http://www.tjkdesign.com/articles/user_defined_accesskeys.asp"&gt;one in ASP&lt;/a&gt;, and one in &lt;a href="http://juicystudio.com/article/user-defined-accesskeys.php"&gt;PHP&lt;/a&gt;.  The PHP method has also been ported into ASP, so you can look at both versions of that one, as well. 

Hope that helps!</description>
		<content:encoded><![CDATA[<p>If access keys are used at all, allowing the user to define them is absolutely the best choice. That leaves the options open to the user: they know what shortcuts they&#8217;re likely to use with their own browser which they can then avoid assigning; they can standardize their choice of access keys in a manner which is intuitive to them. </p>
<p>Assigning access keys via client-side scripting isn&#8217;t really ideal, however. I&#8217;d suggest using a server-side solution &#8212; I know of two freely available scripts for assigning access keys: <a href="http://www.tjkdesign.com/articles/user_defined_accesskeys.asp">one in ASP</a>, and one in <a href="http://juicystudio.com/article/user-defined-accesskeys.php"><acronym title="Hypertext PreProcessing">PHP</acronym></a>.  The <acronym title="Hypertext PreProcessing">PHP</acronym> method has also been ported into ASP, so you can look at both versions of that one, as well. </p>
<p>Hope that helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fahed Bizzari</title>
		<link>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63274</link>
		<dc:creator>Fahed Bizzari</dc:creator>
		<pubDate>Tue, 26 Jun 2007 07:03:31 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/11/05/almost-getting-it-right-with-access-keys/#comment-63274</guid>
		<description>I am currently overseeing the redevelopment of our site and the solution which our developers have come with is to allow the user define the access keys using javascript. 

Obviously, this won't be of any good to non-js users, but that would be explained to them. 

What are your opinions in this regard?</description>
		<content:encoded><![CDATA[<p>I am currently overseeing the redevelopment of our site and the solution which our developers have come with is to allow the user define the access keys using javascript. </p>
<p>Obviously, this won&#8217;t be of any good to non-js users, but that would be explained to them. </p>
<p>What are your opinions in this regard?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.659 seconds -->
