Comments on: Access Keys - A Potential Solution? http://blackwidows.co.uk/blog/2005/12/16/access-keys-a-potential-solution/ The meanderings of a black widow... Fri, 21 Nov 2008 13:14:20 +0000 http://wordpress.org/?v=2.6.3 By: Administrator http://blackwidows.co.uk/blog/2005/12/16/access-keys-a-potential-solution/#comment-1130 Administrator Wed, 21 Dec 2005 11:41:40 +0000 http://www.blackwidows.co.uk/blog/?p=50#comment-1130 I appreciate that, especially for new users, being presented with a completely new set of choices could be overwhelming. However, I think there may be some issues with providing a suggested set of pre-defined keys within the context of a form. For example, a site implements the script and identifies 10 anchors, or links, that are likely to benefit from accesskey implementation. They also provide a set of pre-defined keys for users who may be unsure of what keys to use - maybe 0-9. User A then visits the site. S/he is an experienced user who has developed a series of well-honed strategies for coping with site navigation and, as a result, only wishes to set 3 or 4 accesskeys. If the form/script allows the pre-defined set to be enabled by default when the form is submitted, User A is going to have to manually clear at least 6 input boxes to avoid the mapping of keys that s/he doesn't want. That scenario may present some users with whole new set of problems to deal with. Reversing the situation slightly - the form doesn't set the pre-defined accesskeys by default but only if users select a box labelled "I want to use these keys" or uses a checkbox next to each input where they only want to use a sub-set. Again, we're going to be asking users to complete a form that may be more complex than it really needs to be. And these may be some of the very users who find form completion to be particularly difficult. Do we really want to make users jump through hoops if we can avoid it? Alternative suggestion: Don't provide a set of pre-defined keys but provide examples of keys that could be used - perhaps using UK Government guidelines (numeric keys 0-9) or based upon <a href="http://www.diveintoaccessibility.org/accessibility_statement.html">Mark Pilgrim's list of accesskeys</a>. Using this approach, we don't interfere with a user's potential choice, we keep the accesskey selection form as simple as possible and we, potentially, educate users. Following this train of thought, what would be a really nice 'extra' would be for site developers to provide a vehicle for more experienced users to submit lists of accesskeys that they'd found to be particularly useful. This could, theoretically, build up into quite a valuable resource - accessekys based, not on some theoretical guideline, but on actual, real life, usage. I appreciate that, especially for new users, being presented with a completely new set of choices could be overwhelming. However, I think there may be some issues with providing a suggested set of pre-defined keys within the context of a form.

For example, a site implements the script and identifies 10 anchors, or links, that are likely to benefit from accesskey implementation. They also provide a set of pre-defined keys for users who may be unsure of what keys to use - maybe 0-9. User A then visits the site. S/he is an experienced user who has developed a series of well-honed strategies for coping with site navigation and, as a result, only wishes to set 3 or 4 accesskeys.

If the form/script allows the pre-defined set to be enabled by default when the form is submitted, User A is going to have to manually clear at least 6 input boxes to avoid the mapping of keys that s/he doesn’t want. That scenario may present some users with whole new set of problems to deal with.

Reversing the situation slightly - the form doesn’t set the pre-defined accesskeys by default but only if users select a box labelled “I want to use these keys” or uses a checkbox next to each input where they only want to use a sub-set. Again, we’re going to be asking users to complete a form that may be more complex than it really needs to be. And these may be some of the very users who find form completion to be particularly difficult.

Do we really want to make users jump through hoops if we can avoid it?

Alternative suggestion: Don’t provide a set of pre-defined keys but provide examples of keys that could be used - perhaps using UK Government guidelines (numeric keys 0-9) or based upon Mark Pilgrim’s list of accesskeys.

Using this approach, we don’t interfere with a user’s potential choice, we keep the accesskey selection form as simple as possible and we, potentially, educate users.

Following this train of thought, what would be a really nice ‘extra’ would be for site developers to provide a vehicle for more experienced users to submit lists of accesskeys that they’d found to be particularly useful. This could, theoretically, build up into quite a valuable resource - accessekys based, not on some theoretical guideline, but on actual, real life, usage.

]]> By: grant broome http://blackwidows.co.uk/blog/2005/12/16/access-keys-a-potential-solution/#comment-1125 grant broome Mon, 19 Dec 2005 11:56:50 +0000 http://www.blackwidows.co.uk/blog/?p=50#comment-1125 I hope that the script is developed to include a set of pre-defined access keys. The danger is that the user will be too daunted at the prospect of defining their own, or that they will set keys that are already in use by the browser. An option of setting the keys to something relatively safe like the UK government standard would be a very good addition IMO. I'm really glad to see this moving forward. It's a genuine result for lots of mobility impaired keyboard users. I hope that the script is developed to include a set of pre-defined access keys.
The danger is that the user will be too daunted at the prospect of defining their own, or that they will set keys that are already in use by the browser. An option of setting the keys to something relatively safe like the UK government standard would be a very good addition IMO.

I’m really glad to see this moving forward. It’s a genuine result for lots of mobility impaired keyboard users.

]]>